[CS9] TripleO CI failing on ovb-manage: find UUID of instance
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Invalid
|
Critical
|
Unassigned |
Bug Description
During a job run for "tripleo-
2022-01-31 14:21:21.412786 | TASK [ovb-manage : Find out UUID of instance with metadata file]
2022-01-31 09:21:22.248316 | primary | Traceback (most recent call last):
2022-01-31 09:21:22.248423 | primary | File "<string>", line 1, in <module>
2022-01-31 09:21:22.248439 | primary | File "/usr/lib64/
2022-01-31 09:21:22.248443 | primary | return loads(fp.read(),
2022-01-31 09:21:22.248448 | primary | File "/usr/lib64/
2022-01-31 09:21:22.248452 | primary | return _default_
2022-01-31 09:21:22.248457 | primary | File "/usr/lib64/
2022-01-31 09:21:22.248534 | primary | obj, end = self.raw_decode(s, idx=_w(s, 0).end())
2022-01-31 09:21:22.248542 | primary | File "/usr/lib64/
2022-01-31 09:21:22.248609 | primary | raise JSONDecodeError
2022-01-31 09:21:22.248615 | primary | json.decoder.
2022-01-31 14:21:22.493259 | primary | ERROR
[1]: https:/
[2]: https:/
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → Critical |
milestone: | none → yoga-2 |
summary: |
- TripleO CI failing on ovb-manage: find UUID of instance + [CS9] TripleO CI failing on ovb-manage: find UUID of instance |
Not a bug. Misread logs.