Barbican's database is created on the barbican profile

Bug #1710928 reported by Juan Antonio Osorio Robles on 2017-08-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Emilien Macchi

Bug Description

This causes the barbican database creation to happen on the barbican node and not on the mysql node. This gets problematic since the database creation manifest includes the server and client configuration, so this conflicts with containerized environments.

Fix proposed to branch: master

Changed in tripleo:
assignee: nobody → Juan Antonio Osorio Robles (juan-osorio-robles)
status: New → In Progress
Changed in tripleo:
assignee: Juan Antonio Osorio Robles (juan-osorio-robles) → Alex Schultz (alex-schultz)
Changed in tripleo:
importance: Undecided → High
milestone: none → pike-rc1
Changed in tripleo:
assignee: Alex Schultz (alex-schultz) → Emilien Macchi (emilienm)

Submitter: Jenkins
Branch: master

commit 6b0c04a4720036828ffc5e8ea690fdeddc1a77fb
Author: Juan Antonio Osorio Robles <email address hidden>
Date: Tue Aug 15 19:52:07 2017 +0300

    Move barbican's database creation to mysql profile

    This makes sure that the database creation is only executed on the mysql
    profile (or container if that's enabled), and stops the conflicts and
    errors that were happening when barbican was deployed in containerized

    Change-Id: Ib5c99482f62397fc5fb79a9dc537dfb06ee7f4df
    Closes-Bug: #1710928

Changed in tripleo:
status: In Progress → Fix Released

This issue was fixed in the openstack/puppet-tripleo 7.3.0 release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers