aio-dx duplex-direct ifup failure because of interface name mismatch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Teresa Ho |
Bug Description
Brief Description
-----------------
The initial controller unlock on an AIO-DX duplex-direct system fails because of a failure to bring up the mgmt interface. The issue appears related to how the interface name is constructed for the ifcfg script's pre-up option. The name used is the configured interface name rather than the o/s interface name.
This error occurs when the ifup is attempted manually:
controller-
sysctl: cannot stat /proc/sys/
This is related to the fix for bug: https:/
Severity
--------
Critical, the first unlock fails and the system is not recoverable.
Steps to Reproduce
------------------
Install an AIO-DX duplex-direct system with mgmt network on a physical interface and cluster-host on a vlan interface.
Expected Behavior
------------------
The unlock should succeed and the initial reboot should successfully enable all platform services.
Actual Behavior
----------------
The unlock succeeds, but platform services are not enabled due to the missing mgmt IP address related to the interface configuration failure.
Reproducibility
---------------
100%
System Configuration
-------
AIO-DX duplex-direct
Branch/Pull Time/Commit
-------
09/oct/2019
Last Pass
---------
07/oct/2019
Timestamp/Logs
--------------
See above
Test Activity
-------------
Feature testing
Changed in starlingx: | |
assignee: | nobody → Teresa Ho (teresaho) |
tags: | added: stx.networking |
Marking as stx.3.0 / high priority - issue is introduced by recent code changes and makes a supported config (AIO-Duplex-Direct w/ IPv4) not usable.