galera_server is using repo by default instead of packages in centos

Bug #1654004 reported by Jean-Philippe Evrard on 2017-01-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openstack-ansible
Medium
Markos Chandras

Bug Description

With ubuntu use_percona_upstream is set to no, while in centos it's set to yes.

We should be consistent, and fix centos.

Changed in openstack-ansible:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Marc Gariépy (mgariepy)
Marc Gariépy (mgariepy) wrote :

So the consistency would be to install mariadb from RDO packages instead of upstream.

Markos Chandras (hwoarang) wrote :

It does not seem the RDO (at least for Pike) provides galera packages.

Fix proposed to branch: master
Review: https://review.openstack.org/535252

Changed in openstack-ansible:
assignee: Marc Gariépy (mgariepy) → Markos Chandras (hwoarang)
status: Confirmed → In Progress

Change abandoned by Markos Chandras (hwoarang) (<email address hidden>) on branch: master
Review: https://review.openstack.org/535252
Reason: abandoning for now to let the rest go in

Changed in openstack-ansible:
assignee: Markos Chandras (hwoarang) → Jean-Philippe Evrard (jean-philippe-evrard)
Changed in openstack-ansible:
assignee: Jean-Philippe Evrard (jean-philippe-evrard) → Markos Chandras (hwoarang)

Reviewed: https://review.openstack.org/535252
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-galera_server/commit/?id=dbbcb56a62e4a97af3f63f970a34a3c815352ced
Submitter: Zuul
Branch: master

commit dbbcb56a62e4a97af3f63f970a34a3c815352ced
Author: Markos Chandras <email address hidden>
Date: Mon Jan 15 23:17:41 2018 +0000

    tasks: Fix use_percona_upstream variable usage

    The 'use_percona_upstream' variable had quite different and conflicting
    meanings in the tasks. It's used to either denote that the upstream
    packages will be used directly or that the upstream repositories will
    be configured on the hosts and then use the packages from these
    repositories. However, the packages in both cases are the same so the
    variable was pointless in this form. The variable was meant to be used
    to select between upstream and downstream repositories for the Percona
    packages. Moreover, upstream does not provide packages for SUSE so we
    have to exit the deployment if that variable is set.

    Partial-Bug: #1654004
    Change-Id: I18853707c29955186da5a1f4d6e80bc3012c04f9

Reviewed: https://review.openstack.org/547738
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-galera_server/commit/?id=462b92a0f833591a2a6f08a2599146d65bef3b8a
Submitter: Zuul
Branch: stable/queens

commit 462b92a0f833591a2a6f08a2599146d65bef3b8a
Author: Markos Chandras <email address hidden>
Date: Mon Jan 15 23:17:41 2018 +0000

    tasks: Fix use_percona_upstream variable usage

    The 'use_percona_upstream' variable had quite different and conflicting
    meanings in the tasks. It's used to either denote that the upstream
    packages will be used directly or that the upstream repositories will
    be configured on the hosts and then use the packages from these
    repositories. However, the packages in both cases are the same so the
    variable was pointless in this form. The variable was meant to be used
    to select between upstream and downstream repositories for the Percona
    packages. Moreover, upstream does not provide packages for SUSE so we
    have to exit the deployment if that variable is set.

    Partial-Bug: #1654004
    Change-Id: I18853707c29955186da5a1f4d6e80bc3012c04f9
    (cherry picked from commit dbbcb56a62e4a97af3f63f970a34a3c815352ced)

tags: added: in-stable-queens
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers