StarlingX

AIO-DX controller-1 fails to unlock - it thinks it's in static mgmt address mode

Bug #1794576 reported by Chris Winnicki
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
High
Teresa Ho

Bug Description

Title
-----
AIO-DX controller-1 fails to unlock - it thinks it's in static mgmt address mode

Brief Description
-----------------
controller-1 fails to unlock when MGMT interface is configured as AE

Severity
--------
Provide the severity of the defect.
Critical: Controller-1 is unusable when MGMT is configured as AE

Steps to Reproduce
------------------
1)
Install controller-0
Run config_controller

Example config file:
##########################################################################
[SYSTEM]
SYSTEM_MODE=duplex-direct

[MGMT_NETWORK]
CIDR = 192.168.204.0/24
MULTICAST_CIDR=239.1.1.0/28
DYNAMIC_ALLOCATION = Y
LOGICAL_INTERFACE = LOGICAL_INTERFACE_1

[LOGICAL_INTERFACE_1]
LAG_INTERFACE = Y
LAG_MODE = 4
INTERFACE_MTU = 9216
INTERFACE_LINK_CAPACITY = 10000
INTERFACE_PORTS = enp5s0f0, enp5s0f1

[OAM_NETWORK]
CIDR = 128.224.150.0/23
MULTICAST_CIDR=239.1.1.0/28
GATEWAY = 128.224.150.1
IP_FLOATING_ADDRESS = 128.224.150.49
IP_UNIT_0_ADDRESS = 128.224.150.48
IP_UNIT_1_ADDRESS = 128.224.150.52
LOGICAL_INTERFACE = LOGICAL_INTERFACE_3

[LOGICAL_INTERFACE_3]
LAG_INTERFACE = N
INTERFACE_MTU = 1500
INTERFACE_PORTS = eno1

[AUTHENTICATION]
ADMIN_PASSWORD = Test123r*
##########################################################################

2)
Configure controller-0 interfaces as in the example below

[wrsroot@controller-0 ~(keystone_admin)]$ system host-if-list controller-0
+--------------------------------------+----------+----------+----------+------+---------------+--------------+-------------+------------------------------------------------+-------------------+
| uuid | name | class | type | vlan | ports | uses i/f | used by i/f | attributes | provider networks |
| | | | | id | | | | | |
+--------------------------------------+----------+----------+----------+------+---------------+--------------+-------------+------------------------------------------------+-------------------+
| 0a223047-6cfb-4d7a-8c4e-57b4b1c5cbb9 | enp5s0f1 | None | ethernet | None | [u'enp5s0f1'] | [] | [u'bond0'] | MTU=9216 | None |
| 3baf9599-5511-4f9d-a85c-2aec02ef66a8 | oam0 | platform | ethernet | None | [u'eno1'] | [] | [] | MTU=1500 | None |
| b5b476d7-f3c8-4d9c-a12e-680ce3bfde7f | enp5s0f0 | None | ethernet | None | [u'enp5s0f0'] | [] | [u'bond0'] | MTU=9216 | None |
| e0a4cea0-91ac-4bfd-b79a-58ddaaa1e169 | data0 | data | ethernet | None | [u'enp4s0f0'] | [] | [] | MTU=1500,accelerated=True | group0-data0 |
| f4980912-f663-4587-a4d2-d41c24596e18 | bond0 | platform | ae | None | [] | [u'enp5s0f0' | [] | MTU=9216,AE_MODE=802.3ad,AE_XMIT_POLICY=layer2 | None |
| | | | | | | , | | | |
| | | | | | | u'enp5s0f1'] | | | |
| | | | | | | | | | |
+--------------------------------------+----------+----------+----------+------+---------------+--------------+-------------+------------------------------------------------+-------------------+

