Description of problem: When upgrading controller nodes, we should stop all services on unupgraded controller nodes before we start services on the upgraded bootstrap controller. However currently there are no logics implemented to stop manila services on unupgraded controller nodes. As a result we get manila services running on both unupgraded controller nodes and upgraded nodes, in the middle of upgrade. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Deploy RHOSP13 with manila enabled in overcloud 2. Follow the upgrade procedures described in the documentation[1] [1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/framework_for_upgrades_13_to_16.1/index Actual results: manila services on unupgraded controller nodes are not stopped even after system_upgrade_transfer_data is executed(*1) Expected results: manila services on unupgraded controller nodes are stopped when system_upgrade_transfer_data is executed(*1) Additional info: (*1) $ openstack overcloud external-upgrade run --stack STACK NAME --tags system_upgrade_transfer_data
Hi, as you're pulling the review upstream I'll assign this to you, thanks for the work, don't hesitate to reach out if you need any help. Thanks,
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenStack Platform 16.1.6 bug fix and enhancement advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:2097