[Rdo-list] RDO test day (7,8-JAN-2014) -- IRC meeting minutes log
by Kashyap Chamarthy
================================
#rdo: RDO test day; 7,8-JAN-2014
================================
Thanks everyone for participating in the test day, here's the summary (&
URL to full logs) of MeetBot-generated IRC meeting minutes over the last
2 days.
The full logs are available at:
http://meetbot.fedoraproject.org/rdo/2014-01-07/rdo-test-day-jan2014.2014...
.
(We're currently using Fedora infrastructure's meetbot; hence the name
the URL.)
Meeting summary
---------------
* LINK: http://www.fpaste.org/66374/90963731/ (afazekas, 12:06:21)
* LINK: http://pastebin.com/qQXgL7hF (ohochman, 12:15:38)
* LINK: http://www.fpaste.org/66388/90983821/ (afazekas, 12:39:55)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1020954 (rlandy,
13:19:44)
* LINK: http://openstack.redhat.com/Workarounds#Could_not_enable_mysqld
(flaper87, 13:49:08)
* LINK: http://openstack.redhat.com/Workarounds_2014_01 (giulivo,
14:06:07)
* LINK:
http://openstack.redhat.com/Testing_IceHouse_using_Tempest#configure_and_...
(weshay, 14:34:06)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1049235 (majopela,
15:02:17)
* LINK:
http://www.redhat.com/archives/libvir-list/2013-November/msg00967.html
, https://bugzilla.redhat.com/show_bug.cgi?id=1033039 (afazekas,
15:35:42)
* LINK: http://www.fpaste.org/66440/13891090/ n-net f20 (afazekas,
15:38:01)
* LINK: http://fpaste.org/66476/13891181/ (shardy, 18:13:54)
* LINK: http://www.fpaste.org/66498/91217481/ do I need to enable
something to get the dhcp agent bindings ? (afazekas, 19:12:40)
* LINK: http://www.fpaste.org/66503/12312313/ (afazekas, 19:32:28)
* LINK:
https://github.com/openstack/cinder/commit/bb06ebd0f6a75a6ba55a7c022de96a...
(abaron, 06:53:11)
* LINK: http://openstack.redhat.com/Adding_a_compute_node (kashyap,
08:56:44)
* LINK:
http://repos.fedorapeople.org/repos/openstack/openstack-icehouse/epel-7/r...:
[Errno 14] HTTP Error 404 - Not Found (afazekas, 11:28:51)
* ACTION: Kashyap/larsks to bring up the issue of modularized SELinux
policies for OpenStack on the list (kashyap, 14:21:37)
Meeting ended at 07:22:49 UTC.
Action Items
------------
* Kashyap/larsks to bring up the issue of modularized SELinux policies
for OpenStack on the list
Action Items, by person
-----------------------
* larsks
* Kashyap/larsks to bring up the issue of modularized SELinux policies
for OpenStack on the list
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* ndipanov (227)
* kashyap (199)
* ohochman (150)
* Dafna (114)
* giulivo (95)
* larsks (91)
* pixelb (77)
* majopela (63)
* afazekas (55)
* morazi (35)
* jbernard (34)
* ayoung (32)
* mbourvin (29)
* shardy (25)
* paul__ (24)
* yfried (24)
* abaron (23)
* Dominic (21)
* rlandy (19)
* yrabl (18)
* DrBacchus (13)
* zaitcev (13)
* flaper87 (12)
* weshay (12)
* nmagnezi (11)
* pradeep (11)
* mrunge (11)
* eglynn (11)
* vladan (10)
* tshefi_ (10)
* jistr (10)
* Egyptian[Laptop] (6)
* jruzicka (6)
* mpavlase (6)
* dneary (5)
* japerry (4)
* kwhitney (4)
* oblaut (3)
* zodbot (3)
* anand_ (3)
* bcrochet (3)
* panda (2)
* mbourvin1 (2)
* tshefi (2)
* nlevinki (2)
* psedlak (1)
* jpich (1)
* TVR_ (1)
* mmagr (1)
* misterr (1)
* ukalifon (1)
--
/kashyap
10 years, 3 months
[Rdo-list] Packstack error
by Tim Bell
Any ideas how to fix ? I'm running Scientific Linux 6.5.
Running packstack (turning off neutron)
ERROR : Error appeared during Puppet run: 128.142.135.93_horizon.pp
Error: Parameter name failed on Package[horizon-packages]: Name must be a String not Array at /var/tmp/packstack/805bcb724cfe4f8499e799d1795f3a0c/manifests/128.142.135.93_horizon.pp:7
You will find full trace in log /var/tmp/packstack/20131220-135003-LzYOG0/manifests/128.142.135.93_horizon.pp.log
The additional logs just report the same thing (i.e. Name must be a String not Array).
cd /usr/lib/python2.6/site-packages/packstack/puppet/modules
tar --dereference -cpzf - apache ceilometer certmonger cinder concat firewall glance heat horizon inifile keystone memcached mongodb mysql neutron nova nssdb openstack packstack qpid rsync ssh stdlib swift sysctl tempest vcsrepo vlan vswitch xinetd | ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root(a)128.142.135.93 tar -C /var/tmp/packstack/805bcb724cfe4f8499e799d1795f3a0c/modules -xpzf -
2013-12-20 13:52:12::ERROR::run_setup::909::root:: Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 904, in main
_main(confFile)
File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 573, in _main
runSequences()
File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 552, in runSequences
controller.runAllSequences()
File "/usr/lib/python2.6/site-packages/packstack/installer/setup_controller.py", line 84, in runAllSequences
sequence.run(self.CONF)
File "/usr/lib/python2.6/site-packages/packstack/installer/core/sequences.py", line 105, in run
step.run(config=config)
File "/usr/lib/python2.6/site-packages/packstack/installer/core/sequences.py", line 52, in run
raise SequenceError(str(ex))
SequenceError: Error appeared during Puppet run: 128.142.135.93_horizon.pp
Error: Parameter name failed on Package[horizon-packages]: Name must be a String not Array at /var/tmp/packstack/805bcb724cfe4f8499e799d1795f3a0c/manifests/128.142.135.93_horizon.pp:7
You will find full trace in log /var/tmp/packstack/20131220-135003-LzYOG0/manifests/128.142.135.93_horizon.pp.log
[cid:image001.png@01CEFD89.483D8020]
10 years, 3 months
[Rdo-list] Quick tip: while logging/investigating SELinux issues
by Kashyap Chamarthy
I usually try these when I hit SELinux issues, thought
I'd quickly share here.
# Enable SELinux
$ setenforce 1
# Clear the audit log (so only relevant messages can be analysed later)
$ > /var/log/audit/audit.log
[Perform your offending test]
# Show a reference policy
$ cat /var/log/audit/audit.log | audit2allow -R
And, if you're feeling more adventurous, you can even generate
an SELinux reference policy and re-test it:
e.g. If you see Neutron issues from the previous command,
you can try
# Generate an SELinux loadable module package
$ audit2allow -a -M neutron
# Install the Policy Package
$ semodule -i neutron.pp
# Restart neutron-dhcp-agent again
$ systemctl restart neutron-dhcp-agent
See if it alleviates your problem.
Ref:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Lin...
--
/kashyap
10 years, 3 months
[Rdo-list] Heads up: openstack-neutron-agent fails to start w/o python-psutil
by Kashyap Chamarthy
Heya,
I just upgraded my Fedora 20 Havana setup to IceHouse, and, restarting
openstack-neutron-agent fails with the below:
=================================
$ systemctl start neutron-openvswitch-agent
$ systemctl status neutron-openvswitch-agent
[. . .]
Jan 07 02:45:15 node2-compute neutron-openvswitch-agent[3471]: from neutron.agent.linux
import polling
Jan 07 02:45:15 node2-compute neutron-openvswitch-agent[3471]: File
"/usr/lib/python2.7/site-packages/neutron/agent/linux/polling.py", line 2...odule>
Jan 07 02:45:15 node2-compute neutron-openvswitch-agent[3471]: from neutron.agent.linux
import ovsdb_monitor
Jan 07 02:45:15 node2-compute neutron-openvswitch-agent[3471]: File
"/usr/lib/python2.7/site-packages/neutron/agent/linux/ovsdb_monitor.py", ...odule>
Jan 07 02:45:15 node2-compute neutron-openvswitch-agent[3471]: from neutron.agent.linux
import async_process
Jan 07 02:45:15 node2-compute neutron-openvswitch-agent[3471]: File
"/usr/lib/python2.7/site-packages/neutron/agent/linux/async_process.py", ...odule>
Jan 07 02:45:15 node2-compute neutron-openvswitch-agent[3471]: import psutil
Jan 07 02:45:15 node2-compute neutron-openvswitch-agent[3471]: ImportError: No module
named psutil
Jan 07 02:45:15 node2-compute systemd[1]: neutron-openvswitch-agent.service: main process
exited, code=exited, status=1/FAILURE
Jan 07 02:45:15 node2-compute systemd[1]: Unit neutron-openvswitch-agent.service entered
failed state.
Hint: Some lines were ellipsized, use -l to show in full.
[root@node2-compute ~]# systemctl status neutron-openvswitch-agent -l
neutron-openvswitch-agent.service - OpenStack Quantum Open vSwitch Agent
Loaded: loaded (/usr/lib/systemd/system/neutron-openvswitch-agent.service; enabled)
Active: failed (Result: exit-code) since Mon 2012-12-10 02:45:15 EST; 20s ago
Process: 3471 ExecStart=/usr/bin/neutron-openvswitch-agent --config-file
/usr/share/neutron/neutron-dist.conf --config-file /etc/neutron/neutron.conf --config-file
/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini --log-file
/var/log/neutron/openvswitch-agent.log (code=exited, status=1/FAILURE)
Main PID: 3471 (code=exited, status=1/FAILURE)
=================================
Workaround for now - explicitly install python-psutil:
$ yum install python-psutil.x86_64
$ systemctl start neutron-openvswitch-agent
$ systemctl status neutron-openvswitch-agent -l
neutron-openvswitch-agent.service - OpenStack Quantum Open vSwitch Agent
Loaded: loaded (/usr/lib/systemd/system/neutron-openvswitch-agent.service; enabled)
Active: active (running) since Mon 2012-12-10 18:23:13 EST; 1 years 0 months ago
Main PID: 3515 (neutron-openvsw)
CGroup: /system.slice/neutron-openvswitch-agent.service
└─3515 /usr/bin/python /usr/bin/neutron-openvswitch-agent --config-file
/usr/share/neutron/neutron-dist.conf --config-file /etc/neutron/neutron.conf --config-file
/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini --log-file
/var/log/neutron/openvswitch-agent.log
[. . .]
Not sure if others are encountering this too?
--
/kashyap
10 years, 3 months
[Rdo-list] Reminder: RDO Icehouse test days TOMORROW
by Rich Bowen
A reminder that we'll be doing the Icehouse Milestone 1 RDO test days
starting tomorrow, January 7th and 8th. We'd really appreciate it if you
could give us an hour or two of your time, to try to ferret out any
problems with the RDO packages.
The Icehouse Milestone 1 package set is available for Fedora 20, and
RHEL 6, and derivatives.
To prepare for testing, have a look at
http://openstack.redhat.com/RDO_test_day_January_2014 and add your name
to the list if you're going to be able to participate.
The tests that we'd like to do are listed at
http://openstack.redhat.com/TestedSetups_2014_01 so if you're unable to
participate during the designated time, but are able to do some testing
at another time, please go ahead and put your results and notes there.
Join us on #rdo, on the Freenode IRC network, for questions and
conversation during the event. See you there!
--Rich
--
Rich Bowen - rbowen(a)redhat.com
OpenStack Community Liaison
http://openstack.redhat.com/
10 years, 3 months
