Bug 894633 - Error updating system data on the server /VERSUS/ Consumer <uuid> has been deleted
Summary: Error updating system data on the server /VERSUS/ Consumer <uuid> has been de...
Keywords:
Status: CLOSED DUPLICATE of bug 798788
Alias: None
Product: Candlepin
Classification: Community
Component: candlepin
Version: 0.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: William Poteat
QA Contact: Eric Sammons
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel70
TreeView+ depends on / blocked
 
Reported: 2013-01-12 19:01 UTC by John Sefler
Modified: 2015-05-14 14:52 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-31 12:39:21 UTC
Embargoed:


Attachments (Terms of Use)

Description John Sefler 2013-01-12 19:01:51 UTC
Description of problem:
After a consumer has been deleted server-side (e.g. using rhsm-web application), the system now receives an "Error updating system data on the server" message when calling subscription-manager facts --update.   This is a new change in response.  The prior response was "Consumer %s has been deleted".   The former message is more accurate.


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


How reproducible:


Steps to Reproduce:
delete a system consumer on the candlepin server and then from the system with the deleted consumer....
# subscription-manager facts --update
Stdout:
Stderr: Error updating system data on the server, see /var/log/rhsm/rhsm.log for more details.
ExitCode: 255
  

Actual results:
Error updating system data on the server, see /var/log/rhsm/rhsm.log for more details.

Expected results:
Consumer 0445a7cd-0159-43fc-96d8-6b47b2363c8c has been deleted


Additional Info:
This failure was revealed by automated test case:
VerifyIdentityIsBackedUpWhenConsumerIsDeletedServerSide_Test

Comment 1 William Poteat 2013-01-31 12:39:21 UTC

*** This bug has been marked as a duplicate of bug 798788 ***


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