Hide Forgot
Description of problem: Minor version upgrade to latest minor version is getting failed. Version-Release number of selected component (if applicable): RHEL OSP 7 How reproducible: Everytime for customer. Steps to Reproduce: 1. Template used to upgrade : -e /usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \ -e /home2/stack/templates/network-environment.yaml \ -e /home2/stack/templates/storage-environment.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/updates/update-from-vip.yaml \ -e /home2/stack/templates/param-updates.yaml 2. command used for overcloud upgrade : openstack overcloud update stack overcloud -i \ --templates \ -e /usr/share/openstack-tripleo-heat-templates/overcloud-resource-registry-puppet.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \ -e /home2/stack/templates/network-environment.yaml \ -e /home2/stack/templates/storage-environment.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/updates/update-from-vip.yaml \ -e /home2/stack/templates/param-updates.yaml 3. Actual results: Minor version update is not making the progress for package upgrade on overcloud nodes. Expected results: Minor version update should update the overcloud packages. Additional info: Stuck at step "10.3.5. Updating the Overcloud Packages" of official guide : https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/7/html-single/Director_Installation_and_Usage/index.html#sect-Updating_the_Overcloud_Packages
Initially upgrade command was failed because of timeout and it was showing the message "Started yum_update.sh on server d2a5d176-0ebc-4c35-8cb0-4718bb0fef23 at Fri Jan 8 06:17:49 EST 2016\nNot running due to unset update_identifier\n" for all IN_PROGRESS resources. ~~~ { "status": "IN_PROGRESS", "server_id": "d2a5d176-0ebc-4c35-8cb0-4718bb0fef23", "config_id": "6abd218a-a583-4a16-900a-7447f3ced6cd", "output_values": { "deploy_stdout": "Started yum_update.sh on server d2a5d176-0ebc-4c35-8cb0-4718bb0fef23 at Fri Jan 8 06:17:49 EST 2016\nNot running due to unset update_identifier\n", "deploy_stderr": "", "update_managed_packages": "false", "deploy_status_code": 0 }, "creation_time": "2016-01-08T12:18:15Z", "updated_time": "2016-11-19T01:15:11Z", "input_values": {}, "action": "UPDATE", "status_reason": "Deploy data available", "id": "78a23916-18ee-4853-875d-7ad836563afe" } { "status": "IN_PROGRESS", "server_id": "d2a5d176-0ebc-4c35-8cb0-4718bb0fef23", "config_id": "6abd218a-a583-4a16-900a-7447f3ced6cd", "output_values": { "deploy_stdout": "Started yum_update.sh on server d2a5d176-0ebc-4c35-8cb0-4718bb0fef23 at Fri Jan 8 06:17:49 EST 2016\nNot running due to unset update_identifier\n", "deploy_stderr": "", "update_managed_packages": "false", "deploy_status_code": 0 }, "creation_time": "2016-01-08T12:18:15Z", "updated_time": "2016-11-19T01:15:11Z", "input_values": {}, "action": "UPDATE", "status_reason": "Deploy data available", "id": "78a23916-18ee-4853-875d-7ad836563afe" } { "status": "IN_PROGRESS", "server_id": "d2a5d176-0ebc-4c35-8cb0-4718bb0fef23", "config_id": "6abd218a-a583-4a16-900a-7447f3ced6cd", "output_values": { "deploy_stdout": "Started yum_update.sh on server d2a5d176-0ebc-4c35-8cb0-4718bb0fef23 at Fri Jan 8 06:17:49 EST 2016\nNot running due to unset update_identifier\n", "deploy_stderr": "", "update_managed_packages": "false", "deploy_status_code": 0 }, "creation_time": "2016-01-08T12:18:15Z", "updated_time": "2016-11-19T01:15:11Z", "input_values": {}, "action": "UPDATE", "status_reason": "Deploy data available", "id": "78a23916-18ee-4853-875d-7ad836563afe" } ~~~ Try to set the following parameter in "/home2/stack/templates/network-environment.yaml " to get rid of "Not running due to unset update_identifier" message. ~~~ UpdateIdentifier: '' ~~~ But no luck it's not showing any breakpoint as indicated in official guide. Upgrade command is keep on running.