Bug 1725145

Summary: Advanced details for Gluster Data Brick are empty (glusterv6.1 ,gluster v6.3)
Product: [oVirt] ovirt-engine Reporter: Strahil Nikolov <hunter86_bg>
Component: Frontend.WebAdminAssignee: Kaustav Majumder <kmajumde>
Status: CLOSED NOTABUG QA Contact: Lukas Svaty <lsvaty>
Severity: high Docs Contact:
Priority: medium    
Version: 4.3.5.2CC: bugs, sabose
Target Milestone: ovirt-4.3.6Keywords: Regression
Target Release: ---Flags: sbonazzo: ovirt-4.3?
pm-rhel: blocker?
sbonazzo: planning_ack?
sbonazzo: devel_ack?
sbonazzo: testing_ack?
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-19 06:33:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Gluster RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Data Brick advanced details screenshot
none
Advanced details of arbiter brick - OK
none
Network-diagram none

Description Strahil Nikolov 2019-06-28 14:04:02 UTC
Created attachment 1585645 [details]
Data Brick advanced details screenshot

Description of problem:
Advanced details for gluster data brick is empty in oVirt Admin UI.Arbiter brick is OK. 

Version-Release number of selected component (if applicable)
oVirt - 4.3.5.2-1.el7
glusterfs-6.3-1.el7.x86_64
glusterfs-api-6.3-1.el7.x86_64
glusterfs-api-devel-6.3-1.el7.x86_64
glusterfs-cli-6.3-1.el7.x86_64
glusterfs-client-xlators-6.3-1.el7.x86_64
glusterfs-coreutils-0.2.0-1.el7.x86_64
glusterfs-devel-6.3-1.el7.x86_64
glusterfs-events-6.3-1.el7.x86_64
glusterfs-extra-xlators-6.3-1.el7.x86_64
glusterfs-fuse-6.3-1.el7.x86_64
glusterfs-geo-replication-6.3-1.el7.x86_64
glusterfs-libs-6.3-1.el7.x86_64
glusterfs-rdma-6.3-1.el7.x86_64
glusterfs-resource-agents-6.3-1.el7.noarch
glusterfs-server-6.3-1.el7.x86_64
libvirt-daemon-driver-storage-gluster-4.5.0-10.el7_6.12.x86_64
nfs-ganesha-gluster-2.7.4-1.el7.x86_64
python2-gluster-6.3-1.el7.x86_64
vdsm-gluster-4.30.22-1.el7.x86_64



How reproducible:
Always.
First noticed on 4.3.4.X and gluster v6.1

Steps to Reproduce:
1.Upgrade to 4.3.5 RC3 (engine & hosts)
2.Go to Advanced Details in Admin UI (Storage -> Volumes -> any gluster volume -> Bricks -> Select data brick -> Advanced Details


Actual results:
Data bricks' advanced details is empty and user can type in the fields
Arbiter brick is OK and advanced details are presented.

Expected results:
Both data bricks to show advanced details just like the arbiter brick.

Additional info:
OS - Windows Server 2016 v1607
Browser:
Firefox 67.0.4 (64bit)
Chrome 75.0.3770.100 (Official Build) (64-bit)
Opera 60.0.3255.165

Comment 1 Strahil Nikolov 2019-06-28 14:04:31 UTC
Created attachment 1585646 [details]
Advanced details of arbiter brick - OK

Comment 2 RHEL Program Management 2019-06-28 15:27:08 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 3 Sahina Bose 2019-07-10 15:57:32 UTC
If you still have this setup, could you attach the vdsm log of the host on which the gluster volume status was queried? (To know which of the hosts, you can check the engine.log for GlusterVolumeAdvancedDetails)

Comment 4 Strahil Nikolov 2019-07-10 16:42:58 UTC
Hi Sahina,

my setup is still the same , but I think I know why it happens.
In the engine I get errors like:
2019-07-10 19:18:00,627+03 WARN  [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler7) [4d777224] Could not associate brick 'gluster1:/gluster_bricks/engine/engine' of volume '30ca1cc2-f2f7-4749-9e2e-cee9d7099ded' with correct network as no gluster network found in cluster '94808fca-f662-45f9-9d6e-463bfc11c1dd'
2019-07-10 19:18:00,628+03 WARN  [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler7) [4d777224] Could not associate brick 'gluster2:/gluster_bricks/engine/engine' of volume '30ca1cc2-f2f7-4749-9e2e-cee9d7099ded' with correct network as no gluster network found in cluster '94808fca-f662-45f9-9d6e-463bfc11c1dd'
2019-07-10 19:18:00,630+03 WARN  [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler7) [4d777224] Could not associate brick 'ovirt3:/gluster_bricks/engine/engine' of volume '30ca1cc2-f2f7-4749-9e2e-cee9d7099ded' with correct network as no gluster network found in cluster '94808fca-f662-45f9-9d6e-463bfc11c1dd'
2019-07-10 19:18:00,631+03 WARN  [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler7) [4d777224] Could not associate brick 'gluster1:/gluster_bricks/data_fast4/data_fast4' of volume '6b98de22-1f3c-4e40-a73d-90d425df986f' with correct network as no gluster network found in cluster '94808fca-f662-45f9-9d6e-463bfc11c1dd'
2019-07-10 19:18:00,633+03 WARN  [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler7) [4d777224] Could not associate brick 'gluster2:/gluster_bricks/data_fast4/data_fast4' of volume '6b98de22-1f3c-4e40-a73d-90d425df986f' with correct network as no gluster network found in cluster '94808fca-f662-45f9-9d6e-463bfc11c1dd'
2019-07-10 19:18:00,634+03 WARN  [org.ovirt.engine.core.vdsbroker.gluster.GlusterVolumesListReturn] (DefaultQuartzScheduler7) [4d777224] Could not associate brick 'ovirt3:/gluster_bricks/data_fast4/data_fast4' of volume '6b98de22-1f3c-4e40-a73d-90d425df986f' with correct network as no gluster network found in cluster '94808fca-f662-45f9-9d6e-463bfc11c1dd'

I will upload a diagram of the setup.
Instead of static routes, I have used entries (/etc/hosts) on ovirt1 that makes it resolve gluster1 as the ip of ovirt1 and gluster2 as the ip of ovirt2.
If you think this setup is unsupported - we can mark it as 'WONTFIX'

Comment 5 Strahil Nikolov 2019-07-10 16:43:34 UTC
Created attachment 1589158 [details]
Network-diagram

Comment 6 Strahil Nikolov 2019-07-10 16:45:08 UTC
Last one didn't sound quite clear.
The /etc/hosts entries that point to ovirt1 and ovirt2 are only on the arbiter (ovirt3) due to the network setup.

Comment 7 Sahina Bose 2019-07-19 06:33:51 UTC
Ok. So the brick details only works if the correct brick is passed. Since the brick info passed to gluster cli would be based on the hostname and not ovirt{1,2,3}://gluster_bricks/data_fast4/data_fast4 the details would fail

I'm closing this as this is expected.