IPv4 subcloud deployment failure with Bond interfaces
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Mohammad Issa |
Bug Description
Brief Description
-----------------
Subcloud deployments are failing because the conductor could not reach one of the oam vlan IP, but can after reboot.
Severity
--------
Major: Subcloud deployment fails and needs to be rebooted before getting stable
Steps to Reproduce
------------------
Create a subcloud deployment with a bond interface.
Expected Behavior
------------------
Subcloud vlan comes up with the specified bond name in DM config.
Actual Behavior
----------------
Subcloud vlan coming up with bootstrap interface instead of bond interface
Reproducibility
---------------
Reproducible 100% for ipv4 simplex.
System Configuration
-------
Distributed Cloud
Last Pass
---------
-
Timestamp/Logs
--------------
Test Activity
-------------
Developer Testing (Unit Test)
Workaround
----------
After the reboot, the conf changes to the desired naming and the connectivity between the conductor and subcloud is resolved.
Changed in starlingx: | |
assignee: | nobody → Mohammad Issa (m-issa) |
Changed in starlingx: | |
importance: | Undecided → Medium |
tags: | added: stx.9.0 stx.networking |
Fix proposed to branch: master /review. opendev. org/c/starlingx /metal/ +/906007
Review: https:/