standalone fails if hostname is not properly set and pacemaker is used

Bug #1814564 reported by Alex Schultz on 2019-02-04
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tripleo
High
Alex Schultz

Bug Description

If pacemaker is used in the standalone but the hostname is not properly set on the host prior to deployment, the deployment fails in step3 when trying to configure galera. Additionally rabbitmq has issues.

        "Error: /usr/bin/clustercheck >/dev/null returned 1 instead of one of [0]",
        "Error: /Stage[main]/Tripleo::Profile::Pacemaker::Database::Mysql_bundle/Exec[galera-ready]/returns: change from notrun to 0 failed: /usr/bin/clustercheck >/dev/null returned 1 instead of one of [0]",
        "Error: Failed to apply catalog: Execution of '/usr/bin/mysql --defaults-extra-file=/root/.my.cnf -NBe SELECT CONCAT(User, '@',Host) AS User FROM mysql.user' returned 1: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (111 \"Connection refused\")",

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

Changed in tripleo:
status: Triaged → In Progress

Reviewed: https://review.openstack.org/634836
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=fc07a263170329370476abf2a5a18f5fab177d76
Submitter: Zuul
Branch: master

commit fc07a263170329370476abf2a5a18f5fab177d76
Author: Alex Schultz <email address hidden>
Date: Mon Feb 4 17:14:35 2019 -0700

    Specify hostname for standalone

    The standalone must have a fully qualified hostname configured as it can
    have issues when deploying with pacemaker managed services.

    Change-Id: If7ae3f575238e69bfc8858dd968cf3c69af512ca
    Related-Bug: #1814564

Reviewed: https://review.openstack.org/634803
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=63f4175e768796970801a36dee9585b3d89a9531
Submitter: Zuul
Branch: master

commit 63f4175e768796970801a36dee9585b3d89a9531
Author: Alex Schultz <email address hidden>
Date: Mon Feb 4 13:36:29 2019 -0700

    Run hostname check for standalone

    Run a hostname preflight check when running the standalone as this can
    cause issues with rabbit/mysql/pacemaker/puppet. The standalone check is
    not run when an undercloud is being deployed or if output only is
    specified. The undercloud has a different set of preflight checks run
    prior to deployment so we do not need to rerun the hostname check when
    the undercloud is being deployed.

    Depends-On: https://review.openstack.org/#/c/634836/
    Change-Id: I4de51d792f004575e0e802a1d340478d6ae9f848
    Closes-Bug: #1814564

Changed in tripleo:
status: In Progress → Fix Released

Reviewed: https://review.openstack.org/634971
Committed: https://git.openstack.org/cgit/openstack/tripleo-docs/commit/?id=14dd0e4bd8b3db503cb7741ecff1dea1ff308eb6
Submitter: Zuul
Branch: master

commit 14dd0e4bd8b3db503cb7741ecff1dea1ff308eb6
Author: Alex Schultz <email address hidden>
Date: Tue Feb 5 09:29:57 2019 -0700

    Document the requirement for the hostname on standalone

    When deploying a standalone system, a fully qualified hostname is
    required when deploying with pacemaker managed services. This change
    documents this as a best practice for the deployment.

    Depends-On: https://review.openstack.org/#/c/634803/
    Change-Id: I3f993f6ab98b7138cfbdc5e57b7a19dcc03b1000
    Related-Bug: #1814564

Reviewed: https://review.openstack.org/637309
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=892f4848c8c1ee5c661eb536ca906b0c6d3cf172
Submitter: Zuul
Branch: master

commit 892f4848c8c1ee5c661eb536ca906b0c6d3cf172
Author: Alex Schultz <email address hidden>
Date: Fri Feb 15 14:39:55 2019 -0700

    Set hostname for undercloud-upgrade

    Not sure how this was passing previously as the undercloud has always
    required a proper hostname, but the change for Bug 1814564 seems to be
    failing on rocky upgrade job. So let's properly set the undercloud
    hostname on installation.

    Change-Id: I217abd975ec6a7a98a624a09c9194db9ecdafe35
    Related-Bug: #1814564

Reviewed: https://review.openstack.org/637200
Committed: https://git.openstack.org/cgit/openstack/python-tripleoclient/commit/?id=272beb2d192b965f30435106938a06a2ba051408
Submitter: Zuul
Branch: stable/rocky

commit 272beb2d192b965f30435106938a06a2ba051408
Author: Alex Schultz <email address hidden>
Date: Mon Feb 4 13:36:29 2019 -0700

    Run hostname check for standalone

    Run a hostname preflight check when running the standalone as this can
    cause issues with rabbit/mysql/pacemaker/puppet. The standalone check is
    not run when an undercloud is being deployed or if output only is
    specified. The undercloud has a different set of preflight checks run
    prior to deployment so we do not need to rerun the hostname check when
    the undercloud is being deployed.

    Conflicts:
     tripleoclient/tests/test_utils.py
     tripleoclient/tests/v1/tripleo/test_tripleo_deploy.py
     tripleoclient/utils.py
     tripleoclient/v1/tripleo_deploy.py
     tripleoclient/v1/undercloud_preflight.py

    Depends-On: https://review.openstack.org/#/c/637309/
    Change-Id: I4de51d792f004575e0e802a1d340478d6ae9f848
    Closes-Bug: #1814564
    (cherry picked from commit 63f4175e768796970801a36dee9585b3d89a9531)

tags: added: in-stable-rocky

Reviewed: https://review.openstack.org/637938
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart/commit/?id=9e6177d0f115b72bbd48f649101f26013a725683
Submitter: Zuul
Branch: master

commit 9e6177d0f115b72bbd48f649101f26013a725683
Author: Emilien Macchi <email address hidden>
Date: Tue Feb 19 12:04:12 2019 -0500

    Set hostname for containerized undercloud-upgrade

    See I217abd975ec6a7a98a624a09c9194db9ecdafe35 - same spirit.

    Depends-On: I4a569195deeadb34180561c778dabe77be4f6466
    Change-Id: I217d15b5156b29139fd17c2a9d40b1e0c06941b4
    Related-Bug: #1814564

This issue was fixed in the openstack/python-tripleoclient 11.3.0 release.

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

Duplicates of this bug

Other bug subscribers