dynamic setting of pci-alias using juju config nova-compute command will not propagate to nova.cfg on nova-cloud-controller unit

Bug #1998496 reported by Itai Levy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Nova Compute Charm
Invalid
Undecided
Unassigned

Bug Description

Canonical Charmed Openstack platform
Jammy OS
Openstack Yoga

After cloud was deployed, I tried to dynamically set nova alias using the command:

juju config nova-compute pci-alias='[{"vendor_id":"10de","product_id":"20f1","name":"a100-gpu","device_type":"type-PF"}]'

I could see the new entry in nova.conf on the nova-compute nodes, however the new configuration didn't propagated into nova.conf in the nova-cloud-controller unit container.
I had to ssh into it, manually edit the nova.conf and restart the services to apply the new config.

Revision history for this message
Itai Levy (etlvnvda) wrote :

I see there is pci-alias also for nova-cloud-controller...
closing.

Changed in charm-nova-compute:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.