Loading...

XML

Word

Printable

Type: Bug
Resolution: Done-Errata
Priority: Undefined
Fix Version/s: rhel-9.4
Affects Version/s: rhel-9.0.0.z, rhel-9.2.0, rhel-9.2.0.z, rhel-9.3.0.z
Component/s: libvirt / Storage
Labels:

Fixed in Build:
libvirt-9.9.0-1.el9
Severity:
Major

Pool Team:

sst_virtualization_storage
Sub-System Group:

ssg_virtualization

Dev Target Milestone:
13
Internal Target Milestone:
17
Story Points:
3
ACKs Check:

QE ack, Dev ack
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Product Documentation Required:
None
Sprint:
None

Preliminary Testing:
Pass
Test Link:
https://polarion.engineering.redhat.com/polarion/#/project/RHELVIRT/workitem?id=VIRT-300253
Errata Link:
https://errata.devel.redhat.com/advisory/125049
Test Coverage:

Automated

Release Note Type:
If docs needed, set a value

Experience:
Architecture:

Unspecified
Target Upstream Version:
9.7.0
Bugzilla Bug:
RHBZ: 2228223

PX Impact Score:
PX Priority Data:
PX Review Complete:
SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Planning:
None

Description of problem:
When configuring a logical storage pool virsh, the storage pool will automatically go into an "inactive" state after a short period of time (5-10 minutes).

Version-Release number of selected component (if applicable):
kernel-5.14.0-284.11.1.el9_2.x86_64 Thu Jun 22 07:07:42 2023
libvirt-9.0.0-10.2.el9_2.x86_64
lvm2-2.03.17-7.el9.x86_64

How reproducible:
100%

Steps to Reproduce:
1. install qemu-kvm libvirt virt-install virt-viewer
2. virsh pool-define-as storage-pool logical --source-dev /dev/sda --target=/dev/storage-pool
3. virsh pool-build storage-pool
4 virsh pool-start storage-pool
5. virsh pool-autostart storage-pool

Actual results:

date ; virsh pool-list --all
Tue Aug 1 07:49:35 AM EDT 2023
Name State Autostart
-----------------------------------------------------
storage-pool active yes

date ; virsh pool-list --all
Tue Aug 1 07:55:03 AM EDT 2023
Name State Autostart
-------------------------------------------------------
storage-pool inactive yes

Expected results:
For the storage pool to stay active or autostart if virtstoraged is restarted.

Additional info:
It appears that virt*d.service are being restarted
~~~
Aug 1 07:55:03 hostname systemd[1]: Starting Virtualization qemu daemon...
Aug 1 07:55:03 hostname systemd[1]: Started Virtualization qemu daemon.
Aug 1 07:55:03 hostname systemd[1]: Starting Virtualization storage daemon...
Aug 1 07:55:03 hostname systemd[1]: Started Virtualization storage daemon.
Aug 1 07:55:26 hostname systemd[1]: Starting Virtualization network daemon...
Aug 1 07:55:26 hostname systemd[1]: Started Virtualization network daemon.
Aug 1 07:55:27 hostname systemd[1]: Starting Virtualization nwfilter daemon...
Aug 1 07:55:27 hostname systemd[1]: Started Virtualization nwfilter daemon.
Aug 1 07:55:27 hostname systemd[1]: Starting Virtualization nodedev daemon...
Aug 1 07:55:27 hostname systemd[1]: Started Virtualization nodedev daemon.
Aug 1 07:55:37 hostname systemd[89815]: Starting Virtual filesystem service...
Aug 1 07:55:37 hostname systemd[89815]: Started Virtual filesystem service.
~~~