standalone-upgrade-ussuri can't start containers during deployment container-puppet step2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Unassigned |
Bug Description
At [1][2][3] the ussuri gate tripleo-
2020-12-11 05:04:16.226666 | fa163ed5-
...
2020-12-11 05:04:21.501837 | fa163ed5-
2020-12-11 05:04:21.698224 | fa163ed5-
2020-12-11 05:04:21.858922 | fa163ed5-
...
2020-12-11 06:07:05.369731 | fa163ed5-
This is Ussuri gate blocker.
[1] https:/
[2] http://
[3] https:/
tags: | added: promotion-blocker |
description: | updated |
Changed in tripleo: | |
milestone: | none → wallaby-2 |
been digging here for a while... can't find any root cause yet... adding some notes to avoid repeated efforts later:
there are a few errors that are red herrings... using [1] as a reference since it is a green job for example:
0x7f1f78c22898>): [Errno 2] No such file or directory: '/var/log/ validations/ bc 1120-1a3a- 1363-0000000000 08_deploy_ steps_playbook_ 2020-12- 10T18:08: 49.69
764e20-
1685Z.json'
Exception: Deployment failed
The errors.log is empty [2] and I can't find an error in the container outputs [3] that is not also duplicated in the 'good' run [1]
[1] https:/ /7eeddc8c208d72 a47f96- 284a4b285d9a15f afe54e6a481b891 ab.ssl. cf1.rackcdn. com/757821/ 12/check/ tripleo- ci-centos- 8-standalone- upgrade- ussuri/ e0fc8e9/ logs/ /872de5c590dd92 6ff0db- 30e72828a36544d 0c7466f2989d78b fe.ssl. cf1.rackcdn. com/766516/ 1/check/ tripleo- ci-centos- 8-standalone- upgrade- ussuri/ 3072fa1/ logs/undercloud /var/log/ extra/errors. txt.txt /872de5c590dd92 6ff0db- 30e72828a36544d 0c7466f2989d78b fe.ssl. cf1.rackcdn. com/766516/ 1/check/ tripleo- ci-centos- 8-standalone- upgrade- ussuri/ 3072fa1/ logs/undercloud /var/log/ containers/ stdouts/ index.html
[2] https:/
[3] https:/