RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1080343 - Fedora20: Traceback while doing packstack --allinone —quantum-l3-ext-bridge=eth0
Summary: Fedora20: Traceback while doing packstack --allinone —quantum-l3-ext-bridge=eth0
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RDO
Classification: Community
Component: openstack-packstack
Version: unspecified
Hardware: x86_64
OS: FreeBSD
unspecified
high
Target Milestone: ---
: Icehouse
Assignee: Martin Magr
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-25 08:13 UTC by Amita Sharma
Modified: 2015-03-20 20:16 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-20 20:16:27 UTC
Embargoed:


Attachments (Terms of Use)
error_logs (11.12 KB, text/plain)
2014-03-25 08:13 UTC, Amita Sharma
no flags Details

Description Amita Sharma 2014-03-25 08:13:21 UTC
Created attachment 878326 [details]
error_logs

Description of problem:
I got trace back while performing testing for openstack Icehouse milestone3.


Steps to Reproduce:
1. Followed steps given http://allthingsopen.com/2013/08/23/openstack-packstack-installation-with-external-connectivity/
2. On step packstack --allinone —quantum-l3-ext-bridge=eth0

Actual results:
It says ERROR : Error appeared during Puppet run: 10.65.201.125_mysql.pp
Error: /Stage[main]/Mysql::Config/Exec[mysqld-restart]: Failed to call refresh: service mariadb restart returned 1 instead of one of [0]

Expected results:
Installation should be successful.

Additional info:
PFA for the logs.

NOTE : It was on Selinux enforcing mode

Comment 1 Pádraig Brady 2014-03-25 10:46:46 UTC
Does the mariadb workaround in http://openstack.redhat.com/Workarounds_2014_01 work for you?

Comment 2 Amita Sharma 2014-03-25 11:12:36 UTC
I did not do any clean up, just executed two commands given on above link::
 sed -e 's/mysql/mariadb/g' -i  /usr/lib/python2.7/site-packages/packstack/puppet/modules/tempest/manifests/params.pp

packstack --answer-file=$answerfile

and it asked me lot many configuration question, which I choose to answer as default.

And unfortunately, it fails again with ::
                                                                                          [ ERROR ]

ERROR : Error appeared during Puppet run: 10.65.201.125_mysql.pp
Error: Could not start Service[mysqld]: Execution of '/sbin/service mariadb start' returned 1: 
You will find full trace in log /var/tmp/packstack/20140325-064111-4H08GX/manifests/10.65.201.125_mysql.pp.log
Please check log file /var/tmp/packstack/20140325-064111-4H08GX/openstack-setup.log for more information

In /var/tmp/packstack/20140325-064111-4H08GX/manifests/10.65.201.125_mysql.pp.log ::
^[[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: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
^[[0m

In /var/tmp/packstack/20140325-064111-4H08GX/openstack-setup.log
 packstack qpid rsync ssh stdlib swift sysctl tempest vcsrepo vlan vswitch xinetd | ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root.201.125 tar -C /var/tmp/packstack/b5d48ed03fac47f4b9163b1bb0647323/modules -xpzf -
2014-03-25 06:42:53::ERROR::run_setup::912::root:: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 907, in main
    _main(confFile)
  File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 573, in _main
    runSequences()
  File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 552, in runSequences
    controller.runAllSequences()
  File "/usr/lib/python2.7/site-packages/packstack/installer/setup_controller.py", line 84, in runAllSequences
    sequence.run(self.CONF)
  File "/usr/lib/python2.7/site-packages/packstack/installer/core/sequences.py", line 105, in run
    step.run(config=config)
  File "/usr/lib/python2.7/site-packages/packstack/installer/core/sequences.py", line 52, in run
    raise SequenceError(str(ex))
SequenceError: Error appeared during Puppet run: 10.65.201.125_mysql.pp
Error: Could not start Service[mysqld]: Execution of '/sbin/service mariadb start' returned 1: ^[[0m
You will find full trace in log /var/tmp/packstack/20140325-064111-4H08GX/manifests/10.65.201.125_mysql.pp.log

Comment 3 Martin Magr 2014-04-08 14:07:42 UTC
What packstack version do you use? I suppose you are running on Fedora 20, right?

Comment 4 Hideaki Suzuki 2014-04-24 15:15:24 UTC
I've got exactlly the same problem on Fedora 20 and at last have solved it.

What I did is like this as below...
  # packstack --allinone

I got this error.

  ERROR : Error appeared during Puppet run: 192.168.85.131_mysql.pp
  Error: /Stage[main]/Mysql::Config/Exec[mysqld-restart]: Failed to call refresh: service mariadb restart returned 1 instead of one of [0]

Then I just tried command again with $answer-file.
  # packstack --answer-file=/root/packstack-answers-20140424-193241.txt

And I got next error.

  ERROR : Error appeared during Puppet run: 192.168.85.131_mysql.pp
  Error: Could not start Service[mysqld]: Execution of '/sbin/service mariadb start' returned 1: 

This time, I could find out what command packstack run.
So I just executed 
  # /sbin/service mariadb start

Then I got next error.

  Redirecting to /bin/systemctl start  mariadb.service
  Job for mariadb.service failed. See 'systemctl status mariadb.service' and 'journalctl -xn' for details.

So I checked error by looking up systemctl
  # systemctl -l status mariadb.service

  Apr 24 22:53:08 localhost.localdomain mysqld_safe[23774]: /usr/bin/mysqld_safe: line 182: /var/log/mysqld.log: Permission denied
  Apr 24 22:53:08 localhost.localdomain mysqld_safe[23774]: touch: cannot touch ‘/var/log/mysqld.log’: Permission denied
  Apr 24 22:53:08 localhost.localdomain mysqld_safe[23774]: chown: cannot access ‘/var/log/mysqld.log’: No such file or directory
  Apr 24 22:53:08 localhost.localdomain mysqld_safe[23774]: chmod: cannot access ‘/var/log/mysqld.log’: No such file or directory
  Apr 24 22:53:08 localhost.localdomain mysqld_safe[23774]: 140424 22:53:08 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
  Apr 24 22:53:08 localhost.localdomain mysqld_safe[23774]: /usr/bin/mysqld_safe: line 138: /var/log/mysqld.log: Permission denied
  Apr 24 22:53:08 localhost.localdomain systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE
  Apr 24 22:53:09 localhost.localdomain systemd[1]: mariadb.service: control process exited, code=exited status=1
  Apr 24 22:53:09 localhost.localdomain systemd[1]: Failed to start MariaDB database server.
  Apr 24 22:53:09 localhost.localdomain systemd[1]: Unit mariadb.service entered failed state.

Here I found out PackStack didn't have the WRITE permission for /var/log.
Then I tried to give it permission.
  # chmod a+w /var/log

And run this command again.
  # /sbin/service mariadb start
  Redirecting to /bin/systemctl start  mariadb.service

I didn't get any errors...
So I tried third time.
  # packstack --answer-file=/root/packstack-answers-20140424-193241.txt

finally I got this.
 
  **** Installation completed successfully ******

Comment 5 Pádraig Brady 2014-04-26 02:44:46 UTC
Note the /var/log perms issue is tracked in bug #1087389

Comment 6 Lars Kellogg-Stedman 2015-03-20 20:16:27 UTC
This problem has been resolved in the current RDO release.  On Fedora 21 I can deploy RDO Juno without error.


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