tripleo

Containers scenario002 broken -- trying to start MariaDB on bare metal

Bug #1700050 reported by Jiří Stránský
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Unassigned
tripleo pike-3 "pike-3"

Bug Description

Scenario 002 with containers is broken because it tries to start MariaDB on host, and it conflicts with the one already running in a container.

Something must be pulling in the MariaDB puppet code, my suspicion is that it could be the non-containerized Barbican.

Tags: ci containers
Revision history for this message
Jiří Stránský (jistr) wrote :

http://logs.openstack.org/80/476680/1/experimental/gate-tripleo-ci-centos-7-scenario002-multinode-oooq-container/b61b056/logs/undercloud/home/jenkins/overcloud_deploy.log.txt.gz#_2017-06-22_21_13_20

Revision history for this message
Jiří Stránský (jistr) wrote :

Just to clarify, the bug happens with the scenario002 enablement patch here https://review.openstack.org/#/c/476680

Revision history for this message
Jiří Stránský (jistr) wrote :

I've tried disabling non-containerized Barbican in the patch, just to see if it solves the issue, and i'm also trying to reproduce the issue locally.

Revision history for this message
Jiří Stránský (jistr) wrote :

Indeed it was fixed by removing the bare metal Barbican service.

Change https://review.openstack.org/#/c/474327 adds Barbican back in the containerized form.

Revision history for this message
Jiří Stránský (jistr) wrote :

This is now fixed, Barbican service will be added to that scenario when it can pass CI.

Changed in tripleo:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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