Bug 2023344
Summary: | vdsmd fails to shut down cleanly when it tries to deactivate a used LV | ||
---|---|---|---|
Product: | [oVirt] vdsm | Reporter: | Milan Zamazal <mzamazal> |
Component: | Core | Assignee: | Nir Soffer <nsoffer> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | sshmulev |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.50.0.1 | CC: | bugs, dfodor, eshames |
Target Milestone: | ovirt-4.4.10 | Keywords: | ZStream |
Target Release: | 4.40.100.1 | Flags: | pm-rhel:
ovirt-4.4+
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | vdsm-4.40.100.1 | Doc Type: | Bug Fix |
Doc Text: |
Cause:
Vdsm tried to deactivate logical volumes during shutdown.
Consequence:
Vdsm shutdown can fail, or programs using logical volumes managed by vdsm could fail.
Fix:
Vdsm does not deactivate logical volumes during shutdown.
Result:
Vdsm shutdown faster and programs using logical volumes managed by vdsm are not affected.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2022-01-19 07:00:13 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Milan Zamazal
2021-11-15 13:19:53 UTC
(In reply to Milan Zamazal from comment #0) > Expected results: > > vdsmd stops cleanly within TimeoutStopSec interval, logging "[vds] Exiting" > as its last log message. This is not possible to guarantee. The expect result is not to tear down storage during shutdown. Tearing down storage must be done only when engnine ask to deactivate storage domain or disconnect from storage. When the vdsmd service stop, storage should be left as is. Storage domains that were active before vdsm was stopped should remain active. Testing this change: 1. Make sure host is up in a data center with active storage domain 2. List active special volumes: # lvs | egrep 'ids|inbox|leases|measter|metadata|outbox|xleases' ids 313e6d78-80f7-41ab-883b-d1bddf77a5da -wi-ao---- 128.00m inbox 313e6d78-80f7-41ab-883b-d1bddf77a5da -wi-a----- 128.00m leases 313e6d78-80f7-41ab-883b-d1bddf77a5da -wi-a----- 2.00g metadata 313e6d78-80f7-41ab-883b-d1bddf77a5da -wi-a----- 128.00m outbox 313e6d78-80f7-41ab-883b-d1bddf77a5da -wi-a----- 128.00m xleases 313e6d78-80f7-41ab-883b-d1bddf77a5da -wi-a----- 1.00g ids 4345b708-77ab-4477-9d7b-b9e6d053cb1f -wi-ao---- 128.00m inbox 4345b708-77ab-4477-9d7b-b9e6d053cb1f -wi-a----- 128.00m leases 4345b708-77ab-4477-9d7b-b9e6d053cb1f -wi-a----- 2.00g metadata 4345b708-77ab-4477-9d7b-b9e6d053cb1f -wi-a----- 128.00m outbox 4345b708-77ab-4477-9d7b-b9e6d053cb1f -wi-a----- 128.00m xleases 4345b708-77ab-4477-9d7b-b9e6d053cb1f -wi-a----- 1.00g ids feab3738-c158-4d48-8a41-b5a95c057a50 -wi-ao---- 128.00m inbox feab3738-c158-4d48-8a41-b5a95c057a50 -wi-a----- 128.00m leases feab3738-c158-4d48-8a41-b5a95c057a50 -wi-a----- 2.00g metadata feab3738-c158-4d48-8a41-b5a95c057a50 -wi-a----- 128.00m outbox feab3738-c158-4d48-8a41-b5a95c057a50 -wi-a----- 128.00m xleases feab3738-c158-4d48-8a41-b5a95c057a50 -wi-a----- 1.00g ids ffc11717-c272-4a41-be97-9ac75d401413 -wi-ao---- 128.00m inbox ffc11717-c272-4a41-be97-9ac75d401413 -wi-a----- 128.00m leases ffc11717-c272-4a41-be97-9ac75d401413 -wi-a----- 2.00g metadata ffc11717-c272-4a41-be97-9ac75d401413 -wi-a----- 128.00m outbox ffc11717-c272-4a41-be97-9ac75d401413 -wi-a----- 128.00m xleases ffc11717-c272-4a41-be97-9ac75d401413 -wi-a----- 1.00g 3. On the host, stop the vdsmd service systemctl stop vdsmd 4. Make sure this log does not apear: INFO ... [storage.blocksd] Tearing down domain 186180cb-5cc5-4aa4-868a-9e1ed7965ddf (blockSD:996)\ 5. Check that the active special volumes were not deactivated To reproduce, use vdsm from 4.4.9. After stopping it, all the special lvs except "ids" will be inactive. Verified. Versions: ovirt-engine-4.4.10-0.17.el8ev vdsm-4.40.100.1-1.el8ev Steps to reproduce as described in comment2. Also tried to reproduce it on 4.4.9 - Same steps and got the line of "2021-11-24 15:29:18,672+0200 INFO (monitor/6cf08a4) [storage.BlockSD] Tearing down domain 6cf08a47-7cdc-42b1-b7d5-7c685a0ef45e (blockSD:995) " In this version(4.4.10), it does not reproduce, and the special volumes didn't activate. This bugzilla is included in oVirt 4.4.10 release, published on January 18th 2022. Since the problem described in this bug report should be resolved in oVirt 4.4.10 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |