starlingx
/
config
Code Issues Proposed changes

Controller-1 fails to unlock after data-migration 

During an upgrade, data-migration will complete, but the inv_state for
controller-1 will remain at reinstalling. Consequently it will not be
possible to unlock controller-1.

This is addressed by starting the sysinv-agent after the data migration
is complete. The sysinv-agent will then report the inv_state to
controller-0.

Story: 2008055
Task: 40971
Change-Id: I96eb5359bc6b7438c63f1af376db5d8a4a7327f5
Signed-off-by: David Sullivan <david.sullivan@windriver.com>
This commit is contained in:
David Sullivan 2020-09-24 10:31:53 -04:00
parent 5d29b9e0d9
commit dec27c3b21
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
controllerconfig/controllerconfig/controllerconfig/upgrades/controller.py
View File

@ -1014,6 +1014,14 @@ def upgrade_controller(from_release, to_release):
unmount_filesystem("/tmp/etc_platform")
os.rmdir("/tmp/etc_platform")
# Restart the sysinv agent to report the inventory status
# The sysinv.conf contains temporary parameters that are used for
# data-migration. By removing that sysinv.conf we trigger the sysinv-agent
# to load the correct conf from the drbd filesystem
os.remove("/etc/sysinv/sysinv.conf")
LOG.info("Starting sysinv-agent")
cutils.start_service("sysinv-agent")
print("Controller-1 upgrade complete")
LOG.info("Controller-1 upgrade complete!!!")