Bug 1154409 - packstack errors while trying to run mariadb.pp
Summary: packstack errors while trying to run mariadb.pp
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-puppet-modules
Version: 5.0 (RHEL 6)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: z2
: 5.0 (RHEL 6)
Assignee: Gaël Chamoulaud
QA Contact: Ami Jeain
URL:
Whiteboard:
: 1149000 1151928 (view as bug list)
Depends On:
Blocks: 1154145 1154159
TreeView+ depends on / blocked
 
Reported: 2014-10-19 14:03 UTC by Ami Jeain
Modified: 2014-11-03 05:44 UTC (History)
5 users (show)

Fixed In Version: openstack-packstack-2014.1.1-0.42.dev1251.el6ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-03 05:44:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1771 0 normal SHIPPED_LIVE openstack-packstack and openstack-puppet-modules bug fix advisory 2014-11-03 10:43:53 UTC

Description Ami Jeain 2014-10-19 14:03:42 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:

always at the first run of packstack

Steps to Reproduce:
1. run the following allinone packstack line:
packstack --allinone --nagios-install=y --os-ceilometer-install=y --os-neutron-install=y --keystone-admin-passwd=redhat --keystone-demo-passwd=redhat --ssh-public-key=/root/.ssh/id_rsa.pub
2. 
3.

Actual results:

10.35.101.10_mariadb.pp:                          [ ERROR ]        
Applying Puppet manifests                         [ ERROR ]

ERROR : Error appeared during Puppet run: 10.35.101.10_mariadb.pp
Error: Could not start Service[mysqld]: Execution of '/sbin/service mysqld start' returned 1: Initializing MySQL database:  /usr/bin/my_print_defaults: unknown option '--mysqld'
You will find full trace in log /var/tmp/packstack/20141019-154411-BgHr4_/manifests/10.35.101.10_mariadb.pp.log

Expected results:

packstack runs smooth with no errors

Additional info:

from /var/tmp/packstack/20141019-154411-BgHr4_/openstack-setup.log:

tar --dereference -cpzf - apache ceilometer certmonger cinder concat firewall glance heat horizon inifile keystone memcached mongodb mysql neutron nova nssdb openstack packstack qpid rabbitmq remote rsync ssh stdlib swift sysctl tempest vcsrepo vlan vswitch xinetd | ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root.101.10 tar -C /var/tmp/packstack/26e1074841324e2ab5725c3761c9694b/modules -xpzf -
2014-10-19 15:53:57::ERROR::run_setup::921::root:: Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 902, in main
    single_step_aio_install(options)
  File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 688, in single_step_aio_install
    single_step_install(options)
  File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 718, in single_step_install
    _main(answerfilepath)
  File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 605, in _main
    runSequences()
  File "/usr/lib/python2.6/site-packages/packstack/installer/run_setup.py", line 584, in runSequences
    controller.runAllSequences()
  File "/usr/lib/python2.6/site-packages/packstack/installer/setup_controller.py", line 68, in runAllSequences
    sequence.run(config=self.CONF, messages=self.MESSAGES)
  File "/usr/lib/python2.6/site-packages/packstack/installer/core/sequences.py", line 98, in run
    step.run(config=config, messages=messages)
  File "/usr/lib/python2.6/site-packages/packstack/installer/core/sequences.py", line 44, in run
    raise SequenceError(str(ex))
SequenceError: Error appeared during Puppet run: 10.35.101.10_mariadb.pp
Error: Could not start Service[mysqld]: Execution of '/sbin/service mysqld start' returned 1: Initializing MySQL database:  /usr/bin/my_print_defaults: unknown option '--mysqld'
You will find full trace in log /var/tmp/packstack/20141019-154411-BgHr4_/manifests/10.35.101.10_mariadb.pp.log

from mariadb.pp.log:

