"metadata_proxy_shared_secret" missmatch after migration ML2+OVS to ML2+OVN
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Compute Charm |
Confirmed
|
High
|
Liam Young |
Bug Description
After migration from ML2+OVS to ML2+OVN there are different values for the metadata_
As a result, I cannot reach the metadata server in a newly created instance. This means, for example, that the ssh key is not created correctly in the instance.
Test:
juju run --application nova-compute 'grep metadata_
- Stdout: |
/etc/
/etc/
UnitId: nova-compute/0
- Stdout: |
/etc/
/etc/
UnitId: nova-compute/1
- Stdout: |
/etc/
/etc/
UnitId: nova-compute/2
Woraround:
I trigger a change in nova-compute charm options, for example debug on/off
juju config nova-compute debug=true
juju config nova-compute debug=false
After this the secrets are correct now:
juju run --application nova-compute 'grep metadata_
- Stdout: |
/etc/
/etc/
UnitId: nova-compute/0
- Stdout: |
/etc/
/etc/
UnitId: nova-compute/1
- Stdout: |
/etc/
/etc/
Changed in charm-nova-compute: | |
status: | Expired → New |
Changed in charm-nova-compute: | |
assignee: | nobody → Liam Young (gnuoy) |
Hi Matthias
Please could you add the following to the bug report:
1. Ubuntu version (as applicable)
2. OpenStack version
3. Charm versions or the pre- and post- bundles.
4. What steps you did migrate from ML2+OVS to ML2+OVN.
5. Log files (if possible) from a nova-compute unit.
Many thanks.