deploy succeeded but no overcloudrc was generated

[Michele Baldessari]

We seem to be hitting a problem where the deploy succeeds:
http://logs.openstack.org/19/447319/2/check/gate-tripleo-ci-centos-7-nonha-multinode-oooq/5ea42f4/logs/undercloud/home/jenkins/overcloud_deploy.log.txt.gz#_2017-03-24_08_25_15_993619

But then we fail the validate because there is no overcloudrc:
http://logs.openstack.org/19/447319/2/check/gate-tripleo-ci-centos-7-nonha-multinode-oooq/5ea42f4/logs/undercloud/home/jenkins/overcloud_validate.log.txt.gz

We have seen this on a couple of jobs now. Another occurrence was here:
http://logs.openstack.org/87/446887/1/gate/gate-tripleo-ci-centos-7-nonha-multinode-oooq/cf58322/logs/undercloud/home/jenkins/overcloud_validate.log.txt.gz

[Dougal Matthews (d0ugal)]

This really interesting thing about this error is that while the deploy command finishes with status_code 0, it doesn't fully finish.

You can see this because neither of these print statements happen:

https://github.com/openstack/python-tripleoclient/blob/master/tripleoclient/v1/overcloud_deploy.py#L1170-L1171

So, somewhere in this block of code it is exiting early:

https://github.com/openstack/python-tripleoclient/blob/master/tripleoclient/v1/overcloud_deploy.py#L1141-L1169

I opened this patch to rule one of them out (although I don't think it is this one anyway): https://review.openstack.org/#/c/449491/

---

so the question is where, why and how the command exits early and without an error. I have not found anywhere that looks possible yet - but I'll keep digging.

[Dougal Matthews (d0ugal)]

Another case of it here: http://logs.openstack.org/48/446348/4/check/gate-tripleo-ci-centos-7-nonha-multinode-oooq/d4ea9f3/logs/undercloud/home/jenkins/overcloud_deploy.log.txt.gz#_2017-03-24_11_20_31_265890

This one seems a little different, there is more output after the create success/fail message.

[Ben Nemec (bnemec)]

Is this still happening?

[Brent Eagles (beagles)]

while deployment has changed substantially since this was reported, I'm seeing it with config download deployments in rocky. There doesn't seem to be any error just a message after the PLAY RECAP stating "Connection is already closed."

[Brent Eagles (beagles)]

I later discovered that my environment that was exhibiting this behavior on 2018-05-05 was messed.

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE