CI job 'grenade-py3' broken
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
grenade |
Invalid
|
Undecided
|
Unassigned | ||
tempest |
Invalid
|
Undecided
|
Unassigned |
Bug Description
The log as below:
020-03-05 15:42:17.659948 | primary | Captured traceback:
2020-03-05 15:42:17.659954 | primary | ~~~~~~~~~~~~~~~~~~~
2020-03-05 15:42:17.659961 | primary | Traceback (most recent call last):
2020-03-05 15:42:17.659967 | primary | File "/opt/stack/
2020-03-05 15:42:17.659974 | primary | six.reraise(etype, value, trace)
2020-03-05 15:42:17.659980 | primary | File "/opt/stack/
2020-03-05 15:42:17.659986 | primary | raise value
2020-03-05 15:42:17.659993 | primary | File "/opt/stack/
2020-03-05 15:42:17.659999 | primary | cls.resource_
2020-03-05 15:42:17.660010 | primary | File "/opt/stack/
2020-03-05 15:42:17.660017 | primary | cls.server_id = cls.recreate_
2020-03-05 15:42:17.660023 | primary | File "/opt/stack/
2020-03-05 15:42:17.660030 | primary | **kwargs)
2020-03-05 15:42:17.660036 | primary | File "/opt/stack/
2020-03-05 15:42:17.660042 | primary | **kwargs)
2020-03-05 15:42:17.660049 | primary | File "/opt/stack/
2020-03-05 15:42:17.660055 | primary | server['id'])
2020-03-05 15:42:17.660062 | primary | File "/opt/stack/
2020-03-05 15:42:17.660068 | primary | self.force_
2020-03-05 15:42:17.660074 | primary | File "/opt/stack/
2020-03-05 15:42:17.660081 | primary | six.reraise(
2020-03-05 15:42:17.660087 | primary | File "/opt/stack/
2020-03-05 15:42:17.660094 | primary | raise value
2020-03-05 15:42:17.660100 | primary | File "/opt/stack/
2020-03-05 15:42:17.660108 | primary | clients.
2020-03-05 15:42:17.660121 | primary | File "/opt/stack/
2020-03-05 15:42:17.660133 | primary | server_
2020-03-05 15:42:17.660146 | primary | tempest.
2020-03-05 15:42:17.660154 | primary | Details: {'code': 500, 'created': '2020-03-
Changed in tempest: | |
status: | New → Invalid |
Is this related to tempest? shouldn't this be opened against granade or infra?