Debian: kickstart incorrectly updates platform.conf:http_port on controller-0 install
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Eric MacDonald |
Bug Description
The Debian unified kickstart, for controller-0 install from external pxeboot server, is trying to extract an http port number from the $insturl install variable. However, since the wrcp controller-0 install grub menus don't include (and never have) an http port in the specified url we see that the platform.
The CentOS kickstart simply defaults the port to 8080 for the initial controller-0 install case.
Severity
--------
Minor: The incorrect value is never used and replaced with the correct value during the configuration cycle over the unlock.
Steps to Reproduce
------------------
pxeboot install controller-0 from external pxeboot server without http port specified (normal).
Expected Behavior
-----------------
http_port in platform.conf should default to 8080
Actual Behavior
---------------
http_port in platform.conf is set to the <insturl=....> env output value
Reproducibility
---------------
100% reproducible
System Configuration
-------
Any controller-0 install
Load info
---------
Any prior to 2022-06-30
Last Pass
---------
Never observed as it has no real impact therefore no test case verifying it at time its incorrect.
Workaround
----------
Not required. Issue has no product impact.
Any controller-0 install
tags: | added: stx.7.0 stx.debian stx.metal |
Changed in starlingx: | |
importance: | Undecided → Low |
assignee: | nobody → Eric MacDonald (rocksolidmtce) |
Fix proposed to branch: master /review. opendev. org/c/starlingx /metal/ +/849383
Review: https:/