starlingx/stx-puppet
Code Issues Proposed changes

pxeboot should be provisioned after BnR

Browse Source 
The pxeboot-ip service was not provisioned after an AIO-SX BnR in
R8.0, even though pxeboot ip ( 169.254.202.1 ) was installed.
This issue does not occur in R9.0.
However, the SM.pp can be simplified to ensure provisioning
in all cases.

Tests done:
AIO-SX fresh install
AIO-DX fresh install
AIO-DX host-swact
AIO-SX BnR
AIO-DX BnR

Closes-Bug: 2085537

Change-Id: I4143a23e75e8e17444364cf6c707722e9e494fd3
Signed-off-by: Fabiano Correa Mercer <fabiano.correamercer@windriver.com>
This commit is contained in:
Fabiano Correa Mercer 2024-10-22 16:26:25 -03:00
parent d74a25a7e7
commit 48d396dfdc
1 changed files with 5 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
puppet-manifests/src/modules/platform/manifests/sm.pp
View File

@ -486,16 +486,12 @@ class platform::sm
############################
# PXEBOOT
# Create the PXEBoot IP service if it is configured
# PXEBoot only supports IPv4 config
# TODO(heitormatsui) review if we can change this 'if' or move elsewhere like the other ipvX services
if str2bool($::is_initial_config) or str2bool($::usm_upgrade_in_progress) {
exec { 'Configure PXEBoot IPv4 service in SM (service-group-member pxeboot-ipv4)':
command => 'sm-provision service-group-member controller-services pxeboot-ipv4',
}
-> exec { 'Configure PXEBoot IPv4 service in SM (service pxeboot-ipv4)':
command => 'sm-provision service pxeboot-ipv4',
}
exec { 'Configure PXEBoot IPv4 service in SM (service-group-member pxeboot-ipv4)':
command => 'sm-provision service-group-member controller-services pxeboot-ipv4',
}
-> exec { 'Configure PXEBoot IPv4 service in SM (service pxeboot-ipv4)':
command => 'sm-provision service pxeboot-ipv4',
}
if $system_mode == 'duplex-direct' or $system_mode == 'simplex' {