yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #61912
[Bug 1668958] [NEW] metadata service occasionally not returning keys
Public bug reported:
Occasionally we are getting failures like this in the Linux Bridge job
in Neutron:
2017-02-28 11:50:22,162 12602 WARNING [tempest.lib.common.ssh] Failed
to establish authenticated ssh connection to cirros@172.24.5.17 (Error
reading SSH protocol banner). Number attempts: 16. Retry after 17
seconds.
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.
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1668958
Title:
metadata service occasionally not returning keys
Status in OpenStack Compute (nova):
New
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.lib.common.ssh] Failed
to establish authenticated ssh connection to cirros@172.24.5.17 (Error
reading SSH protocol banner). Number attempts: 16. Retry after 17
seconds.
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1668958/+subscriptions
Follow ups