Created attachment 1507151 [details] undercloud_update.log Description of problem: when using custom stack name like qe-Cloud-0 the undercloud update log shows the following error: 2018-11-18 11:12:23 | 2018-11-18 11:12:23,624 INFO: Starting and waiting for validation groups ['post-upgrade'] 2018-11-18 11:12:51 | 2018-11-18 11:12:51,328 ERROR: ERROR error running the validation groups ['post-upgrade'] {"stderr": "[DEPRECATION WARNING]: DEFAULT_SUDO_FLAGS option, In favor of become which is a\n generic framework . This feature will be removed in version 2.8. Deprecation \nwarnings can be disabled by setting deprecation_warnings=False in ansible.cfg.\n", "stdout": "Task 'Fail if the HorizonPublic endpoint is not defined' failed:\nHost: undercloud\nMessage: The `HorizonPublic` endpoint is not defined in the `EndpointMap` of the deployed stack. This means Horizon may not have been deployed correctly.\n\nFailure! The validation failed for all hosts:\n* undercloud\n"} {"stderr": "[DEPRECATION WARNING]: DEFAULT_SUDO_FLAGS option, In favor of become which is a\n generic framework . This feature will be removed in version 2.8. Deprecation \nwarnings can be disabled by setting deprecation_warnings=False in ansible.cfg.\n/usr/lib/python2.7/site-packages/requests/packages/urllib3/connection.py:344: SubjectAltNameWarning: Certificate for 192.168.24.2 has no `subjectAltName`, falling back to check for a `commonName` for now. This feature is being removed by major browsers and deprecated by RFC 2818. (See https://github.com/shazow/urllib3/issues/497 for details.)\n SubjectAltNameWarning\n", "stdout": "Task 'Check stack resource statuses' failed:\nHost: undercloud\nMessage: An unhandled exception occurred while running the lookup plugin 'stack_resources'. Error was a <class 'heatclient.exc.HTTPNotFound'>, original message: ERROR: The Stack (overcloud) could not be found.\n\nFailure! The validation failed for all hosts:\n* undercloud\n"} Mistral execution ID: 4aa85219-21b3-4f9f-b2f2-3e516f4c1881 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Install ops13 with custom stack name like qe-Cloud-0 2. run undercloud upgrade command 3. Actual results: post task fails Expected results: Additional info: More info can be found in the attached log and in Jenkins jobs: https://rhos-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DFG/view/upgrades/view/update/job/DFG-upgrades-updates-13-from-ga-composable-ipv4-predictable/?auto_refresh=false
Still blocked because of an instack-undercloud issue
FYI the current fix for this is resulting in an undercloud upgrade failure. See https://bugs.launchpad.net/tripleo/+bug/1832637
Moving this back to ON_DEV and adding a blocker as the current version of this fix will break customers ability to upgrade when they have validations enabled. I have proposed a fix upstream for the issue.
*** Bug 1720080 has been marked as a duplicate of this bug. ***
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, 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-2019:1738
*** Bug 1573120 has been marked as a duplicate of this bug. ***