system host-lock controller failed to execute

Bug #1966809 reported by Iago Filipe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
Critical
Iago Filipe

Bug Description

Brief Description
-----------------
When host lock controller the following error message is provided: Only 0 storage monitor available. At least 1 unlocked and enabled hosts with monitors are required. Please ensure hosts with monitors are unlocked and enabled.

Severity
--------
Critical

Steps to Reproduce
------------------
system host-lock <controller>

Expected Behavior
------------------
Lock controller.

Actual Behavior
----------------
Fails to lock controller.

Reproducibility
---------------
Reproducible

System Configuration
--------------------
Multi-node system

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to config (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/config/+/835489

Changed in starlingx:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to config (master)

Reviewed: https://review.opendev.org/c/starlingx/config/+/835489
Committed: https://opendev.org/starlingx/config/commit/93eece12a66abddc0bf503d685e34e7c2d118182
Submitter: "Zuul (22348)"
Branch: master

commit 93eece12a66abddc0bf503d685e34e7c2d118182
Author: Iago Estrela <email address hidden>
Date: Mon Mar 28 16:42:03 2022 -0300

    Fix system host-lock controller

    With https://review.opendev.org/c/starlingx/config/+/833468
    changes, host-lock controller started to fail. It should also
    check if the host is included in the active monitors list as
    it was prior to 833468 change.

    PASS: Host lock successfully.
    PASS: Host force lock successfully.

    Closes-Bug: 1966809
    Closes-Bug: 1965945

    Signed-off-by: Iago Estrela <email address hidden>
    Change-Id: I25ffbb676481eaf0c126d3691249f725ff880f36

Changed in starlingx:
status: In Progress → Fix Released
Revision history for this message
Ghada Khalil (gkhalil) wrote :

Screening: stx.7.0 / critical - issue introduced due to recent code changes and prevent a basic operation (host lock)

Changed in starlingx:
importance: Undecided → Critical
tags: added: stx.7.0 stx.config
Changed in starlingx:
assignee: nobody → Iago Filipe (ifest1)
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.