-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 08/07/14 15:39, Rich Bowen wrote: Dependency Service[mysqld] has failures: true Skipping because of failed dependencies I suspect there were more log messages before those you've posted that could reveal the cause of the failure. > mysqld was successfully installed, and is running. > Before I start digging deeper, I wondered if this is something > that's already been encountered. > Thanks.

On 07/08/2014 10:41 AM, Rich Bowen wrote: No joy so far, except that it does *not* seem to be related to https://bugzilla.redhat.com/show_bug.cgi?id=1117035 -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://openstack.redhat.com/

Packstack fails running nova.pp :- Installing Dependencies [ DONE ] Copying Puppet modules and manifests [ DONE ] Applying 192.169.142.57_prescript.pp 192.169.142.57_prescript.pp: [ DONE ] Applying 192.169.142.57_mysql.pp Applying 192.169.142.57_amqp.pp 192.169.142.57_mysql.pp: [ DONE ] 192.169.142.57_amqp.pp: [ DONE ] Applying 192.169.142.57_keystone.pp Applying 192.169.142.57_glance.pp Applying 192.169.142.57_cinder.pp 192.169.142.57_keystone.pp: [ DONE ] 192.169.142.57_glance.pp: [ DONE ] 192.169.142.57_cinder.pp: [ DONE ] Applying 192.169.142.57_api_nova.pp 192.169.142.57_api_nova.pp: [ DONE ] Applying 192.169.142.57_nova.pp 192.169.142.57_nova.pp: [ ERROR ] Applying Puppet manifests [ ERROR ] ERROR : Error appeared during Puppet run: 192.169.142.57_nova.pp Error: /Service[messagebus]: Could not evaluate: Could not find init script for 'messagebus' You will find full trace in log /var/tmp/packstack/20140709-094621-U8Ewey/manifests/192.169.142.57_nova.pp.log Please check log file /var/tmp/packstack/20140709-094621-U8Ewey/openstack-setup.log for more information Boris. From: bderzhavets(a)hotmail.com To: rbowen(a)redhat.com; rdo-list(a)redhat.com Date: Wed, 9 Jul 2014 01:35:24 -0400 Subject: Re: [Rdo-list] mysqld failure on --allinone, centos7 Please view https://bugzilla.redhat.com/show_bug.cgi?id=981116 ############ Comment 36 ############ So workaround is: rm /usr/lib/systemd/system/mysqld.service cp /usr/lib/systemd/system/mariadb.service /usr/lib/systemd/system/mysqld.service Works for me on CentOS 7 . Before packstack rerun:- # systemctl stop mariadb _______________________________________________ Rdo-list mailing list Rdo-list(a)redhat.com https://www.redhat.com/mailman/listinfo/rdo-list

