This bug effects me whenever I try to launch an instance. The instance
starts the "Scheduling" process and hangs. If I change the connection
URL to an invalid one it gives an error that does not allow the instance
to enter the "Scheduling" state. The communication seems to be
functional as when I
Unfortunately, this doesn't look a Nova issue : this is either an
oslo.messaging bug or rather a configuration issue.
Closing this bug for Nova.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
** Also affects: oslo.messaging
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/1968054
Title:
3 matches
Mail list logo