Description of problem: service neutron-ovs-cleanup start. The error is unable to read plugin.ini which is a link to /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini : # systemctl status neutron-ovs-cleanup.service neutron-ovs-cleanup.service - OpenStack Neutron Open vSwitch Cleanup Utility Loaded: loaded (/usr/lib/systemd/system/neutron-ovs-cleanup.service; disabled) Active: failed (Result: exit-code) since Tue 2014-03-25 09:07:37 IST; 43s ago Process: 13798 ExecStart=/usr/bin/neutron-ovs-cleanup --config-file /usr/share/neutron/neutron-dist.conf --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini --log-file /var/log/neutron/ovs-cleanup.log (code=exited, status=1/FAILURE) Main PID: 13798 (code=exited, status=1/FAILURE) Mar 25 09:07:37 puma36.scl.lab.tlv.redhat.com neutron-ovs-cleanup[13798]: File "/usr/bin/neutron-ovs-cleanup", line 10, in <module> Mar 25 09:07:37 puma36.scl.lab.tlv.redhat.com neutron-ovs-cleanup[13798]: sys.exit(main()) Mar 25 09:07:37 puma36.scl.lab.tlv.redhat.com neutron-ovs-cleanup[13798]: File "/usr/lib/python2.7/site-packages/neutron/agent/ovs_cleanup_util.py", line 85, in main Mar 25 09:07:37 puma36.scl.lab.tlv.redhat.com neutron-ovs-cleanup[13798]: conf() Mar 25 09:07:37 puma36.scl.lab.tlv.redhat.com neutron-ovs-cleanup[13798]: File "/usr/lib/python2.7/site-packages/oslo/config/cfg.py", line 1599, in __call__ Mar 25 09:07:37 puma36.scl.lab.tlv.redhat.com neutron-ovs-cleanup[13798]: raise ConfigFilesNotFoundError(self._namespace.files_not_found) Mar 25 09:07:37 puma36.scl.lab.tlv.redhat.com neutron-ovs-cleanup[13798]: oslo.config.cfg.ConfigFilesNotFoundError: Failed to read some config files: /etc/neutr...gin.ini Mar 25 09:07:37 puma36.scl.lab.tlv.redhat.com systemd[1]: neutron-ovs-cleanup.service: main process exited, code=exited, status=1/FAILURE Mar 25 09:07:37 puma36.scl.lab.tlv.redhat.com systemd[1]: Failed to start OpenStack Neutron Open vSwitch Cleanup Utility. Mar 25 09:07:37 puma36.scl.lab.tlv.redhat.com systemd[1]: Unit neutron-ovs-cleanup.service entered failed state. Hint: Some lines were ellipsized, use -l to show in full. Version-Release number of selected component (if applicable): # yum whatprovides neutron-ovs-cleanup openstack-neutron-openvswitch-2014.1-0.1.b1.fc21.noarch : Neutron openvswitch plugin Repo : openstack-icehouse How reproducible: Always Steps to Reproduce: Provision a Fedora20 machine yum upgrade && reboot yum install http://rdo.fedorapeople.org/openstack-icehouse/rdo-release-icehouse.rpm install packstack run packstack all in one Actual results: neutron puppet failed Expected results: neutron puppet won't fail Additional info: workaround: unlink /etc/neutron/plugin.ini && cp /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini /etc/neutron/plugin.in
The config reader doesn't do any link-checking or equivalent. So I can only think of file permissions on the original file. Could you check the file permissions/uid/gid on /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini ? It has to be accessible for neutron uid or gid.
(from ls -l) it was a link like any other link: lrwxrwxrwx 1 root root 55 Mar 25 09:19 /etc/neutron/plugin.ini -> /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini the target file permissions: -rw-r----- 1 root neutron 6382 Mar 25 08:58 /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini I copied the file ovs_neutron_plugin.ini on top of plugin.ini and it worked.
*** This bug has been marked as a duplicate of bug 1080560 ***
Why is this a duplicate? in https://bugzilla.redhat.com/show_bug.cgi?id=1080560 the bug says that the configuration file should be under group neutron. in this bug the file _is_ under that group. There is no problem to read that file by neutron. The problem was that it failed to read the link to it. once it was a file and not a link there were no issues.
(In reply to Amit Ugol from comment #4) > Why is this a duplicate? > in https://bugzilla.redhat.com/show_bug.cgi?id=1080560 the bug says that the > configuration file should be under group neutron. in this bug the file _is_ > under that group. There is no problem to read that file by neutron. The > problem was that it failed to read the link to it. once it was a file and > not a link there were no issues. You're right. Reopening. Is it reproducible? I tried on my env and it works. Are you sure you haven't ran packstack more than once (based on the time of created link and config file: 08:58 09:19).
Amit you said packstack worked on the third try. So is this still a bug or is it no longer triggerable due to bug 1080560 being fixed?
It is a bug that happened to me once .The 3rd time it worked was AFTER I unlinked the file and copied it physically. Is it a bug? sure it is, OpenStack failing to install in the simplest way possible looks very bad, but due to the fact it did not reproduce later I think it can have the lowest priority. If no one will encounter this bug again, then I think it will be safe to close it.
I believe this problem is actually solved by pbrady's fix in bug 1080560. I'm going to go ahead and close this as being fixed in openstack-neutron-2014.1-0.13.rc1. Amit, if you run into the problem again in the latest builds, please feel free to re-open.