Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1267303

Summary: The return code for 'redhat-access-insights' should be 1 when the upload is not successful after unregistering the client from Satellite 6 UI.
Product: Red Hat Enterprise Linux 7 Reporter: Anisha Narang <anarang>
Component: redhat-access-insightsAssignee: jcrafts
Status: CLOSED ERRATA QA Contact: Anisha Narang <anarang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: isenfeld, jcrafts, jmoran
Target Milestone: rcKeywords: Rebase
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
With this update, the return code for 'redhat-access-insights' will be '1' when an upload is not successful after unregistering the client from Satellite 6 UI.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 08:23:36 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:
Bug Depends On:    
Bug Blocks: 1298112    

Description Anisha Narang 2015-09-29 15:04:04 UTC
Description of problem:
The return code for 'redhat-access-insights' should be 1 when the upload is not successful after unregistering the client from Satellite 6 UI.

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


How reproducible:


Steps to Reproduce:
1. Register a VM to RHAI service using redhat-access-inisghts --register
2. From the Satellite 6 UI dashboard, unregister the client.
3. On the client machine, try to upload again:

>>> [10.8.30.181] redhat-access-insights
Attemping to download collection rules from https://qe-sat6-rhel71.usersys.redhat.com:443/redhat_access/r/insights/v1/static/uploader.json
Successfully downloaded collection rules
Attemping to download collection rules GPG signature from https://qe-sat6-rhel71.usersys.redhat.com:443/redhat_access/r/insights/v1/static/uploader.json.asc
Successfully downloaded GPG signature
Verifying GPG signature of Insights configuration
Starting to collect Insights data
Uploading Insights data, this may take a few minutes
Upload attempt 1 of 1 failed! Status Code: 412
All attempts to upload have failed!
Please see /var/log/redhat-access-insights/redhat-access-insights.log for additional information

The return code for the above command is 0, whereas it should be 1.

Actual results:
The return code is 0(success)

Expected results:
The return code should be 1(failure).

Additional info:

Comment 4 Mike McCune 2016-03-28 22:44:25 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 7 errata-xmlrpc 2016-11-04 08:23:36 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://rhn.redhat.com/errata/RHBA-2016-2542.html