Bug 1470528 - Do not blindly ignore subscription-manager errors
Do not blindly ignore subscription-manager errors
Status: ON_QA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: gdeploy (Show other bugs)
3.2
Unspecified Unspecified
unspecified Severity medium
: ---
: RHGS 3.4.0
Assigned To: Sachidananda Urs
Manisha Saini
:
Depends On:
Blocks: 1503134
  Show dependency treegraph
 
Reported: 2017-07-13 02:20 EDT by Sachidananda Urs
Modified: 2017-11-13 10:36 EST (History)
4 users (show)

See Also:
Fixed In Version: gdeploy-2.0.2-14
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
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)

  None (edit)
Description Sachidananda Urs 2017-07-13 02:20:36 EDT
Description of problem:

subscription-manager errors can be of two types:
i. Actual errors (incorrect username/password/network timeout etc)
ii. Error due to `User already subscribed`

Handle the above errors gracefully instead of ignoring the errors blindly.

Refer: BZ #1405966
Comment 3 Sachidananda Urs 2017-09-14 03:36:59 EDT
(In reply to Sachidananda Urs from comment #0)
> Description of problem:
> 
> subscription-manager errors can be of two types:
> i. Actual errors (incorrect username/password/network timeout etc)
> ii. Error due to `User already subscribed`
> 
> Handle the above errors gracefully instead of ignoring the errors blindly.
> 
> Refer: BZ #1405966

The latest version of Ansible invalidates this bug.
subscription-module in Ansible handles the `already subscribed' cases.

I'll keep this bug open for QE to verify.

Steps to reproduce:
===================

Subscribe to CDN with the below config file:

**********************

[hosts]
host-1
host-2
host-3
host-4

#Subscribe to necessary channels
[RH-subscription1]
action=register
username=user@redhat.com
password=<password>
ignore_register_errors=no

**********************

Once subscribed, re-run the configuration file. One should not see
any errors.

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