yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #02017
[Bug 1107950] Re: Quantum L3 agent is using /usr/share/pyshared for locking
** Changed in: oslo/grizzly
Importance: Undecided => High
** Changed in: oslo/grizzly
Status: New => Fix Released
** Changed in: oslo/grizzly
Milestone: None => 2013.1
** Changed in: oslo/grizzly
Assignee: (unassigned) => Jason Kölker (jason-koelker)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.net/bugs/1107950
Title:
Quantum L3 agent is using /usr/share/pyshared for locking
Status in Oslo - a Library of Common OpenStack Code:
Fix Released
Status in oslo grizzly series:
Fix Released
Status in OpenStack Quantum (virtual network service):
Fix Released
Bug description:
2013-01-28 15:35:21.702 734 DEBUG quantum.agent.linux.utils [-] Running command: ['sudo', '/usr/bin/quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'ip', 'netns', 'exec', 'qrouter-a4c9fef2-eea2-4a9a-b5b1-53c86b188a16', 'sysctl', '-w', 'net.ipv4.ip_forward=1'] execute /usr/lib/python2.7/dist-packages/quantum/agent/linux/utils.py:41
2013-01-28 15:35:21.853 734 DEBUG quantum.agent.linux.utils [-]
Command: ['sudo', '/usr/bin/quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'ip', 'netns', 'exec', 'qrouter-a4c9fef2-eea2-4a9a-b5b1-53c86b188a16', 'sysctl', '-w', 'net.ipv4.ip_forward=1']
Exit code: 0
Stdout: 'net.ipv4.ip_forward = 1\n'
Stderr: '' execute /usr/lib/python2.7/dist-packages/quantum/agent/linux/utils.py:58
2013-01-28 15:35:21.855 734 DEBUG quantum.openstack.common.lockutils [-] Got semaphore "iptables" for method "_apply"... inner /usr/lib/python2.7/dist-packages/quantum/openstack/common/lockutils.py:186
2013-01-28 15:35:21.856 734 DEBUG quantum.openstack.common.lockutils [-] Attempting to grab file lock "iptables" for method "_apply"... inner /usr/lib/python2.7/dist-packages/quantum/openstack/common/lockutils.py:190
2013-01-28 15:35:21.857 734 DEBUG quantum.openstack.common.lockutils [-] Released file lock "iptables" at /usr/lib/python2.7/dist-packages/quantum/openstack/quantum-iptables for method "_apply"... inner /usr/lib/python2.7/dist-packages/quantum/openstack/common/lockutils.py:227
2013-01-28 15:35:21.858 734 ERROR quantum.agent.l3_agent [-] Failed synchronizing routers
2013-01-28 15:35:21.858 734 TRACE quantum.agent.l3_agent Traceback (most recent call last):
2013-01-28 15:35:21.858 734 TRACE quantum.agent.l3_agent File "/usr/lib/python2.7/dist-packages/quantum/agent/l3_agent.py", line 603, in _sync_routers_task
2013-01-28 15:35:21.858 734 TRACE quantum.agent.l3_agent self._process_routers(routers)
2013-01-28 15:35:21.858 734 TRACE quantum.agent.l3_agent File "/usr/lib/python2.7/dist-packages/quantum/agent/l3_agent.py", line 584, in _process_routers
2013-01-28 15:35:21.858 734 TRACE quantum.agent.l3_agent self._router_added(r['id'])
2013-01-28 15:35:21.858 734 TRACE quantum.agent.l3_agent File "/usr/lib/python2.7/dist-packages/quantum/agent/l3_agent.py", line 228, in _router_added
2013-01-28 15:35:21.858 734 TRACE quantum.agent.l3_agent ri.iptables_manager.apply()
2013-01-28 15:35:21.858 734 TRACE quantum.agent.l3_agent File "/usr/lib/python2.7/dist-packages/quantum/agent/linux/iptables_manager.py", line 291, in apply
2013-01-28 15:35:21.858 734 TRACE quantum.agent.l3_agent self._apply()
2013-01-28 15:35:21.858 734 TRACE quantum.agent.l3_agent File "/usr/lib/python2.7/dist-packages/quantum/openstack/common/lockutils.py", line 215, in inner
2013-01-28 15:35:21.858 734 TRACE quantum.agent.l3_agent with lock:
2013-01-28 15:35:21.858 734 TRACE quantum.agent.l3_agent File "/usr/lib/python2.7/dist-packages/quantum/openstack/common/lockutils.py", line 75, in __enter__
2013-01-28 15:35:21.858 734 TRACE quantum.agent.l3_agent self.lockfile = open(self.fname, 'w')
2013-01-28 15:35:21.858 734 TRACE quantum.agent.l3_agent IOError: [Errno 13] Permission denied: '/usr/lib/python2.7/dist-packages/quantum/openstack/quantum-iptables'
2013-01-28 15:35:21.858 734 TRACE quantum.agent.l3_agent
gonysh @ freenode had the same problem with the lock occuring in the lib dir instead of in say /var/lock or /var/X...
Is this intentional during development or?
To manage notifications about this bug go to:
https://bugs.launchpad.net/oslo/+bug/1107950/+subscriptions