Description of problem: When trying to change something in nova.conf, found out that the old version of conf file is still located on /etc/nova/nova.conf on compute, in addition to the docker conf file. It can be misleading for customer. Version-Release number of selected component (if applicable): python-novaclient-9.1.1-1.el7ost.noarch openstack-nova-scheduler-16.0.2-0.20171023105738.a2e4540.el7ost.noarch puppet-nova-11.4.1-0.20171021210717.26caed8.el7ost.noarch openstack-nova-compute-16.0.2-0.20171023105738.a2e4540.el7ost.noarch openstack-nova-api-16.0.2-0.20171023105738.a2e4540.el7ost.noarch openstack-nova-common-16.0.2-0.20171023105738.a2e4540.el7ost.noarch openstack-nova-novncproxy-16.0.2-0.20171023105738.a2e4540.el7ost.noarch openstack-nova-console-16.0.2-0.20171023105738.a2e4540.el7ost.noarch python-nova-16.0.2-0.20171023105738.a2e4540.el7ost.noarch openstack-nova-migration-16.0.2-0.20171023105738.a2e4540.el7ost.noarch openstack-nova-conductor-16.0.2-0.20171023105738.a2e4540.el7ost.noarch openstack-nova-placement-api-16.0.2-0.20171023105738.a2e4540.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Go to compute 2. Look for nova.conf 3. Actual results: There is a file /etc/nova/nova.conf Expected results: There supposed to be no conf file in /etc/nova Additional info:
Yes the default package provided conf files will be on the host until we no longer install the packages by default. This depends on no longer requiring the installation the openstack packages on the overcloud images. This most likely will be fixed in a future version. I am changing this bug to be a documentation bug for OSP12 as we will need to ensure this is properly documented. There is a future RFE to switch out to use standard RHEL images which may solve this problem, see Bug 1484962.
Due to the hybrid (baremetal and containers) nature of OSP12 we did not remove the RPMs on existing baremetal hosts during install or upgrade. This is something we are implementing for OSP13 and the files should eventually disappear there. Removing select RPMs got a bit tricky as some of the services are still running on baremetal for this release. For OSP13 everything will be in containers so we should safely be able to go in and cleanup a bunch of packages on the baremetal systems.
This Known Issue was included in the Release Notes here - https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/12/html-single/release_notes/#idm139837388030544 Moving to CLOSED.