KeyError: key 'networks' does not exist in response body
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Fix Released
|
Medium
|
Ghanshyam Mann |
Bug Description
In case tempest.
https:/
However, it reported KeyError that there is no key "networks" in the response body from booting instance. Refer to Openstack API doc: http://
"networks" does not exist.
{
"server": {
{
}
]
},
"created": "2012-08-
"flavor": {
"id": "1",
{
}
]
},
"hostId": "65201c14a29663
"id": "893c7791-
"image": {
"id": "70a599e0-
{
}
]
},
"links": [
{
},
{
}
],
"metadata": {
"My Server Name": "Apache1"
},
"name": "new-server-test",
"progress": 0,
"status": "ACTIVE",
"updated": "2012-08-
"user_id": "fake"
}
}
Changed in tempest: | |
importance: | High → Medium |
Changed in tempest: | |
assignee: | nobody → Ghanshyam Mann (ghanshyammann) |
Yes this is issue.
Actually this was introduced while doing scenario manager migration to tempest client.
IP should be fetched from server['addresses']
This was not caught anywhere as none of gate job run tests with tenant_ networks_ reachable= True