Debian: subcloud install values network_address/mask are not supported
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
In Progress
|
Undecided
|
Unassigned |
Bug Description
Brief Description
The install values 'network_address' and 'network_mask' are not supported in Debian.
These values are required for the networking configuration use-case of applying a static route instead of a default route for the nexthop_gateway during the subcloud install and bootstrap.
Severity
<Major: System/Feature is usable but degraded>
This is missing functionality, However, it's not clear if anyone is actually use this configuration.
Steps to Reproduce
Need a specific installation environment where a gateway is used which is not directly accessible via the subcloud, requiring the use of a static route to the gateway using the supplied subcloud install values of 'network_address' and 'network_mask'.
Expected Behavior
When including 'network_address' and 'network_mask' install values, the subcloud install is supposed to create a static route to the nexthop_gateway instead of a default route.
Actual Behavior
'network_address' and 'network_mask' install values are currently ignored in Debian.
Reproducibility
Reproducible
System Configuration
DC system
Subcloud with nexthop_gateway which is not directly accessible from subcloud (requiring a static route to gateway).
Last Pass
Did this test scenario pass previously? If so, please indicate the load/pull time info of the last pass.
To my knowledge this was working in Centos via the generated kickstart scripts.
Timestamp/Logs
n/a. We do not have a system configured for testing this scenario.
Alarms
n/a
Workaround
Involves low-level interruption and manual intervention during the kickstart execution time.
Fix proposed to branch: master /review. opendev. org/c/starlingx /metal/ +/907909
Review: https:/