Bug 970500
Summary: | quantum server log errors post installation. | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Nir Magnezi <nmagnezi> |
Component: | openstack-neutron | Assignee: | Jakub Libosvar <jlibosva> |
Status: | CLOSED WORKSFORME | QA Contact: | Ofer Blaut <oblaut> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 3.0 | CC: | chrisw, jkt, jlibosva, lpeer |
Target Milestone: | --- | ||
Target Release: | 4.0 | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-11-24 13:27:08 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nir Magnezi
2013-06-04 07:50:04 UTC
After further discussion with Ofer it seems like this has no functionality impact. The exceptions are there because the different processes are not in sync, after the processes go up the exceptions stop. Leaving this as a low priority bug as the logs are not clean and for someone who is not familiar with the product it can appear like there is an error. Does it happen always after installation? I cannot reproduce that. How important is mentioned packstack answer file configuration? The bug no longer reproduce. # rpm -qa| grep quantum python-quantumclient-2.2.1-2.el6ost.noarch python-quantum-2013.1.4-3.el6ost.noarch openstack-quantum-openvswitch-2013.1.4-3.el6ost.noarch openstack-quantum-2013.1.4-3.el6ost.noarch I installed Openstack via packstack [1], an all-in-one installation. I compared and found some differences in quantum configuration files (compared the ones I attached to the bug with the newly created config files) Difference #1: quantum.conf: only the old file contains the line: root_helper=sudo quantum-rootwrap /etc/quantum/rootwrap.conf quantum.conf: only the new file contains the line: qpid_reconnect=True Does not seem like nothing major. Difference #2: When I filed this BZ, namespaces where disabled by default. now the default value is to enable namespaces. This change is expressed in quantum configuration files, but since we no longer work without namespaces, There is no point in trying that configuration. Closing the bug. [1] openstack-packstack-2013.1.1-0.35.dev696.el6ost.noarch |