Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1343233

Summary: [RFE] Add capability to re-run deployment and skip steps which finished successfuly
Product: Red Hat OpenStack Reporter: Matt Flusche <mflusche>
Component: openstack-tripleo-heat-templatesAssignee: Emilien Macchi <emacchi>
Status: CLOSED ERRATA QA Contact: Gurenko Alex <agurenko>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0 (Liberty)CC: ahrechan, aschultz, dbecker, jcoufal, jjoyce, jslagle, mburns, morazi, rhel-osp-director-maint
Target Milestone: Upstream M2Keywords: FutureFeature, Triaged
Target Release: 14.0 (Rocky)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-9.0.0-0.20180710202746.d2994ca.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-11 11:47:00 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1615694    

Description Matt Flusche 2016-06-06 21:30:41 UTC 
Description of problem:

Add the ability to run the Overcloud post configuration steps in a stand-alone mode.

Many Overcloud deployments fail in the post deployment steps (After the heat deployment has completed successfully).  This occurs often due to network connectivity between Director and the Overcloud's public Keystone API endpoint. Having a quick way to complete the Overcloud installation without re-running the entire deployment would be very helpful.

Additional, often the Overcloud's heat stack_status is used to determine the entire deployments status.  Having a quick way to verify the post configuration status also would help close this gap.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 16 Artem Hrechanychenko 2018-11-29 07:49:17 UTC 
VERIFIED
Comment 18 errata-xmlrpc 2019-01-11 11:47:00 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/RHEA-2019:0045