Ask Your Question
1

f20: packstack: Puppet run: <IP> mysql.pp Error: mysqladmin -u root fails

asked 2014-08-16 22:42:48 -0500

FredSmite gravatar image

Fedora 20 :

Applying 192.168.1.126_mysql.pp Applying 192.168.1.126_qpid.pp 192.168.1.126_mysql.pp: [ ERROR ]
Applying Puppet manifests [ ERROR ]

ERROR : Error appeared during Puppet run: 192.168.1.126_mysql.pp Error: mysqladmin -u root password '34a1ce3572424a9c' returned 1 instead of one of [0] You will find full trace in log /var/tmp/packstack/20140816-220059-

See https://bugzilla.redhat.com/show_bug.cgi?id=1130724 (https://bugzilla.redhat.com/show_bug....)

See

edit retag flag offensive close merge delete

Comments

I set SELinux to permissive . rebooted and it still failed.

FredSmite gravatar imageFredSmite ( 2014-08-16 22:44:04 -0500 )edit

4 answers

Sort by ยป oldest newest most voted
1

answered 2014-08-17 04:28:47 -0500

dbaxps gravatar image

If you are running packstack not the first time, you should have answer-file-xxxxxxx.txt generated by previous run of packstack. You may try to run:-

packstack --answer-file=./answer-file-xxxxxxx.txt
edit flag offensive delete link more
0

answered 2014-08-17 02:05:32 -0500

T u l gravatar image

updated 2014-08-17 02:09:18 -0500

If it is not the first time you run packstack, then a random root password for mysql was already set. If you have nothing else apart from openstack on this machine, try to purge mysql package:

yum remove mysql mysql-server
rm -rf /var/lib/mysql

and start packstack again

Alternatively, if you know mysql root password, you may edit the rdo's answer file and put the password there, and run packstack with that answer file

edit flag offensive delete link more

Comments

Thank you

It gets a different error now:

Applying 192.168.1.126_mysql.pp Applying 192.168.1.126_qpid.pp 192.168.1.126_mysql.pp: [ DONE ]
192.168.1.126_qpid.pp: [ DONE ]
Applying 192.168.1.126_keystone.pp Applying 192.168.1.126_glance.pp Applying 192.168.1.126_cinder.pp 192.168.1.126_keystone.pp: [ ERROR ]
Applying Puppet manifests [ ERROR ]

ERROR : Error appeared during Puppet run: 192.168.1.126_keystone.pp Notice: /Stage[main]/Keystone::Db::Sync/Exec[keystone-manage db_sync]/returns: 15033 CRITICAL keystone [-] OperationalError: (OperationalError) (1045, "Access denied for user 'root'@'localhost' (using password: YES)") None None You will find full trace in log /var/tmp/packstack/20140817-061859-nsNydC/manifests/192.168.1.126_keystone.pp.log Please check log file /var/tmp/packstack/20140817-061859-nsNydC/openstack-setup.log for more information

FredSmite gravatar imageFredSmite ( 2014-08-17 06:23:10 -0500 )edit

Now keystone is failing:

sudo /sbin/service openstack-keystone start Redirecting to /bin/systemctl start openstack-keystone.service Job for openstack-keystone.service failed. See 'systemctl status openstack-keystone.service' and 'journalctl -xn' for details. [jpd@gibsonsg ~]$ journalctl -xn -- Logs begin at Sat 2014-08-16 04:53:35 CDT, end at Sun 2014-08-17 06:28:04 CDT Aug 17 06:27:55 gibsonsg systemd[1]: Failed to start OpenStack Identity Service -- Subject: Unit openstack-keystone.service has failed -- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel (http://lists.freedesktop.org/mailman/...)

-- Unit openstack-keystone.service has failed.

-- The result is failed. Aug 17 06:27:55 gibsonsg systemd[1]: Unit openstack-keystone.service entered fai Aug 17 06:28:01 gibsonsg systemd[1]: Starting Session 863 of user root. -- Subject: Unit session-863.scope has begun with start-up -- Defined-By: systemd

-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel (http://lists.freedesktop.org/mailman/...)

-- Unit session-863.scope has ...(more)

FredSmite gravatar imageFredSmite ( 2014-08-17 06:31:42 -0500 )edit
0

answered 2014-08-17 11:57:41 -0500

FredSmite gravatar image

I reinstalled F20 ( network install) and started with a fresh packspace environment and it worked.

I can't stress that openstack likely needs added to a fresh system - not one that has been alternated in anyway .

edit flag offensive delete link more

Comments

You wrote :- I can't stress that openstack likely needs added to a fresh system - not one that has been alternated in anyway .
It is not correct, I can rerun packstack several times using answer-file-xxxxxx.txt created by previous run

dbaxps gravatar imagedbaxps ( 2014-08-17 12:10:15 -0500 )edit

No . I even used hammer.sh remove script and had the same issue . There was obviously some stale setting not being addressed.

FredSmite gravatar imageFredSmite ( 2014-08-17 17:23:42 -0500 )edit
0

answered 2014-08-18 01:50:22 -0500

tpcloud_nerd gravatar image

I solved this issue just by killing all mysql processes that were running. This would occur after the first time I tried to run packstack install.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-08-16 22:42:48 -0500

Seen: 1,747 times

Last updated: Aug 18 '14