Bug 1514577

Summary: Import cluster fails with KeyError
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Nishanth Thomas <nthomas>
Component: web-admin-tendrl-commonsAssignee: gowtham <gshanmug>
Status: CLOSED ERRATA QA Contact: Sweta Anandpara <sanandpa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rhgs-3.3CC: fbalak, nthomas, rhinduja, rhs-bugs, sanandpa, sankarshan, ssaha
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tendrl-commons-1.5.4-3.el7rhgs.noarch Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-18 04:37:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nishanth Thomas 2017-11-17 19:29:56 UTC
Description of problem:


Import cluster fails while getting node interface If an interface does not have ip address. It raises KeyError and import cluster is fails

Comment 3 Filip Balák 2017-11-28 09:34:19 UTC
Could you please provide reproducer and expected output for this bug?

Comment 4 Sweta Anandpara 2017-11-30 09:26:59 UTC
Had a cluster which had its IPs on ovirtmgmt interface. Imported that into Web-Admin and that got successfully executed. Did not see any error. 

Moving this bug to verified.

tendrl-grafana-plugins-1.5.4-8.el7rhgs.noarch
tendrl-selinux-1.5.4-1.el7rhgs.noarch
tendrl-node-agent-1.5.4-8.el7rhgs.noarch
tendrl-ansible-1.5.4-2.el7rhgs.noarch
tendrl-monitoring-integration-1.5.4-8.el7rhgs.noarch
tendrl-grafana-selinux-1.5.4-1.el7rhgs.noarch
tendrl-commons-1.5.4-5.el7rhgs.noarch
tendrl-api-1.5.4-3.el7rhgs.noarch
tendrl-api-httpd-1.5.4-3.el7rhgs.noarch
tendrl-notifier-1.5.4-5.el7rhgs.noarch
tendrl-ui-1.5.4-4.el7rhgs.noarch

Comment 6 errata-xmlrpc 2017-12-18 04:37:04 UTC
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/RHEA-2017:3478