RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1088537 - rhel 6.5 icehouse stage.. neutron-db-manage trying to import systemd
Summary: rhel 6.5 icehouse stage.. neutron-db-manage trying to import systemd
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RDO
Classification: Community
Component: openstack-neutron
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: RC
: Icehouse
Assignee: Ihar Hrachyshka
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-16 18:13 UTC by wes hayutin
Modified: 2016-04-26 14:44 UTC (History)
4 users (show)

Fixed In Version: openstack-neutron-2014.1-10.el6.noarch
Clone Of:
Environment:
Last Closed: 2016-03-30 23:00:36 UTC
Embargoed:
ihrachys: needinfo+


Attachments (Terms of Use)
install log (6.15 MB, application/octet-stream)
2014-04-16 18:13 UTC, wes hayutin
no flags Details

Description wes hayutin 2014-04-16 18:13:21 UTC
Created attachment 886969 [details]
install log

Description of problem:

SequenceError: Error appeared during Puppet run: 172.16.7.8_neutron.pp
Notice: /Stage[main]/Main/Exec[neutron-db-manage upgrade]/returns: ImportError: cannot import name systemd
You will find full trace in log /var/tmp/packstack/20140416-134621-moszsh/manifests/172.16.7.8_neutron.pp.log


see attached logs

Comment 1 Ihar Hrachyshka 2014-04-22 13:46:21 UTC
From the logs:

[0;36mnotice: /Stage[main]//Exec[neutron-db-manage upgrade]/returns:   File "/usr/lib/python2.6/site-packages/neutron/openstack/common/service.py", line 44, in <module>[0m
[0;36mnotice: /Stage[main]//Exec[neutron-db-manage upgrade]/returns:     from neutron.openstack.common import systemd[0m
[0;36mnotice: /Stage[main]//Exec[neutron-db-manage upgrade]/returns: ImportError: cannot import name systemd[0m

So it fails to import oslo 'systemd' module. I wonder whether you have /usr/lib/python2.6/site-packages/neutron/openstack/common/systemd.py* in your installation.

Comment 2 Ihar Hrachyshka 2014-04-22 13:52:06 UTC
Also please provide which neutron package version failed for you.

Comment 3 wes hayutin 2014-04-22 14:10:15 UTC
Found in:
python-neutron-2014.1-0.19.rc2.el6.noarch
openstack-neutron-2014.1-0.19.rc2.el6.noarch
openstack-neutron-openvswitch-2014.1-0.19.rc2.el6.noarch



Resolved in:
python-neutron-2014.1-10.el6.noarch
openstack-neutron-2014.1-10.el6.noarch
openstack-neutron-openvswitch-2014.1-10.el6.noarch

I believe the issue is fixed now 

[0;37mdebug: Exec[neutron-db-manage upgrade](provider=posix): Executing 'neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini upgrade head'[0m
[0;37mdebug: Executing 'neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini upgrade head'[0m
[0;36mnotice: /Stage[main]//Exec[neutron-db-manage upgrade]/returns: executed successfully[0m
[0;37mdebug: /Stage[main]//Exec[neutron-db-manage upgrade]: The container Class[Main] will propagate my refresh event[0m


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