Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1321109 - Hang on invalid static ip
Hang on invalid static ip
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance (Show other bugs)
5.4.0
Unspecified Unspecified
medium Severity medium
: GA
: 5.6.0
Assigned To: Šimon Lukašík
luke couzens
appliance:black
: ZStream
Depends On:
Blocks: 1334934
  Show dependency treegraph
 
Reported: 2016-03-24 12:54 EDT by luke couzens
Modified: 2016-06-29 11:44 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1334934 (view as bug list)
Environment:
Last Closed: 2016-06-29 11:44:41 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 14:50:04 EDT

  None (edit)
Description luke couzens 2016-03-24 12:54:06 EDT
Description of problem:setting invalid ip cause an infinite hang when applying


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


How reproducible:100%


Steps to Reproduce:
1.ssh into appliance
2.start appliance_console
3.setup static ip with invalid ip address


Actual results:Applying static network configuration (never finishes)


Expected results:invalid ip address 


Additional info:

Static Network Configuration

        IP Address:      01.01.01.01
        Netmask:         255.255.252.0
        Gateway:         10.16.7.254
        Primary DNS:     10.10.160.1
        Secondary DNS:   
        Search Order:    rhq.lab.eng.bos.redhat.com

Apply static network configuration? (Y/N)
y

Applying static network configuration...
Comment 3 luke couzens 2016-04-01 14:11:13 EDT
Bug also in 5.5.3.2
Comment 4 Šimon Lukašík 2016-04-12 04:52:10 EDT
Luke, I cannot reproduce this in 5.5.3.2. The 5.5.3.2 seems to have nice
error message 

    01.01.01.01 is not a valid IPv4 or IPv6 address> (NoMethodError)

instead of hanging on. This has been fixed by Nick, who has rewrote
static network handling in

    https://github.com/ManageIQ/manageiq/pull/4877

I am flipping this ON_QA. Please let me know if this is not appropriate
state in this case.
Comment 5 luke couzens 2016-04-12 05:40:35 EDT
Hi Simon,

Just checked this and you are correct, however this error still crashes out of appliance console. I would expect it to just request a correct IP not require the user to launch appliance_console again.

Hope this helps.
Comment 6 Šimon Lukašík 2016-04-12 11:40:15 EDT
Yeah, right. It crashes. I have fixed the crash in https://github.com/ManageIQ/manageiq/pull/7823

Can you confirm that the traceback contains word 'massage'?
Comment 7 luke couzens 2016-04-26 14:18:40 EDT
Verified in 5.6.0.4-beta2.3
Comment 8 luke couzens 2016-05-04 11:11:33 EDT
Appliance_console also crashes in 5.5.4.0
Comment 11 errata-xmlrpc 2016-06-29 11:44:41 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1348

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