Clean install IceHouse on Fedora 20 gives ------------------------------------------------------------------------------------------------------------------ [root@icehouse1 ~(keystone_admin)]# service mariadb status Redirecting to /bin/systemctl status mariadb.service mariadb.service - MariaDB database server Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled) Active: active (running) since Wed 2014-07-09 09:08:21 MSK; 12h ago Process: 1610 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=0/SUCCESS) Process: 760 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS) Main PID: 1609 (mysqld_safe) CGroup: /system.slice/mariadb.service ├─1609 /bin/sh /usr/bin/mysqld_safe --basedir=/usr └─3328 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/us... Jul 09 09:08:13 icehouse1.localdomain mysqld_safe[1609]: 140709 09:08:08 mysqld_safe Logging .... Jul 09 09:08:13 icehouse1.localdomain mysqld_safe[1609]: 140709 09:08:08 mysqld_safe Starting...l Jul 09 09:08:13 icehouse1.localdomain mysqld_safe[1609]: 140709 09:08:08 mysqld_safe WSREP: R...' Jul 09 09:08:18 icehouse1.localdomain mysqld_safe[1609]: 140709 09:08:18 mysqld_safe WSREP: R...1 Jul 09 09:08:21 icehouse1.localdomain systemd[1]: Started MariaDB database server. Hint: Some lines were ellipsized, use -l to show in full. ------------------------------------------------------------------------------------------------------------------ [root@icehouse1 ~(keystone_admin)]# service mysqld status Redirecting to /bin/systemctl status mysqld.service mariadb.service - MariaDB database server Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled) Active: active (running) since Wed 2014-07-09 09:08:21 MSK; 12h ago Process: 1610 ExecStartPost=/usr/libexec/mariadb-wait-ready $MAINPID (code=exited, status=0/SUCCESS) Process: 760 ExecStartPre=/usr/libexec/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS) Main PID: 1609 (mysqld_safe) CGroup: /system.slice/mariadb.service ├─1609 /bin/sh /usr/bin/mysqld_safe --basedir=/usr └─3328 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/us... Jul 09 09:08:13 icehouse1.localdomain mysqld_safe[1609]: 140709 09:08:08 mysqld_safe Logging .... Jul 09 09:08:13 icehouse1.localdomain mysqld_safe[1609]: 140709 09:08:08 mysqld_safe Starting...l Jul 09 09:08:13 icehouse1.localdomain mysqld_safe[1609]: 140709 09:08:08 mysqld_safe WSREP: R...' Jul 09 09:08:18 icehouse1.localdomain mysqld_safe[1609]: 140709 09:08:18 mysqld_safe WSREP: R...1 Jul 09 09:08:21 icehouse1.localdomain systemd[1]: Started MariaDB database server. Hint: Some lines were ellipsized, use -l to show in full. ----------------------------------------------------------------------------------------------------------------- [root@icehouse1 ~(keystone_admin)]# rpm -qa | grep mariadb mariadb-5.5.37-1.fc20.x86_64 mariadb-galera-common-5.5.36-9.fc20.x86_64 mariadb-libs-5.5.37-1.fc20.x86_64 mariadb-galera-server-5.5.36-9.fc20.x86_64 ---------------------------------------------------------------- Same picture I have on CentOS 7 after hack. ---------------------------------------------------------------- [root@ip-192-169-142-37 ~]# rpm -qa | grep mariadb mariadb-galera-common-5.5.36-9.el7.x86_64 mariadb-5.5.37-1.el7_0.x86_64 mariadb-galera-server-5.5.36-9.el7.x86_64 mariadb-libs-5.5.37-1.el7_0.x86_64 Thanks. Boris.

On 07/08/2014 09:39 AM, Rich Bowen wrote: I'm encountering this problem again. It appears that the very best way to work around it right now is to tell packstack that it's Fedora 20, rather than CentOS7. ie, replace contents of /etc/redhat-release with “Fedora release 20 (Heisenbug)” and rerun packstack. I've been digging for tickets, and I've found a number of related ones: https://bugzilla.redhat.com/show_bug.cgi?id=1065977 https://bugzilla.redhat.com/show_bug.cgi?id=1066112 https://bugzilla.redhat.com/show_bug.cgi?id=1061152 https://bugzilla.redhat.com/show_bug.cgi?id=1061045 Possibly related https://bugzilla.redhat.com/show_bug.cgi?id=981116 (Closed) What I'm wondering is if these are in fact different facets of the same issue, or if they're really different things. -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://openstack.redhat.com/

On 09/12/2014 11:17 AM, Gael Chamoulaud wrote: Thanks. My mistake. I've had this message in draft for a while and hadn't sent it because I knew you were working on that. Looks like I went ahead and sent it. --Rich -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://openstack.redhat.com/

On 09/12/2014 02:14 PM, Ivan Chavero wrote: Gaël mentioned in his response that the issue I'm experiencing will be resolved on CentOS7 real soon, so I'll just hang in there and try again in a few days. As I mentioned in my earlier response, I sent a message from my draft folder in error - I knew that Gaël was working on this fix. But, for whatever it's worth: openstack-packstack-2014.1.1-0.28.dev1238.el7.noarch openstack-packstack-puppet-2014.1.1-0.28.dev1238.el7.noarch -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://openstack.redhat.com/