Bug 968965
Summary: | quantum-metadata-agent is not run with the configuration file /usr/share/quantum/quantum-dist.conf | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Gary Kotton <gkotton> |
Component: | openstack-quantum | Assignee: | Gary Kotton <gkotton> |
Status: | CLOSED ERRATA | QA Contact: | yfried |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.0 | CC: | chrisw, jturner, sgordon, ykaul |
Target Milestone: | snapshot2 | Keywords: | Triaged |
Target Release: | 3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-quantum-2013.1.1-9.el6ost | Doc Type: | Bug Fix |
Doc Text: |
The initialization script for the OpenStack Networking metadata service was starting the service with arguments that did not include distribution specific configuration file /usr/share/quantum/quantum-dist.conf. As a result the service was previously being started with incorrect default configuration values set. The initialization script has been updated and now starts the metadata service with arguments that include the distribution specific configuration file.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-06-11 18:56:50 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
Gary Kotton
2013-05-30 11:32:10 UTC
diff --git a/quantum-metadata-agent.init b/quantum-metadata-agent.init index e6f146f..f930e19 100644 --- a/quantum-metadata-agent.init +++ b/quantum-metadata-agent.init @@ -23,7 +23,7 @@ start() { [ -x $exec ] || exit 5 [ -f $config ] || exit 6 echo -n $"Starting $prog: " - daemon --user quantum --pidfile $pidfile "$exec --log-file /var/log/$proj/$plugin.log --config-file /etc/$proj/$proj.conf --config-file $config &>/dev/null & echo \$! > $pidfile" + daemon --user quantum --pidfile $pidfile "$exec --log-file /var/log/$proj/$plugin.log --config-file /usr/share/$proj/$proj-dist.conf --config-file /etc/$proj/$proj.conf --config-file $config &>/dev/null & echo \$! > $pi retval=$? echo [ $retval -eq 0 ] && touch $lockfile diff --git a/quantum-metadata-agent.init b/quantum-metadata-agent.init index e6f146f..f930e19 100644 --- a/quantum-metadata-agent.init +++ b/quantum-metadata-agent.init @@ -23,7 +23,7 @@ start() { [ -x $exec ] || exit 5 [ -f $config ] || exit 6 echo -n $"Starting $prog: " - daemon --user quantum --pidfile $pidfile "$exec --log-file /var/log/$proj/$plugin.log --config-file /etc/$proj/$proj.conf --config-file $config &>/dev/null & echo \$! > $pidfile" + daemon --user quantum --pidfile $pidfile "$exec --log-file /var/log/$proj/$plugin.log --config-file /usr/share/$proj/$proj-dist.conf --config-file /etc/$proj/$proj.conf --config-file $config &>/dev/null & echo \$! > $pidfile" retval=$? echo [ $retval -eq 0 ] && touch $lockfile diff --git a/quantum-metadata-agent.upstart b/quantum-metadata-agent.upstart index c11261b..9f51395 100644 --- a/quantum-metadata-agent.upstart +++ b/quantum-metadata-agent.upstart @@ -6,4 +6,4 @@ stop on runlevel [S016] respawn -exec su -s /bin/sh -c "exec /usr/bin/quantum-metadata-agent --config-file /etc/quantum/quantum.conf --config-file /etc/quantum/metadata_agent.ini --log-file /var/log/quantum/metadata-agent.log" quantum +exec su -s /bin/sh -c "exec /usr/bin/quantum-metadata-agent --config-file /usr/share/quantum/quantum-dist.conf --config-file /etc/quantum/quantum.conf --config-file /etc/quantum/metadata_agent.ini --log-file /var/log/quantum/metadata-agent.log" quantum Hi Gary Please add more details on what to test Ofer # quantum --version quantum 2.0 # ps aux | grep quantum quantum 21994 0.0 0.0 261460 26576 ? S Jun03 0:00 python /usr/bin/quantum-metadata-agent --log-file /var/log/quantum/metadata-agent.log --config-file /usr/share/quantum/quantum-dist.conf --config-file /etc/quantum/quantum.conf --config-file /etc/quantum/metadata_agent.ini Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0933.html |