periodic-tripleo-ci-centos-8-scenario000-multinode-oooq-container-updates-master failing in create container mysql_init_bundle
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Triaged
|
Critical
|
Unassigned |
Bug Description
2020-08-23 18:10:23 | [ERROR]: Container(s) which failed to be created by podman_container module:
2020-08-23 18:10:23 | ['mysql_
2020-08-23 18:10:23 | [ERROR]: Container(s) which did not finish after 300 minutes:
2020-08-23 18:10:23 | ['mysql_
2020-08-23 18:10:23 | 2020-08-23 18:10:23.058255 | fa163e8d-
2020-08-23 18:10:23 | "changed": false,
2020-08-23 18:10:23 | "msg": "Failed container(s): ['mysql_
2020-08-23 18:10:23 | }
2020-08-23 18:10:23 |
2020-08-23 18:10:23 | NO MORE HOSTS LEFT *******
tags: | removed: quickstart |
This is a dup of https:/ /launchpad. net/bugs/ 1890798, more specifically, the two container images used during the update job have misaligned UID/GID:
# original container image used for the deploy rdoproject. org/tripleomast er/centos- binary- mariadb: 8a3f4edf6c2e538 0db8b47eb0b4c31 57 id mysql 42434(mysql) ,42400( kolla)
sudo podman run --rm --net=host -it trunk.registry.
uid=42434(mysql) gid=42434(mysql) groups=
# updated container image io/tripleomaste r/centos- binary- mariadb: current- tripleo id mysql 27(mysql) ,42400( kolla)
sudo podman run --rm --net=host -it docker.
uid=27(mysql) gid=27(mysql) groups=
This issue is fixed in master [1] fixed the issue, but we probably need a promotion or the latest container image tagged current-tripleo needs to be rebuilt for that bug to go away.
[1] https:/ /review. opendev. org/#/c/ 745575