Bug 1662394

Summary:	Gdeploy execution is failing with IPV6
Product:	[oVirt] cockpit-ovirt	Reporter:	Gobinda Das <godas>
Component:	Gdeploy	Assignee:	Sachidananda Urs <surs>
Status:	CLOSED NOTABUG	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	high
Version:	0.11.29	CC:	bugs, fkust, sabose, surs
Target Milestone:	ovirt-4.3.2	Flags:	rule-engine: ovirt-4.3+ surs: devel_ack+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously, if the gdeploy config file contained the following header formatting [feature:host] the host's IP address was incorrectly parsed. In this release, gdeploy now correctly parses the section header for both ipv4 and ipv6 addresses.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-18 06:47:25 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:
Bug Depends On:	1624708, 1680596
Bug Blocks:

Description Gobinda Das 2018-12-28 07:04:18 UTC

Description of problem:
Now if we provide IPV6(128 bit address with colon separated) the gdeploy configuration file takes the first colon value as it's splitting with (:) and because of that the whole gluster deployment processing is failing. 

Version-Release number of selected component (if applicable):


How reproducible:
Always 

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
 Gdeploy should treat the complete ipv6 as a single unit.

Additional info:

Comment 1 Sachidananda Urs 2018-12-31 05:22:01 UTC

PR: https://github.com/gluster/gdeploy/pull/522 fixes the issue.

Comment 2 Sandro Bonazzola 2019-01-28 09:44:25 UTC

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 3 Gobinda Das 2019-02-27 11:04:06 UTC

As we replaced gdeploy with gluster-ansible roles. Do we still need this for gdeploy?

Comment 4 Sachidananda Urs 2019-02-28 12:08:08 UTC

(In reply to Gobinda Das from comment #3)
> As we replaced gdeploy with gluster-ansible roles. Do we still need this for
> gdeploy?

We do not need this for now immediately. But if someone wants to use gdeploy
they can use this patch. We need not prioritise this for rhhi.

Comment 5 Sahina Bose 2019-03-18 06:47:25 UTC

Since gdeploy is not the underlying tool used for deployment, this bug is no longer relevant