Bug 1243472 - don't save UpdateIdentifier in tuskar when running package update
Summary: don't save UpdateIdentifier in tuskar when running package update
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: y1
: 7.0 (Kilo)
Assignee: Jan Provaznik
QA Contact: Udi Kalifon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-15 14:07 UTC by Jan Provaznik
Modified: 2023-02-22 23:02 UTC (History)
9 users (show)

Fixed In Version: openstack-tripleo-common-0.0.1.dev6-2.git49b57eb.el7ost
Doc Type: Bug Fix
Doc Text:
Updating an Overcloud sets the UpdateIdentifier parameters for each node in the director's Overcloud plan. However, deleting the Overcloud stack and redeploying it results in failure if the UpdateIdentifier parameters are set due to no preset repositories upon deployment. This fix stops the Overcloud from setting the UpdateIdentifier parameter on each node. This results in a successful Overcloud deployment.
Clone Of:
Environment:
Last Closed: 2015-10-08 12:14:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 202120 0 'None' 'MERGED' 'Don''t set UpdateIdentifier in tuskar plan' 2019-11-29 15:54:13 UTC
Red Hat Product Errata RHSA-2015:1862 0 normal SHIPPED_LIVE Moderate: Red Hat Enterprise Linux OpenStack Platform 7 director update 2015-10-08 16:05:50 UTC

Description Jan Provaznik 2015-07-15 14:07:23 UTC 
Description of problem:
Currently "overcloud stack update" sets and stores UpdateIdentfier param in tuskar plan. If this parameter is not empty, "yum update" is executed on each OC node. The problem is if overcloud stack is deleted and created again with the same tuskar plan - then this parameter is not reset and "yum update" is triggered on OC stack creation which fails.

The simplest solution is to not to save UpdateIdentifier in Tuskar. Upstream patch:
https://review.openstack.org/#/c/202120/
Comment 5 Udi Kalifon 2015-09-07 18:54:10 UTC 
I ran a deployment and failed on a step called UpdateDeployment. On this setup I had a different deployment which I previously deleted (but I never ran an update on the overcloud).

Did I recreate the failure described in this bug or is it something else? How do I know if UpdateIdentifier is set or not, when I'm deploying with the templates (or is this bug not relevant at all if not using tuskar) ?
Comment 6 Jan Provaznik 2015-09-08 06:38:53 UTC 
It is possible that the failure was caused by this bug, but I can not confirm this because of lack of information (no logs, no heat resource info...). To provide more info in this particular case, please attach at least output of:

heat stack-show overcloud
heat resource-list -n 5 overcloud
heat deployment-show <id-of-the-failed-UpdateDeployment>
Comment 7 Udi Kalifon 2015-09-08 11:25:00 UTC 
Verified: openstack-tripleo-common-0.0.1.dev6-2.git49b57eb.el7ost.noarch

Verified when using tuskar and also with the templates. Verified by deploying the cloud, updating it, undeploying and redeploying the same cloud again.
Comment 9 errata-xmlrpc 2015-10-08 12:14:50 UTC 
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/RHSA-2015:1862
Note You need to log in before you can comment on or make changes to this bug.