centos8 standalone-upgrade master fails during upgrade step 1 haproxy

Bug #1886529 reported by Marios Andreou
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Damien Ciabrini

Bug Description

The centos8 standalone-upgrade job is failing during step1 upgrade tasks at [1][2] unable to start haproxy with trace like

        2020-07-03 13:55:37 | 2020-07-03 13:55:37.631151 | bc764e04-506c-0306-b8de-000000000571 | TIMING | Update the haproxy bundle to use the new container image name | 0:01:45.968 | 1.35s
        2020-07-03 13:55:43 | 2020-07-03 13:55:43.949445 | bc764e04-506c-0306-b8de-000000000572 | RETRY | Enable the haproxy cluster resource | standalone | 5 retries left
        2020-07-03 13:55:51 | 2020-07-03 13:55:51.134458 | bc764e04-506c-0306-b8de-000000000572 | RETRY | Enable the haproxy cluster resource | standalone | 4 retries left
        2020-07-03 13:55:58 | 2020-07-03 13:55:58.321592 | bc764e04-506c-0306-b8de-000000000572 | RETRY | Enable the haproxy cluster resource | standalone | 3 retries left
        2020-07-03 13:56:05 | 2020-07-03 13:56:05.590314 | bc764e04-506c-0306-b8de-000000000572 | RETRY | Enable the haproxy cluster resource | standalone | 2 retries left
        2020-07-03 13:56:12 | 2020-07-03 13:56:12.762566 | bc764e04-506c-0306-b8de-000000000572 | RETRY | Enable the haproxy cluster resource | standalone | 1 retries left
        2020-07-03 13:56:19 | 2020-07-03 13:56:19.988036 | bc764e04-506c-0306-b8de-000000000572 | FATAL | Enable the haproxy cluster resource | standalone | error={"attempts": 5, "changed": false, "error": "Error: resource 'haproxy-bundle' is not running on any node\n", "msg": "Failed, to set the resource haproxy-bundle to the state enable", "output": "", "rc": 1}

Note this job is being added with [3]

[1] https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_528/738844/7/check/tripleo-ci-centos-8-standalone-upgrade/52838a3/logs/undercloud/home/zuul/standalone_upgrade.log
[2] https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_abe/739217/1/check/tripleo-ci-centos-8-standalone-upgrade/abed4b5/logs/undercloud/home/zuul/standalone_upgrade.log
[3] https://review.opendev.org/738844

Tags: alert ci
Changed in tripleo:
importance: Undecided → High
wes hayutin (weshayutin)
tags: added: alert
Changed in tripleo:
milestone: victoria-1 → victoria-3
Changed in tripleo:
assignee: Marios Andreou (marios-b) → Damien Ciabrini (dciabrin)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-quickstart-extras (master)

Reviewed: https://review.opendev.org/747526
Committed: https://git.openstack.org/cgit/openstack/tripleo-quickstart-extras/commit/?id=5c02fd18ef8f6982249ffcad5710ccff3732edaf
Submitter: Zuul
Branch: master

commit 5c02fd18ef8f6982249ffcad5710ccff3732edaf
Author: Damien Ciabrini <email address hidden>
Date: Sat Aug 22 15:25:40 2020 +0200

    Standalone upgrade for HA profile

    Since Ussuri, standalone defaults to HA profile and
    uses a dedicated setting for control-virtual-ip [1].

    When generating the upgrade script, make sure to
    generate the appropriate control-virtual-ip setting
    to keep the pacemaker configuration intact.

    [1] I367cf4b65300be8dca0190b9adeab549018d4a56

    Closes-Bug: #1886529

    Change-Id: I8e5bf2e3582564cff90f0bb6ef7d5660c1aa2cb5

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

Other bug subscribers

Remote bug watches

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