Using different interface for br-fw-admin than the boot interface, IP duplication will be present after rebooting the host

Bug #1526424 reported by Alexander Zatserklyany
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Medium
Stanislav Makar
7.0.x
Invalid
Medium
Stanislav Makar

Bug Description

Using different interface for br-fw-admin than the boot interface, IP duplication will be present after rebooting the host (right after provisioning)
In this case 2 network interfaces are connected to admin network and 1st one used for booting but the other should be used for normal service.

Steps to reproduce
-----------------------------
1. Create environment
    fuel env create --name=test --mode=ha --rel=2
2. Upload network template (see in attachment)
    fuel --env 1 network-template --upload
3. Add node with role 'virt'
    fuel node -s --env 1 --node-id=1 --role=virt
4. Provision the node
    fuel --env 1 node --provision --node 1
5. Execute netconfig task
    fuel node --node 1 --end netconfig
6. Get net configuration
    ssh node-1 ifconfig | grep -A 1 -E 'br-fw-admin|eth0'

Expected results:
--------------------------
br-fw-admin and eth0 has different IPs

Actual results:
---------------------
br-fw-admin Link encap:Ethernet HWaddr 0c:c4:7a:13:4a:91
          inet addr:172.16.58.201 Bcast:172.16.58.255 Mask:255.255.255.192
--
eth0 Link encap:Ethernet HWaddr 0c:c4:7a:13:4a:90
          inet addr:172.16.58.201 Bcast:172.16.58.255 Mask:255.255.255.192

Revision history for this message
Alexander Zatserklyany (zatserklyany) wrote :
tags: added: feature-network-template l23network
Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Stanislav Makar (smakar)
status: New → Confirmed
Revision history for this message
Anton Matveev (amatveev) wrote :

sla2 tag for MOS7.0

tags: added: sla2
Dmitry Pyzhov (dpyzhov)
tags: added: area-library
Stanislav Makar (smakar)
Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
Stanislav Makar (smakar) wrote :

I have just researched all variants and there is no such possibility to disable and flush ip address you already used to boot in templates due to It is a very rare case but there are some workarounds:

1. Disable the not_needed_int and boot, provision and deploy on that interface which you want to be in admin network
2. You can upload template and then download astute.yaml for every node and add there endpoint with below values and upload them:

for example
network_scheme:
  transformations:
   - action: add-port
    name: not_neede_int
  endpoints:
    not_neede_int:
      IP: none

3. You can assign this not_needed_int to the fake network in template

Changed in fuel:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.