Bug 1390023 - [ceph-iscsi-ansible] bogus client IQN causes a python backtrace
Summary: [ceph-iscsi-ansible] bogus client IQN causes a python backtrace
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat Storage
Component: ceph-ansible
Version: 2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 2
Assignee: Paul Cuzner
QA Contact: ceph-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-30 22:45 UTC by Paul Cuzner
Modified: 2016-11-22 23:42 UTC (History)
11 users (show)

Fixed In Version: ceph-iscsi-ansible-1.5-1.el7cp ceph-iscsi-config-1.5-1.el7cp
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-22 23:42:30 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2817 0 normal SHIPPED_LIVE ceph-iscsi-ansible and ceph-ansible bug fix update 2017-04-18 19:50:43 UTC

Description Paul Cuzner 2016-10-30 22:45:39 UTC
Description of problem:
When an invalid IQN is provided in the group_vars file, the client module attempts to create a NodeACL - this fails with an uncaught RTSLIBerror/backtrace

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

How reproducible:
Every time

Steps to Reproduce:
1. Create a group_vars file with an invalid iqn - i.e. use '_' in the iqn name
2. run the playbook
3.

Actual results:
playbook fails with backtrace

Expected results:
client iqn should be validated, and failed gracefully with an appropriate message to the admin

Additional info:

Comment 2 Paul Cuzner 2016-11-02 04:36:23 UTC
please test with 1.5 release

Comment 3 Tejas 2016-11-02 09:20:20 UTC
Verified in build:
ceph-iscsi-ansible-1.5-1.el7test.noarch
ceph-iscsi-config-1.5-1.el7test.noarch

A proper error message is shown here

Comment 6 errata-xmlrpc 2016-11-22 23:42:30 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/RHBA-2016:2817


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