Bug 1193999 - When creating GlusterFS volumes, bricks should be chosen from peers instead of management FQDN/IP
Summary: When creating GlusterFS volumes, bricks should be chosen from peers instead o...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: ---
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-3.6.7
: ---
Assignee: Sahina Bose
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On: 1049994
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-18 18:03 UTC by Stefano Stagnaro
Modified: 2016-07-04 12:31 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-04 12:31:24 UTC
oVirt Team: Gluster
Embargoed:
sabose: ovirt-3.6.z?
ylavi: planning_ack?
rule-engine: devel_ack+
knarra: testing_ack+


Attachments (Terms of Use)
Attaching screenshot where user is failed to attach the glusternw role to a network (177.96 KB, image/png)
2016-02-16 09:34 UTC, RamaKasturi
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 53672 0 master ABANDONED engine: Add gluster network as additional feature 2016-08-14 01:56:05 UTC

Description Stefano Stagnaro 2015-02-18 18:03:06 UTC
Description of problem:
The problem arise once you manually change the network for GlusterFS synchronization (as described here: http://www.ovirt.org/Change_network_interface_for_Gluster). Webadmin lose the capability to create new GlusterFS volumes. Resolution of bug 1049994 will maybe overcome this problem.

		management FQDN		GlusterFS FQDN
node 1:		s20.ovirt.prisma	s20gfs.ovirt.prisma
node 2:		s21.ovirt.prisma	s21gfs.ovirt.prisma


Version-Release number of selected component (if applicable):
ovirt-engine-webadmin-portal-3.5.1.1-1.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. put GlusterFS hosts acting as bricks in maintenance
2. detach every peer from the CLI
3. add them back with IP/FQDN of the desired network
4. activate GlusterFS hosts
5. try to create a new volume from the Webadmin


Actual results:
Webadmin shows error: "Error while executing action Create Gluster Volume: Unexpected exception"
Engine log shows error: "error: Host s20.ovirt.prisma is not in 'Peer in Cluster' state"

Expected results:
Webportal should use FQDN/IP from node peers as bricks (instead of management FQDN/IP).

Additional info:

[root@s20 ~]# gluster peer status
                                                                
Number of Peers: 1

Hostname: s21gfs.ovirt.prisma
Uuid: 44be4447-2d44-41b3-b42a-f9a8d998f7d4
State: Peer in Cluster (Connected)

Comment 1 Sahina Bose 2015-02-23 05:44:30 UTC
Please note that with resolution of Bug 1049994, the peers would be added with IP address of the interface (not the alternate FQDN)

Comment 2 Red Hat Bugzilla Rules Engine 2015-10-19 10:52:27 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 3 Sandro Bonazzola 2015-10-26 12:31:52 UTC
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015.
Please review this bug and if not a blocker, please postpone to a later release.
All bugs not postponed on GA release will be automatically re-targeted to

- 3.6.1 if severity >= high
- 4.0 if severity < high

Comment 4 Sahina Bose 2015-10-30 11:58:01 UTC
Please let us know if you face issue with latest 3.6 builds and applying gluster network role to your interface.

Comment 5 Red Hat Bugzilla Rules Engine 2015-11-02 12:26:47 UTC
Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA.

Comment 7 RamaKasturi 2016-02-16 09:31:25 UTC
Moving this bug back as gluster network is not supported in 3.5 with additional features.

when created a cluster and trying to attach the role as gluster network to a network it fails with error "Error while executing action: Gluster networks are not supported in this cluster compatibility version".

Comment 8 Red Hat Bugzilla Rules Engine 2016-02-16 09:31:32 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 9 RamaKasturi 2016-02-16 09:34:10 UTC
Created attachment 1127546 [details]
Attaching screenshot where user is failed to attach the glusternw role to a network

Comment 11 Sahina Bose 2016-04-18 12:15:19 UTC
Kasturi, can you verify this with upstream version?

The patch to add network as additional feature is still pending ack due to comments related to support of 3.5 in master.

Comment 12 Yaniv Kaul 2016-05-04 18:18:08 UTC
Pushed to 3.6.7, let me know if it's a blocker and should be returned to 3.6.6

Comment 13 Sahina Bose 2016-05-05 09:41:22 UTC
(In reply to Yaniv Kaul from comment #12)
> Pushed to 3.6.7, let me know if it's a blocker and should be returned to
> 3.6.6

ack - this is fine.

Comment 14 RamaKasturi 2016-06-06 10:44:06 UTC
Verified and works fine with rhevm-3.6.7.2-0.1.el6.noarch.

When user selects to add brick Host text box in the Add Bricks Dialog shows Mgmnt/IP. But when user gives the path to the brick and say ok, it creates the brick using glusternw ip.


Note You need to log in before you can comment on or make changes to this bug.