Bug 972359 - quantum-server doesn't output error to log when fails on parsing plugin conf
Summary: quantum-server doesn't output error to log when fails on parsing plugin conf
Keywords:
Status: CLOSED DUPLICATE of bug 973333
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-quantum
Version: 3.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: 3.0
Assignee: Gary Kotton
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks: 973328 973333
TreeView+ depends on / blocked
 
Reported: 2013-06-08 20:43 UTC by Jaroslav Henner
Modified: 2016-04-27 00:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 972360 973328 973333 (view as bug list)
Environment:
Last Closed: 2013-06-11 17:19:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 972360 0 urgent CLOSED linuxbridge config contains value without option 2021-02-22 00:41:40 UTC

Internal Links: 972360

Description Jaroslav Henner 2013-06-08 20:43:42 UTC
Description of problem:
quantum fails and there is nothing in the log

if there is 
[SECURITYGROUP]
# Firewall driver for realizing quantum security group function
quantum.agent.linux.iptables_firewall.IptablesFirewallDriver

in the /etc/quantum/plugin.ini, then quantum doesn't start and doesn't output anything to server.log


Version-Release number of selected component (if applicable):
openstack-quantum-2013.1.1-10.el6ost.noarch
openstack-quantum-linuxbridge-2013.1.1-10.el6ost.noarch


How reproducible:
always


Steps to Reproduce:
1. change the config accordingly to description
2. restart quantum-server
3.

Actual results:
quantum is dead, nothing in log.

Expected results:
error in log

Additional info:

Comment 1 Ryan O'Hara 2013-06-11 00:33:32 UTC
How did you install? Can you attach the plugin.ini file?

Comment 2 Jaroslav Henner 2013-06-11 12:22:19 UTC
(In reply to Ryan O'Hara from comment #1)
> How did you install? Can you attach the plugin.ini file?

With broken Packstack (see the referred clone of this bug), but you can simulate it without the packstack, with the RPMs for sure. Obviously, the bug won't appear with Devstack because Devstack IMHO doesn't use the init scripts.

I don't have that config, but you should be able to reproduce it:

[root@master-02 ~]# echo 'I am evil as hell.' >> /etc/quantum/plugin.ini 
[root@master-02 ~]# tail -fn0 /var/log/quantum/linuxbridge-agent.log &
[2] 16976
[root@master-02 ~]# /etc/init.d/quantum-linuxbridge-agent restart
Stopping quantum-linuxbridge-agent:                        [  OK  ]
Starting quantum-linuxbridge-agent:                        [  OK  ]
[root@master-02 ~]# /etc/init.d/quantum-linuxbridge-agent status
quantum-linuxbridge-agent dead but pid file exists
[root@master-02 ~]# kill %
[root@master-02 ~]# 

See? No message. Only death.

Comment 3 Jaroslav Henner 2013-06-11 17:19:51 UTC

*** This bug has been marked as a duplicate of bug 973333 ***


Note You need to log in before you can comment on or make changes to this bug.