On 5 July 2013 06:23, Kashyap Chamarthy <kchamart@redhat.com> wrote:
Heya,


On 07/04/2013 09:29 PM, Jonathan Barber wrote:


> On 4 July 2013 06:26, Kashyap Chamarthy <kchamart@redhat.com> wrote:
>
>> https://bugzilla.redhat.com/show_bug.cgi?id=981116 -- packstack fails
>> with mysql-server
>> dependency as a result of Fedora's switch to mariadb-server
>>
>> Anyone else seeing this too on F19?
>>
>
> Me too. I just hacked the params.pp to replace mysqldb with mariadb..
>
> I also see problems with:
> * iptables being disabled in favor of firewalld (the firewall rules are
> applied against iptables, but not read by firewalld and this means they are
> not persistant across reboots) - disable firewalld and enable iptables
> before doing packstack.

Right.

Please file a bug, when you find time. This needs to be tracked.

 https://bugzilla.redhat.com/show_bug.cgi?id=981583


> * sudoers restrictions being too tight for the quantum user to update dhcp
> records - edit /etc/sudoers.d/quantum to allow that user to execute all
> commands via sudo (not very secure I know...)

This appeared when I ran packstack from the git repo, I'll follow this up later.

> * selinux rules preventing random stuff - so I set selinux to permissive
> mode

If you file bz, maybe along with the o/p of:

  $ cat /var/log/audit/audit.log | audit2allow -R

https://bugzilla.redhat.com/show_bug.cgi?id=981598 


> * the systemd unit file for quantum-l3-agent is wrong -
> sed -i '/^ExecStart/ { s#.*#ExecStart=/usr/bin/quantum-l3-agent
> --config-file /etc/quantum/quantum.conf --config-file
> /etc/quantum/l3_agent.ini --log-file /var/log/quantum/l3-agent.log# }'
> /usr/lib/systemd/system/quantum-l3-agent.service

Also, sounds like bug.

This appears to only show up when running packstack from the git repo, I'll follow this up later.

>
> I think this is also a problem:
> * limits are wrong for the memcached configuration

This wasn't a problem with the openstack-packstack RPM, it may just be a bug in the upstream git repo. I follow this up later.
 
>
> I ran into more issues, but I didn't write them down and I've not had time
> to make a systematic check from a clean install.

Again, if you have time, please file these as bugs, as you have the context in your head,
these need to be tracked.

Will do.

Additionally, I caught this one (qpidd doesn't start and packstack doesn't report it failing) from the fedora RPM:
https://bugzilla.redhat.com/show_bug.cgi?id=981601

Some of the above issues are fixed in the upstream packstack git repo, so I would recommend anyone else to take a look at that (although it has it's own bugs which I will try to report).

For my future reference and the benefit of anyone else trying to use packstack on f19 ATM (using the RPM openstack-packstack-2013.1.1-0.3.dev527.fc19.noarch), I also ran into these problems:
https://bugzilla.redhat.com/show_bug.cgi?id=979041
https://bugzilla.redhat.com/show_bug.cgi?id=978647


--
/kashyap

Cheers
--
Jonathan Barber <jonathan.barber@gmail.com>