Changing virt-type is unsupported, config-changed should block and advise via status
Bug #1539489 reported by
Ryan Beisner
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Compute Charm |
Triaged
|
Wishlist
|
Unassigned | ||
nova-compute (Juju Charms Collection) |
Invalid
|
Wishlist
|
Unassigned |
Bug Description
Changing virt-type is unsupported, config-changed should block and advise via status.
Example:
nova-compute is deployed with virt-type=kvm.
User then sets virt-type to something different, such as lxd.
Juju get shows virt-type: lxd, but the charm has otherwise not reacted, and virt-type remains kvm (as it should).
Extended status should advise that the compute node type cannot be changed after deployment.
Changed in nova-compute (Juju Charms Collection): | |
status: | New → Triaged |
importance: | Undecided → Low |
importance: | Low → Wishlist |
tags: | added: openstack sts |
Changed in charm-nova-compute: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
Changed in nova-compute (Juju Charms Collection): | |
status: | Triaged → Invalid |
To post a comment you must log in.
Related fix proposed to branch: master /review. openstack. org/409423
Review: https:/