Timeout error occurred trying to start MySQL Daemon.
Starting mysqld:  [FAILED]^[[0m
^[[1;31mError: /Stage[main]/Main/Service[mysqld]: Failed to call refresh: Could not start Service[mysqld]: Execution of '/sbin/service mysqld start' returned 1: MySQL Daemon failed to start.
Starting mysqld:  [FAILED]^[[0m
^[[1;31mError: /Stage[main]/Main/Service[mysqld]: Could not start Service[mysqld]: Execution of '/sbin/service mysqld start' returned 1: MySQL Daemon failed to start.
Starting mysqld:  [FAILED]
Wrapped exception:
Execution of '/sbin/service mysqld start' returned 1: MySQL Daemon failed to start.
Starting mysqld:  [FAILED]^[[0m
^[[mNotice: /Stage[main]/Mysql::Config/File[/etc/mysql/conf.d]/ensure: created^[[0m
^[[mNotice: /Stage[main]/Mysql::Config/Exec[set_mysql_rootpw]: Dependency Service[mysqld] has failures: true^[[0m
^[[1;31mWarning: /Stage[main]/Mysql::Config/Exec[set_mysql_rootpw]: Skipping because of failed dependencies^[[0m
^[[mNotice: /Stage[main]/Mysql::Config/File[/root/.my.cnf]: Dependency Service[mysqld] has failures: true^[[0m
^[[1;31mWarning: /Stage[main]/Mysql::Config/File[/root/.my.cnf]: Skipping because of failed dependencies^[[0m
^[[mNotice: /Stage[main]/Mysql::Config/Exec[mysqld-restart]: Dependency Service[mysqld] has failures: true^[[0m
^[[1;31mWarning: /Stage[main]/Mysql::Config/Exec[mysqld-restart]: Skipping because of failed dependencies^[[0m
^[[mNotice: /Stage[main]/Mysql::Config/Exec[mysqld-restart]/returns: Stopping mysqld:  [  OK  ]^M^[[0m
^[[mNotice: /Stage[main]/Mysql::Config/Exec[mysqld-restart]/returns: MySQL Daemon failed to start.^[[0m
^[[mNotice: /Stage[main]/Mysql::Config/Exec[mysqld-restart]/returns: Starting mysqld:  [FAILED]^M^[[0m
^[[1;31mError: /Stage[main]/Mysql::Config/Exec[mysqld-restart]: Failed to call refresh: service mysqld restart returned 1 instead of one of [0]^[[0m
^[[1;31mError: /Stage[main]/Mysql::Config/Exec[mysqld-restart]: service mysqld restart returned 1 instead of one of [0]^[[0m
^[[mNotice: /Stage[main]/Main/Database_user[@%]: Dependency Service[mysqld] has failures: true^[[0m
^[[1;31mWarning: /Stage[main]/Main/Database_user[@%]: Skipping because of failed dependencies^[[0m
^[[mNotice: /Stage[main]/Main/Database_user[root@::1]: Dependency Service[mysqld] has failures: true^[[0m
^[[1;31mWarning: /Stage[main]/Main/Database_user[root@::1]: Skipping because of failed dependencies^[[0m
^[[mNotice: /Stage[main]/Glance::Db::Mysql/Mysql::Db[glance]/Database[glance]: Dependency Service[mysqld] has failures: true^[[0m
^[[1;31mWarning: /Stage[main]/Glance::Db::Mysql/Mysql::Db[glance]/Database[glance]: Skipping because of failed dependencies^[[0m
^[[mNotice: /Stage[main]/Glance::Db::Mysql/Glance::Db::Mysql::Host_access[%]/Database_user[glance@%]: Dependency Service[mysqld] has failures: true^[[0m
^[[1;31mWarning: /Stage[main]/Glance::Db::Mysql/Glance::Db::Mysql::Host_access[%]/Database_user[glance@%]: Skipping because of failed dependencies^[[0m
^[[1;31mError: Could not prefetch database_grant provider 'mysql': Execution of '/usr/bin/mysql --defaults-file=/root/.my.cnf mysql -Be describe user' returned 1: Could not open required defaults file: /root/.my.cnf
Fatal error in defaults handling. Program aborted

Comment 1 Ami Jeain 2014-10-19 14:19:03 UTC
running packstack the 2nd time (with the generated answerfile) runs smoothly all the way to the end

Comment 2 Ami Jeain 2014-10-20 12:56:16 UTC
reproduced it again with just:
#packstack --allinone

Comment 3 Martin Magr 2014-10-21 15:08:47 UTC
*** Bug 1149000 has been marked as a duplicate of this bug. ***

Comment 4 Martin Magr 2014-10-21 15:36:29 UTC
*** Bug 1151928 has been marked as a duplicate of this bug. ***

Comment 6 Ami Jeain 2014-10-22 09:22:02 UTC
verified in latest puddle:
# rpm -qa |grep openstack-packstack
openstack-packstack-2014.1.1-0.42.dev1251.el6ost.noarch

Comment 8 errata-xmlrpc 2014-11-03 05:44:22 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2014-1771.html


Note You need to log in before you can comment on or make changes to this bug.