Bug 1633090 - Deployment exited when entered an invalid IP address
Summary: Deployment exited when entered an invalid IP address
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-colonizer
Version: rhgs-3.4
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: Ramakrishna Reddy Yekulla
QA Contact: Rahul Hinduja
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-26 07:50 UTC by Bala Konda Reddy M
Modified: 2019-04-18 09:54 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-18 09:54:44 UTC
Embargoed:


Attachments (Terms of Use)
Deployment exiting when entered invalid ip (361.16 KB, image/jpeg)
2018-09-26 07:50 UTC, Bala Konda Reddy M
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github https://github.com/gluster gluster-colonizer issues 69 0 None None None 2018-11-20 04:55:11 UTC

Description Bala Konda Reddy M 2018-09-26 07:50:22 UTC
Created attachment 1487055 [details]
Deployment exiting when entered invalid ip

Description of problem:
When entered an invalid ip as "192/168/1/0" instead of 192.168.1.0
it should error out and ask again for valid ip but deployment should not exit


Version-Release number of selected component (if applicable):
gluster-colonizer-1.2-2.el7rhgs.noarch
glusterfs-3.12.2-18

How reproducible:
always

Steps to Reproduce:
1. Setup proper RAID configuration
2. Start the gluster-colonizer.py -f "g1-oemid-smci-media.yml"
3. Start the installation and whenever it asks for IP, provide invalid IP as mentioned in the description

Actual results:
Deployment exited 
Attaching the screenshot

Expected results:
It should error out and ask for valid ip and proceed further with the installation


Additional info:

Comment 2 Dustin Black 2018-09-26 13:57:30 UTC
This is curious. It could be a problem in the python library that we use to validate IP input rather than with the colonizer itself.

Does the problem occur only with the example input including / characters, or does the failure occur with _any_ bad input?

Comment 3 Bala Konda Reddy M 2018-09-27 08:48:15 UTC
This is seen only with / character not with any bad input.

when entered alphanumeric with other special characters like @ , _ & ( ) ^
It didn't error out as mentioned in the description and asking for valid ip again.

Comment 4 Ramakrishna Reddy Yekulla 2018-11-20 04:54:43 UTC
Opening an upstream issue for the same bug, https://github.com/gluster/gluster-colonizer/issues/69

Comment 5 Yaniv Kaul 2019-04-18 09:54:44 UTC
Closing all Colonizer BZs (as DEFERRED) as we do not intend to work on them for the time being.


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