Description of problem:
If you run openstack overcloud deploy with &> logfile, the process goes into the background. This results in the deployment hanging on one of the last steps in postdeployment, and the endpoints and security settings don't get completed.
Version-Release number of selected component (if applicable):
OSP 7 GA (probably affects Director 7.1 as well)
Steps to Reproduce:
1. Run the openstack overcloud deploy in the background
The stack gets to CREATE_COMPLETE, but in the postdeployment steps the script will hang.
The postdeployment should complete.
When the script was in this state, ps showed it as "stopped". When we foregrounded the process, the postdeployment immediately completed and the endpoints and security for the admin user was set up. This *might* have something to do with an SSH call requiring a TTY, but definitely only works when the process is in the foreground. This causes a lot of confusion, since the stack goes to CREATE_COMPLETE but the overcloud is not functional.
A simple workaround is just to make sure that the overcloud deploy process happens in the foreground. The output can be piped to tee to write it to a log file while keeping it in the foreground.
Hi, I've put together a patchset to resolve this upstream - it's somewhat large so I'd want to put together a less invasive set of patches if we want this to make it into y2.
I'm aware of this happening in at least a couple of instances, but I also have a report that someone was able to deploy successfully with the process in the background, so it appears this isn't 100% reproducible. Still unclear what the cause is.
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
Note that this may be fixed in OSP 10, since we don't do post-deployment over ssh anymore.
*** Bug 1329343 has been marked as a duplicate of this bug. ***
I couldn't reproduce it for a while and personally I always deploy to the background.
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.
This did not show up in my doc-text query so I missed it. Adding it now in case it's still useful.