Container exited with non-zero return code

Bug #1644286 reported by wanghongxu
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
kolla
Expired
Undecided
Unassigned

Bug Description

kolla version:390b4a2(git rev-parse --short HEAD)

[root@controller kolla]# cat /etc/kolla/globals.yml | grep -v "^#" | grep -v "^$"
---
openstack_release: "4.0.0"
kolla_internal_vip_address: "192.168.80.11"
network_interface: "eno16777736"
neutron_external_interface: "eno33554984"

ERROR LOG:
......
TASK [mariadb : include] *******************************************************
included: /usr/share/kolla/ansible/roles/mariadb/tasks/bootstrap_cluster.yml for localhost

TASK [mariadb : Running MariaDB bootstrap container] ***************************
fatal: [localhost]: FAILED! => {"changed": true, "failed": true, "msg": "Container exited with non-zero return code"}
 to retry, use: --limit @/usr/share/kolla/ansible/site.retry

PLAY RECAP *********************************************************************
localhost : ok=58 changed=22 unreachable=0 failed=1

[root@controller kolla]# docker logs bootstrap_mariadb
INFO:__main__:Kolla config strategy set to: COPY_ALWAYS
INFO:__main__:Loading config file at /var/lib/kolla/config_files/config.json
INFO:__main__:Validating config file
INFO:__main__:Copying service configuration files
INFO:__main__:Removing existing destination: /etc//my.cnf
INFO:__main__:Copying /var/lib/kolla/config_files/galera.cnf to /etc//my.cnf
INFO:__main__:Setting permissions for /etc//my.cnf
INFO:__main__:Copying /var/lib/kolla/config_files/wsrep-notify.sh to /usr/local/bin/wsrep-notify.sh
INFO:__main__:Setting permissions for /usr/local/bin/wsrep-notify.sh
INFO:__main__:Writing out command to execute
INFO:__main__:Setting permission for /var/lib/mysql
Installing MariaDB/MySQL system tables in '/var/lib/mysql/' ...
161120 20:22:48 [Note] /usr/sbin/mysqld (mysqld 10.0.28-MariaDB-wsrep) starting as process 31 ...
OK
Filling help tables...
161120 20:22:55 [Note] /usr/sbin/mysqld (mysqld 10.0.28-MariaDB-wsrep) starting as process 58 ...
OK

To start mysqld at boot time you have to copy
support-files/mysql.server to the right place for your system

PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
To do so, start the server, then issue the following commands:

'/usr/bin/mysqladmin' -u root password 'new-password'
'/usr/bin/mysqladmin' -u root -h controller password 'new-password'

Alternatively you can run:
'/usr/bin/mysql_secure_installation'

which will also give you the option of removing the test
databases and anonymous user created by default. This is
strongly recommended for production servers.

See the MariaDB Knowledgebase at http://mariadb.com/kb or the
MySQL manual for more instructions.

You can start the MariaDB daemon with:
cd '/usr' ; /usr/bin/mysqld_safe --datadir='/var/lib/mysql/'

You can test the MariaDB daemon with mysql-test-run.pl
cd '/usr/mysql-test' ; perl mysql-test-run.pl

Please report any problems at http://mariadb.org/jira

The latest information about MariaDB is available at http://mariadb.org/.
You can find additional information about the MySQL part at:
http://dev.mysql.com
Support MariaDB development by buying support/new features from MariaDB
Corporation Ab. You can contact us about this at <email address hidden>.
Alternatively consider joining our community based development effort:
http://mariadb.com/kb/en/contributing-to-the-mariadb-project/

161120 20:23:00 mysqld_safe Logging to '/var/log/kolla/mariadb/mariadb.log'.

[root@controller kolla]# docker exec -it heka bash
(heka)[heka@controller /]$ cat /var/log/kolla/mariadb/mariadb.log
cat: /var/log/kolla/mariadb/mariadb.log: Permission denied
(heka)[heka@controller /]$ ls -al /var/log/kolla/mariadb/mariadb.log
-rw-rw----. 1 997 996 10642 Nov 20 20:37 /var/log/kolla/mariadb/mariadb.log

description: updated
Changed in kolla:
status: New → Triaged
importance: Undecided → Low
Changed in kolla:
assignee: nobody → sayantani (sayantani.goswami)
assignee: sayantani (sayantani.goswami) → nobody
Changed in kolla:
milestone: none → ocata-3
Changed in kolla:
milestone: ocata-3 → ocata-rc1
Changed in kolla:
milestone: ocata-rc1 → pike-1
Changed in kolla:
milestone: pike-2 → pike-3
Changed in kolla:
milestone: pike-3 → pike-rc1
Changed in kolla:
milestone: pike-rc1 → queens-1
Revision history for this message
Chris Suttles (killface007) wrote :

this looks like a duplicate of https://bugs.launchpad.net/kolla/+bug/1652567

Changed in kolla:
milestone: queens-2 → queens-3
Changed in kolla:
milestone: queens-3 → queens-rc1
Changed in kolla:
milestone: queens-rc1 → queens-rc2
Changed in kolla:
milestone: queens-rc2 → rocky-1
Revision history for this message
jichenjc (jichenjc) wrote :

keep seeing this error when doing PoC, need restart again and again when deploy a all-in-one env
any idea on workaround?

Revision history for this message
jichenjc (jichenjc) wrote :

1/2 has this kind of issues

included: /usr/local/share/kolla-ansible/ansible/roles/glance/tasks/bootstrap_service.yml for localhost

TASK [glance : Running Glance bootstrap container] ********************************************************************************************
fatal: [localhost -> localhost]: FAILED! => {"changed": true, "msg": "Container exited with non-zero return code"}

NO MORE HOSTS LEFT ****************************************************************************************************************************
        to retry, use: --limit @/usr/local/share/kolla-ansible/ansible/site.retry

PLAY RECAP ************************************************************************************************************************************
localhost : ok=91 changed=16 unreachable=0 failed=1

Changed in kolla:
milestone: rocky-2 → rocky-3
Revision history for this message
Jeffrey Zhang (jeffrey4l) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
  Valid example: CONFIRMED FOR: OCATA

Changed in kolla:
importance: Low → Undecided
status: Triaged → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.