Comment 9 for bug 1880509
Revision history for this message
| Balazs Gibizer (balazs-gibizer) wrote | #9 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Could be a cinder - nova, FQDN - non-FQDN config mismatch but it is hard to tell.
Another angle to tackle this is by dissecting the stack trace:
So the error happens here[1]. The None condition can happen if there was a host_down without a host_up or if there was no host_up since __init__. Both host_up and down is called from the libvirt driver [2]. This code has debug log statements so we might be able to understand the situation better from the logs.
@Alphh23:
Do you have debug logs from nova-compute service?
Can you reproduce the problem and collect such logs?
Does a nova-compute service restart resolve the problem?
Does a compute host reboot resolves the problem?
Does a
$ openstack compute service set <host> <service> --disable
$ openstack compute service set <host> <service> --enable
resolves the problem?
Setting the nova bug Incomplete until for now but please set it back to New when you provided the requested information.
[1] https:/
[2] https:/