metadata service occasionally not returning keys
Bug #1668958 reported by
Kevin Benton
This bug affects 10 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Critical
|
Kevin Benton |
Bug Description
Occasionally we are getting failures like this in the Linux Bridge job in Neutron:
2017-02-28 11:50:22,162 12602 WARNING [tempest.
I traced it down to the VM not getting keys back from the metadata service even though it has a keypair configured. The request makes it over to Nova metadata with the relevant instance ID but no keys are being returned.
no longer affects: | nova |
Changed in neutron: | |
status: | New → In Progress |
assignee: | nobody → Kevin Benton (kevinbenton) |
importance: | Undecided → Critical |
tags: | added: gate-failure ocata-backport-potential |
tags: | added: neutron-proactive-backport-potential |
tags: | added: neutron-easy-proactive-backport-potential |
tags: | removed: neutron-easy-proactive-backport-potential neutron-proactive-backport-potential ocata-backport-potential |
To post a comment you must log in.
http:// logstash. openstack. org/#dashboard/ file/logstash. json?query= message% 3A%5C%22( Error%20reading %20SSH% 20protocol% 20banner) .%20Number% 20attempts% 3A%2016% 5C%22