Uploaded image for project: 'honeycomb'
  1. honeycomb
  2. HONEYCOMB-99

wrong execution order when changing ipv4 address

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • 16.09
    • None
    • None
    • None
    • Honeycomb buid: https://gerrit.fd.io/r/#/c/1490/
      VPP version: v16.09-rc0~134-ga026eb1
      both from 21. June

      Steps to reproduce:
      1. add ipv4 address to interface:
      "ietf-ip:ipv4": {"address": [

      {"ip": "192.168.0.2", "netmask": "255.255.255.0"}

      ]}
      2. remove the address and add a new one in a single PUT request:
      "ietf-ip:ipv4": {"address": [

      {"ip": "192.168.0.3", "netmask": "255.255.255.0"}

      ]}
      The new address is added before the old one is deleted. The delete operation should be completed first.

      3. get operational interface data:
      "ietf-ip:ipv4":{}
      4. get VPP ip adddress dump:
      192.168.0.2/24
      If the two addresses cannot be configured together (e.g. they are on the same subnet), this causes desync between VPP state and HC operational data.

            mgradzki Marek Gradzki
            selias Samuel Eliáš
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: