Bug 1324445

Summary:	Update command for the overcloud exits with status COMPLETE even if the update has just started
Product:	Red Hat OpenStack	Reporter:	Raoul Scarazzini <rscarazz>
Component:	python-tripleoclient	Assignee:	Julie Pichon <jpichon>
Status:	CLOSED WONTFIX	QA Contact:	Ola Pavlenko <opavlenk>
Severity:	low	Docs Contact:
Priority:	low
Version:	7.0 (Kilo)	CC:	achernet, beth.white, dbecker, hbrock, jcoufal, jrist, jslagle, mburns, morazi, rhel-osp-director-maint
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	11.0 (Ocata)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-02 16:14:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Raoul Scarazzini 2016-04-06 10:51:55 UTC

Description of problem:

While updating Overcloud the update starts and seems to end in a while:

[stack@macb8ca3a66dcd8 ~]$ time openstack overcloud update stack overcloud --templates -e /usr/share/openstack-tripleo-heat-templates/environments/puppet-pacemaker.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml -e /home/stack/network-environment.yaml -e /home/stack/custom-env.yaml
starting package update on stack overcloud
stack overcloud status: COMPLETE

but the message related to the overcloud is somehow wrong, since at this point the update is just started.

So the command should wait to exit or report a different message.

Version-Release number of selected component (if applicable):

openstack-tripleo-0.0.7-0.1.1664e566.el7ost.noarch

How reproducible:

Just launch an update to an existing overcloud environment.

Comment 2 Mike Burns 2016-04-06 12:10:56 UTC

Please use rhel-osp-director for generic bugs against director.

Comment 3 Raoul Scarazzini 2016-04-06 14:58:13 UTC

Sorry for the mistake Mike, will take care of your suggestion in the future.

In the meantime I find out two issues that maybe already related to this topic, one upstream [1] and one downstream [2].

[1] https://review.openstack.org/#/c/275149/
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1308309

Comment 4 Jason E. Rist 2016-10-14 22:26:39 UTC

Is this still an issue?

Comment 5 Raoul Scarazzini 2016-10-18 08:26:02 UTC

Hi Jason,
yes, as I see from here [1] this is still an issue, but unfortunately I don't have enough time slots right now to reproduce it.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1384246

Comment 6 Beth White 2018-02-02 16:14:25 UTC

Since this has a negative pm score and the target release is nearing end of life, we are closing this bug.