UnsupportedVersion Endpoint does not support RPC version 6.0 caused because nova.conf misses RPC pinning for RPC 5.12 -> 6.0 PRC jump during Victoria -> Wallaby
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Compute Charm |
Triaged
|
High
|
Unassigned |
Bug Description
Hi,
Environment is:
* Focal-Victoria cloud during upgrade to Focal-Wallaby
* Juju 2.9.45
* All charms were refreshed to their victoria/latest on the 29th of May.
* The juju status --relations output: https:/
* Nova-compute revision after refresh to wallaby/stable is 726
* The sanitized bundle is here: https:/
Cloud is under upgrade from Victoria to Wallaby. I'm doing one by one upgrades.
1. Control plane is all on Wallaby, including nova-cloud-
2. Set `juju config nova-compute action-
3. Refreshed `nova-compute` to 'wallaby/stable'
4. Set `juju config nova-compute openstack-
5. Ran `juju run-action --wait nova-compute/XX openstack-upgrade`
After that I was able to create VMs on new hosts, migrated VMs from them and to them. But, when I tried to migrate a VM from Victoria host, to Wallaby host, I received:
```
$ os server migrate --os-compute-
The --disk-overcommit and --no-disk-
Unexpected API Error. Please report this at http://
<class 'nova.exception
```
In `nova-compute.log` on the target migration host I see (the full trace is here: https:/
```
2024-06-04 12:42:14.900 284516 ERROR oslo_messaging.
```
I checked that `nova-cloud-
```
[upgrade_levels]
compute = auto
```
From the trace, I checked found the line below in `/usr/lib/
```
* 6.0 - Remove 5.x compatibility
```
Unfortunately, nova-compute charm is missing this in its latest template `templates/
The workaround was to add to `templates/
```
[upgrade_levels]
compute = auto
```
and run `juju run -a nova-compute config changed`
Changed in charm-nova-compute: | |
importance: | Undecided → High |
status: | New → Triaged |