Bug 973328 - nova doesn't output error to log when fails on parsing plugin conf
Summary: nova 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-nova
Version: 3.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: 4.0
Assignee: RHOS Maint
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On: 972359 973333
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-11 17:05 UTC by Jaroslav Henner
Modified: 2019-09-09 14:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 972359
Environment:
Last Closed: 2013-06-11 17:19:40 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jaroslav Henner 2013-06-11 17:05:57 UTC
+++ This bug was initially created as a clone of Bug #972359 +++

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:

--- Additional comment from Ryan O'Hara on 2013-06-11 02:33:32 CEST ---

How did you install? Can you attach the plugin.ini file?

--- Additional comment from Jaroslav Henner on 2013-06-11 14:22:19 CEST ---

(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 1 Jaroslav Henner 2013-06-11 17:19:40 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.