[Starlingx-discuss] Fail to change config of nova-compute container
chris.friesen at windriver.com
Mon Sep 9 15:51:28 UTC 2019
This is arguably a bug...the intent of the "system helm-override-update"
command was to allow the admin to override system-configured settings.
On 9/8/2019 6:27 PM, Lin, Shuicheng wrote:
> For nova-compute, it is due to this configuration is overrides by
> sysinv in below code.
> Best Regards
> *From:*胡天昊[mailto:hu.tianhao at 99cloud.net]
> *Sent:* Friday, September 6, 2019 2:13 PM
> *To:* starlingx-discuss at lists.starlingx.io
> *Subject:* [Starlingx-discuss] Fail to change config of nova-compute
> 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.
> 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:
> My system is virtual standard with controller storage r2.0 following
> I don't understand why this happened. Can anyone give me some help?
> Hu Tianhao
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Starlingx-discuss