Browse Source

AIO-SX reboots after change OAM ip address

On HW tests, it was detected that openstack-endpoints restart was
happening at the same as the service-manager restart, this creating
a conflict that preventing SM services to reach enabled-active.
This was provoking the reboot.

The correction add a class to execute openstack-endpoint runtime
restart on the post stage on puppet, avoiding to be run as SM is
restarted.

Tested on AIO-SX, by monitoring manifest apply and validating that
no reboot happens

Closes-Bug: 1927275
Depends-On: https://review.opendev.org/c/starlingx/stx-puppet/+/789946

Signed-off-by: Andre Fernando Zanella Kantek <AndreFernandoZanella.Kantek@windriver.com>
Change-Id: I9f547fbcc73ba5fea077c764a4a9282a02ac71c6
changes/47/789947/1
Andre Fernando Zanella Kantek 2 months ago
parent
commit
3e9982bab0
1 changed files with 1 additions and 1 deletions
  1. +1
    -1
      sysinv/sysinv/sysinv/sysinv/conductor/manager.py

+ 1
- 1
sysinv/sysinv/sysinv/sysinv/conductor/manager.py View File

@ -6686,7 +6686,7 @@ class ConductorManager(service.PeriodicService):
'platform::sm::update_oam_config::runtime',
'platform::nfv::webserver::runtime',
'platform::haproxy::runtime',
'openstack::keystone::endpoint::runtime',
'openstack::keystone::endpoint::runtime::post',
'platform::dockerdistribution::config',
'platform::dockerdistribution::runtime']
}


Loading…
Cancel
Save