This is arguably a bug...the intent of the "system helm-override-update" command was to allow the admin to override system-configured settings.

Chris

On 9/8/2019 6:27 PM, Lin, Shuicheng wrote:

Hi,

For nova-compute, it is due to this configuration is overrides by sysinv in below code.

https://opendev.org/starlingx/config/src/branch/master/sysinv/sysinv/sysinv/sysinv/helm/nova.py#L363

 

 

Best Regards

Shuicheng

 

From: 胡天昊 [mailto:hu.tianhao@99cloud.net]
Sent: Friday, September 6, 2019 2:13 PM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] Fail to change config of nova-compute container

 

Hi guys,

 

Recently I got a problem when I try to change config of nova-compute.After run the the following command :

 

system helm-override-update six-openstack nova openstack --value nova.yml

system application-apply six-openstack

 

I find that config of every container about nova(just like nova-conductor and nova-scheduler) has changed except nova-compute. Here is my nova.yml file.

conf:

  nova:

    libvirt:

      images_type: rbd

I can find 'images_type: rbd' in /etc/nova/nova.conf in every container about nova but in nova-compute I just find 'images_type: default'.

My system is virtual standard with controller storage r2.0 following the guide(https://docs.starlingx.io/deploy_install_guides/current/virtual_controller_storage.html).

I don't understand why this happened. Can anyone give me some help?

 

Thanks

Hu Tianhao

 

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss@lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss