OAM IP change needs double lock/unlock controllers for IPV6 system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Andre Kantek |
Bug Description
Brief Description
-----------------
IPv6 two nodes system OAM IP change need double lock/unlock of the controllers for the new IP to take effect on the OAM network IF. (while IPv4 system only need single lock/unlock of the controllers)
Severity
--------
Major
Steps to Reproduce
------------------
On a multiple nodes system with two controllers:
1. record OAM IP addresses before making the change:
[root@controller-0 sysadmin(
+------
| Property | Value |
+------
| created_at | 2020-09-
| isystem_uuid | 4a6501e4-
| oam_c0_ip | 2620:10a:
| oam_c1_ip | 2620:10a:
| oam_floating_ip | 2620:10a:
| oam_gateway_ip | 2620:10a:
| oam_subnet | 2620:10a:
| updated_at | None |
| uuid | 6b51882b-
+------
On active controller (controller-0 in this test):
[root@controller-0 sysadmin(
11: enp135s0f1: <BROADCAST,
link/ether 3c:fd:fe:b1:29:f5 brd ff:ff:ff:ff:ff:ff
inet6 2620:10a:
valid_lft forever preferred_lft forever1: lo: <LOOPBACK,
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
inet6 2620:10a:
valid_lft forever preferred_lft forever
inet6 fe80::3efd:
valid_lft forever preferred_lft forever
On standby controller:
[sysadmin@
2: enp134s0f0: <BROADCAST,
link/ether 00:15:17:c7:bf:1c brd ff:ff:ff:ff:ff:ff
inet6 2620:10a:
valid_lft forever preferred_lft forever
inet6 fe80::215:
valid_lft forever preferred_lft forever
2. Change OAM IP address:
[root@controller-0 sysadmin(
+------
| Property | Value |
+------
| created_at | 2020-09-
| isystem_uuid | 4a6501e4-
| oam_c0_ip | 2620:10a:
| oam_c1_ip | 2620:10a:
| oam_floating_ip | 2620:10a:
| oam_gateway_ip | 2620:10a:
| oam_subnet | 2620:10a:
| updated_at | None |
| uuid | 6b51882b-
+------
3. lock/unlock standby controller (controller-1 in this case)
4. On the standby controller (controller-1 in this case), check its OAM network IF again:
controller-
2: enp134s0f0: <BROADCAST,
link/ether 00:15:17:c7:bf:1c brd ff:ff:ff:ff:ff:ff
inet6 2620:10a:
valid_lft forever preferred_lft forever
inet6 fe80::215:
Notice that the IP address is still the old one (2620:10a:
5. lock/unlock the standby controller again
6. check standby controller's OAM IF
controller-
2: enp134s0f0: <BROADCAST,
link/ether 00:15:17:c7:bf:1c brd ff:ff:ff:ff:ff:ff
inet6 2620:10a:
valid_lft forever preferred_lft forever
inet6 fe80::215:
valid_lft forever preferred_lft forever
Notice that the IP address now changes to the new one (2620:10a:
Expected Behavior
------------------
standby controller's OAM network IF IP address should change to reflect the new IP after first lock/unlock.
Actual Behavior
----------------
The standby controller's OAM IF IP remains unchanged until a second lock/unlock.
Reproducibility
---------------
100 % reproducible
System Configuration
-------
System with two controllers and IPv6 on OAM.
Branch/Pull Time/Commit
-------
latest on master.
Last Pass
---------
Unknown
Timestamp/Logs
--------------
See steps to reproduce.
Test Activity
-------------
Developer Testing
Workaround
----------
double lock/unlock the controllers for the new IP to take effect.
CVE References
Changed in starlingx: | |
importance: | Undecided → Medium |
status: | New → Triaged |
tags: | added: stx.5.0 stx.config |
Changed in starlingx: | |
assignee: | nobody → Andre Kantek (akantek) |
tags: | added: in-r-stx50 |
Also want to point out that, after swact to make controller-1 as active controller, controller-0 would need double lock/unlock for the new OAM IP to take effect on its OAM IF as well.