[Rdo-list] Packstack woes - mysql-server to mariadb-server -- BZ -- 981116 [on F19]

[Kashyap Chamarthy]

Heya,


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


> On 4 July 2013 06:26, Kashyap Chamarthy <kchamart at 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.


> * 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...)

> * 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


> * 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.

> 
> I think this is also a problem:
> * limits are wrong for the memcached configuration
> 
> 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.



-- 
/kashyap