Bug 1520928 - Colonizer throws traceback messages and exits when user enters invalid storage network or CIDR details
Summary: Colonizer throws traceback messages and exits when user enters invalid storag...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-colonizer
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Dustin Black
QA Contact: Rahul Hinduja
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-05 13:23 UTC by Nag Pavan Chilakam
Modified: 2019-04-18 09:54 UTC (History)
2 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:48 UTC
Embargoed:


Attachments (Terms of Use)

Description Nag Pavan Chilakam 2017-12-05 13:23:22 UTC
Description of problem:
============================
if some option entered is invalid or enter wrong details, I see script tracebacks  being thrown  on screen
instead we should log them into a file and throw the right and meaningful human readable error
eg:
enter a invalid ip as below
storage n/w and cidr mask: 192.168.1/0/24 (entered 1/0 instead of 1.0 accidentally)

see attached screenshot for the o/p

Comment 2 Dustin Black 2017-12-11 20:28:26 UTC
This might be worth two separate BZs. The request made here to capture the tracebacks and provide better error reporting I would consider to be more of an RFE. However, the specific failure when validating the bad CIDR failure is happening in the IPAddress module and should be fixed.

Comment 3 Nag Pavan Chilakam 2018-04-18 12:03:08 UTC
changing title based on comment#2 and also raised new bug bz#1568898 to track issue of redirecting tracebacks to a file

Comment 4 Nag Pavan Chilakam 2018-04-20 12:40:28 UTC
same happens when we mention manually for VIP IPs in ganesha setup , ie 192.168.1.2/12

Comment 7 Yaniv Kaul 2019-04-18 09:54:48 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.