controller-0 mgmt_mac not set after ansible configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Tee Ngo |
Bug Description
Brief Description
-----------------
After configuring the system using the Ansible playbook, configuring the remaining attributes, and unlock controller-0 the "mgmt_mac" remains uninitialized at 00:00:00:00:00:00. This does not seem to cause any issues until the system is swacted away from controller-0 and controller-0 is rebooted. Once in this state the node will not recover as mtce is failing to enable services.
The node's current task is set to:
Service Failure, threshold reached, Lock/Unlock to retry
The mtcClient.log on the local node is repeatedly reporting (which seems to indicate a mismatch in the expected MAC address):
2019-05-
2019-05-
Severity
--------
Critical, controller-0 will not recover following a reboot or lock/unlock.
Steps to Reproduce
------------------
Install a system using the Ansible playbook, manually configured the required attributes, and install/configure the remaining nodes. Once the system is completely installed/
Expected Behavior
------------------
The mgmt_mac should be set based on the MAC address of the mgmt interface once the controller-0 node is configured and unlocked.
Actual Behavior
----------------
mgmt_mac is never initialized properly.
Reproducibility
---------------
100%
System Configuration
-------
Standard system (2+4)
Branch/Pull Time/Commit
-------
Private load rebased from May 10.
Last Pass
---------
Unknown
Timestamp/Logs
--------------
See above
Test Activity
-------------
Developer testing
Changed in starlingx: | |
assignee: | nobody → Tee Ngo (teewrs) |
Changed in starlingx: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: stx.config |
Marking as release gating; related to ansible deployment feature. system impact is high as the controller won't recover if rebooted/swacted.