Prevent Gluster Volume being monitored by oVirt

2 May
2019
2 May
'19
1:01 p.m.
Dear all We are running a oVirt GlusterFS hyperconverged setup with arbiter version 4.2.6.4-1.el7 here. It looks like we are affected by this bug https://bugzilla.redhat.com/show_bug.cgi?id=1614430 with one or more gluster volumes that are not storage domains of oVirt. Is there a way to exclude them from monitoring (vdsm-gluster) or to prevent being added to the engine's database? Thanks Simon
2294
Age (days ago)
2294
Last active (days ago)
0 comments
1 participants
participants (1)
-
smirta@gmx.net