| *** lbragstad8 is now known as lbragstad | 06:56 | |
| songwenping | bauzas: hi, i have some doubt about nova zed highlight, what is the improvement for 'the possibility to rebuild a volume-backed instance'? | 08:29 |
|---|---|---|
| gibi | songwenping: this is the code we merged to suppot it https://review.opendev.org/q/topic:bp/volume-backed-server-rebuild+status:merged | 08:32 |
| songwenping | is this the API imporvement? | 08:33 |
| songwenping | gibi: i means this feature is not only for API, but include compute modify. | 08:39 |
| gibi | it includes everythin (cinder and nova impacts) that allows reimaging the root volume of a VM booted from that volume | 08:39 |
| gibi | so yes, it is not just an API change | 08:40 |
| songwenping | thanks, got it. and what's the feature for 'the change to only accept importing a public key but also with an extended name pattern'. | 08:42 |
| gibi | that is actually two features. 1) nova stoped supporting generating ssh keys, we only support importing ssh keys. (it is in a new microversion so old microversions still allow generating ssh keys) 2) we extended the list of allowed chars set for the name of the key. Now both @ and . is allowed in the name | 08:44 |
| songwenping | thanks gibi, got it. | 08:52 |
| *** dasm|off is now known as dasm | 12:48 | |
| open10k8s | Hi team, Task_state=deleting VMs don't exist on hypervisors but openstack keeps those list as Active and running. Nova-compute restart solves this but it is only a temporary solution. After delete another machine, same thing happens. I cannot find any error logs from nova services. Is this known issue in a specific condition or any workaround for this? | 16:01 |
| open10k8s | I am running wallaby and never experienced this issue on other clouds with same version | 16:03 |
| melwitt | open10k8s: no, that's not a known issue and it shouldn't be doing that. you are seeing this happen with all delete requests? if the actual VM is gone but the instance still listed, that means that somehow the delete did not reach the DB update to remove the instance record | 16:09 |
| open10k8s | yes, all deletion operation | 16:09 |
| melwitt | I would expect to see some evidence of why in the nova-compute and or nova-conductor logs. are you running logs with debug=True to diagnose? if there's no message in the logs, it will be difficult to find why it's happening | 16:10 |
| open10k8s | i rather tried to find any issues on oslo messaging | 16:10 |
| melwitt | yeah that is a good thing to look for, also the database if there's any issue there when nova-compute attempts to delete the instance record by way of the nova-conductor | 16:11 |
| melwitt | but in both of those cases usually there is an error logged | 16:12 |
| opendevreview | Ghanshyam proposed openstack/os-vif stable/stein: Fix zuul config error for os-vif https://review.opendev.org/c/openstack/os-vif/+/859892 | 19:33 |
| opendevreview | Ghanshyam proposed openstack/os-vif stable/rocky: Fix zuul config error for os-vif https://review.opendev.org/c/openstack/os-vif/+/859893 | 19:38 |
| *** lifeless_ is now known as lifeless | 20:14 | |
| *** tosky_ is now known as tosky | 21:24 | |
| *** dasm is now known as dasm|off | 21:24 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!