Bug 2264175 - Glusterfs Storage Domain based can't be activated if the Storage Server is down
Summary: Glusterfs Storage Domain based can't be activated if the Storage Server is down
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 4.5.3
Hardware: All
OS: All
high
high
Target Milestone: ovirt-4.5.3-1
: ---
Assignee: José Enrique
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-02-14 11:47 UTC by José Enrique
Modified: 2024-06-10 11:57 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-10 11:56:59 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt vdsm pull 414 0 None open Backport: get gluster volume info from any gluster peer 2024-05-02 08:45:53 UTC
Red Hat Product Errata RHBA-2024:3750 0 None None None 2024-06-10 11:57:00 UTC

Description José Enrique 2024-02-14 11:47:03 UTC 
Description of problem:

Glusterfs Storage Domain based can't be activated if the Storage Server is down

Version-Release number of selected component (if applicable):
- RHHI 1.8
- vdsm 4.5.3.1

How reproducible:
Always


Steps to Reproduce:
1. Put on maintenance the vmstore SD.
2. Shutdown the Storage Server.
3. vmstore SD can't be activated.

Actual results:

Storage Domain can't be activated even the glusterfs is quorated.

Expected results:

Activate Storage Domain without needing the Storage Server available.

Additional info:
Comment 8 meital avital 2024-06-06 10:28:53 UTC 
Moving to Verified according to QE automation Passed successfully.
Comment 10 errata-xmlrpc 2024-06-10 11:56:59 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (vdsm bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2024:3750
Note You need to log in before you can comment on or make changes to this bug.