Description of problem: Version-Release number of selected component (if applicable): openstack-packstack-2013.2.1-0.29.dev956.fc20.noarch How reproducible: always Steps to Reproduce: packstack --allinone Actual results: Installation fails with log permission issue. ERROR : Error appeared during Puppet run: 192.168.1.13_mysql.pp Error: Could not start Service[mysqld]: Execution of '/sbin/service mariadb start' returned 1: $ journalctl -xn -- Logs begin at Mon 2014-04-14 08:21:24 UTC, end at Mon 2014-04-14 09:53:11 UTC. -- Apr 14 09:53:10 afazekas-1397463414-f20-novanetwork.novalocal mysqld_safe[19396]: /usr/bin/mysqld_safe: line 182: /var/log/mysqld.log: P Apr 14 09:53:10 afazekas-1397463414-f20-novanetwork.novalocal mysqld_safe[19396]: touch: cannot touch ‘/var/log/mysqld.log’: Permission Apr 14 09:53:10 afazekas-1397463414-f20-novanetwork.novalocal mysqld_safe[19396]: chown: cannot access ‘/var/log/mysqld.log’: No such fi Apr 14 09:53:10 afazekas-1397463414-f20-novanetwork.novalocal mysqld_safe[19396]: chmod: cannot access ‘/var/log/mysqld.log’: No such fi Apr 14 09:53:10 afazekas-1397463414-f20-novanetwork.novalocal mysqld_safe[19396]: 140414 09:53:10 mysqld_safe mysqld from pid file /var/ Apr 14 09:53:10 afazekas-1397463414-f20-novanetwork.novalocal mysqld_safe[19396]: /usr/bin/mysqld_safe: line 138: /var/log/mysqld.log: P Apr 14 09:53:10 afazekas-1397463414-f20-novanetwork.novalocal systemd[1]: mariadb.service: main process exited, code=exited, status=1/FA Apr 14 09:53:11 afazekas-1397463414-f20-novanetwork.novalocal systemd[1]: mariadb.service: control process exited, code=exited status=1 Apr 14 09:53:11 afazekas-1397463414-f20-novanetwork.novalocal systemd[1]: Failed to start MariaDB database server. -- Subject: Unit mariadb.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit mariadb.service has failed. -- -- The result is failed. Apr 14 09:53:11 afazekas-1397463414-f20-novanetwork.novalocal systemd[1]: Unit mariadb.service entered failed state. Expected results: Packstack/puppet modules does not changes the default log location to '/var/log/mysqld.log' to from '/var/log/mariadb/mariadb.log', and the puppet modules ensures the correct log file permission, existence and security label. Additional info: - Just the havana version affected, icehouse version does not fails on this. - Previously we had also the https://bugzilla.redhat.com/show_bug.cgi?id=1063499 issue.
I'm installing openstack on fedora 20 and met this issue,how do I escape the issue ?
I found "chmod a+w /var/log" is a workaround.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.