3)
Configure controller-1 interfaces as in the example below:
[wrsroot@controller-0 ~(keystone_admin)]$ system host-if-list controller-1
+--------------------------------------+----------+----------+----------+------+---------------+--------------+-------------+------------------------------------------------+-------------------+
| uuid | name | class | type | vlan | ports | uses i/f | used by i/f | attributes | provider networks |
| | | | | id | | | | | |
+--------------------------------------+----------+----------+----------+------+---------------+--------------+-------------+------------------------------------------------+-------------------+
| 3fce815e-7a2a-4f6f-a3dd-25cb8000739e | mgmt0 | platform | ae | None | [] | [u'enp5s0f1' | [] | MTU=1500,AE_MODE=802.3ad,AE_XMIT_POLICY=layer2 | None |
| | | | | | | , | | | |
| | | | | | | u'enp5s0f0'] | | | |
| | | | | | | | | | |
| aff83cfd-cffc-4452-8203-f8094325a632 | enp5s0f0 | None | ethernet | None | [u'enp5s0f0'] | [] | [u'mgmt0'] | MTU=1500 | None |
| e8bc86e1-e869-43c7-9b55-92347459b01e | oam0 | platform | ethernet | None | [u'eno1'] | [] | [] | MTU=1500 | None |
| ee0d401f-4969-495b-a1f5-a2f048fec847 | enp5s0f1 | None | ethernet | None | [u'enp5s0f1'] | [] | [u'mgmt0'] | MTU=1500 | None |
| ffa0ee26-59c7-4ac0-aa92-efc80d35818b | data0 | data | ethernet | None | [u'enp4s0f0'] | [] | [] | MTU=1500,accelerated=True | group0-data0 |
+--------------------------------------+----------+----------+----------+------+---------------+--------------+-------------+------------------------------------------------+----------------

4) Attempt to unlock controller-1

Expected Behavior
------------------
controller-1 should unlock without any issues

Actual Behavior
----------------
controller-1 fails to unlock with the following error:

system host-unlock controller-1
Interface mgmt0 on host controller-1 is configured for IPv4 static address but has no configured IPv4 address

Reproducibility
---------------
100% reproducible

System Configuration
--------------------
Two node system (duplex-direct), https, IPv4

Branch/Pull Time/Commit
-----------------------
master as of 2018-09-23_20-18-00

Timestamp/Logs
--------------
n/a

Revision history for this message
Ghada Khalil (gkhalil) wrote :

Targeting stx.2018.10 as the issue is introduced by the Generalized Interface and Networking Feature. This affects systems configured with MGMT AEs and make them unusable.

Changed in starlingx:
importance: Undecided → High
assignee: nobody → Teresa Ho (teresaho)
status: New → Triaged
tags: added: stx.2018.10 stx.networking
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to stx-config (master)

Fix proposed to branch: master
Review: https://review.openstack.org/605502

Changed in starlingx:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to stx-config (master)

Reviewed: https://review.openstack.org/605502
Committed: https://git.openstack.org/cgit/openstack/stx-config/commit/?id=b5fd521f8e954da7033a82ee2843a86e81a5137e
Submitter: Zuul
Branch: master

commit b5fd521f8e954da7033a82ee2843a86e81a5137e
Author: Teresa Ho <email address hidden>
Date: Wed Sep 26 14:17:34 2018 -0400

    Clear networktype when interface class is reset

    When the interface class was reset to none, the networktype was
    unchanged which leads to inconsistent data.
    This update is to clear the networktype when the interface class
    is set to none.

    Closes-Bug: 1794576

    Change-Id: If9e3593c6888981c3cd13ef5a338950f5d2fe24d
    Signed-off-by: Teresa Ho <email address hidden>

Changed in starlingx:
status: In Progress → Fix Released
Ken Young (kenyis)
tags: added: stx.1.0
removed: stx.2018.10
Revision history for this message
Owen Yuen (kkum) wrote :

Hi I ran into this problem again during an AIO dist cloud installation R4.

https://i.imgur.com/zgYDcUu.png

How do I fix this without reinstalling?

Thanks

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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