Uploaded image for project: 'groupbasedpolicy'
  1. groupbasedpolicy
  2. GBP-285

NSH headers not recognized

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • None
    • unspecified
    • Integration:SFC
    • None
    • Operating System: All
      Platform: All

    • 8488
    • Normal

      There is a problem on Jenkins in groupbasedpolicy jobs. We can't upgrade OVS properly.

      We moved from
      curl https://raw.githubusercontent.com/pritesh/ovs/nsh-v8/third-party/start-ovs-deb.sh | bash
      to
      curl https://raw.githubusercontent.com/yyang13/ovs_nsh_patches/master/start-ovs-deb.sh | bash
      since this patch got merged in Openflowplugin
      https://git.opendaylight.org/gerrit/#/c/43697/

      The installation script for new OVS should uninstall existing version of OVS and the install the new one.
      This seems to finish successfully.

      But when trying to add the following flows, an error is returned.

      sudo ovs-ofctl add-flow $sw "priority=1000,nsi=255,actions=move:NXM_NX_NSH_MDTYPE[]>NXM_NX_NSH_MDTYPE[],move:NXM_NX_NSH_NP[]>NXM_NX_NSH_NP[],move:NXM_NX_NSP[]>NXM_NX_NSP[],load:254>NXM_NX_NSI[],move:NXM_NX_NSH_C1[]>NXM_NX_NSH_C1[],move:NXM_NX_NSH_C2[]>NXM_NX_NSH_C2[],move:NXM_NX_TUN_ID[0..31]>NXM_NX_TUN_ID[0..31],load:$TUNNEL>NXM_NX_TUN_IPV4_DST[],load:0x4->NXM_NX_TUN_GPE_NP[],IN_PORT" -OOpenFlow13

      ovs-ofctl: unknown keyword nsi

      sudo ovs-ofctl add-flow $sw "priority=1000,actions=move:NXM_NX_NSH_MDTYPE[]>NXM_NX_NSH_MDTYPE[],move:NXM_NX_NSH_NP[]>NXM_NX_NSH_NP[],move:NXM_NX_NSP[]>NXM_NX_NSP[],load:254>NXM_NX_NSI[],move:NXM_NX_NSH_C1[]>NXM_NX_NSH_C1[],move:NXM_NX_NSH_C2[]>NXM_NX_NSH_C2[],move:NXM_NX_TUN_ID[0..31]>NXM_NX_TUN_ID[0..31],load:$TUNNEL>NXM_NX_TUN_IPV4_DST[],load:0x4->NXM_NX_TUN_GPE_NP[],IN_PORT" -OOpenFlow13

      ovs-ofctl: NXM_NX_NSH_MDTYPE[]->NXM_NX_NSH_MDTYPE[]: unknown field `NXM_NX_NSH_MDTYPE

      The problem seems to be that the new OVS does not recognize NSH headers. The problem seems to be localy significant to Jenkins, haven't been spot elsewhere.
      I was wondering if someone from integration project can help us with this. Maybe it's just a matter of upgrading ovs in releng/builder and not while test is running.

      I don't think that we can just replace github link or rewrite versions in releng builder, since installing this new ovs version require some extra work.

      Thanks
      Tomas

            Unassigned Unassigned
            tcechval Tomas Cechvala
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: