Bug 718052

Fixed in master 66df558b891a2cacbf2d642e043ecc409d4dd201.

Created attachment 510770 [details]
System Registration" dialog still shows "owners"

In the "System Registration" dialog, it still shows:
  Fetching list of possible owners.....

[root@jsefler-onprem-62server ~]# subscription-manager register --username=testuser1 --password=password --org=foo
Owner foo does not exist
^^^^^                   ^
Org                     .  < don't forget punctuation


[root@jsefler-onprem-62server ~]# subscription-manager register --username=testuser1 --password=password
Must specify owner for new consumer.
             ^^^^^
             org

[root@jsefler-onprem-62server ~]# subscription-manager register --username=testuser3 --password=password
User testuser3 cannot access owner admin
                             ^^^^^      ^
                             org        .

Is this really the best message for a READ_ONLY user?  I don't yet know enough about READ_ONLY user to suggest a better message.

c4 is fixed in subscription manager
6a18499c43b4d2c767ff9921d567bab96f14be97

c5 and c6 will require a new build of candlepin. 6b245c82c2f0bf8cf156b7b5ec3873b2da2c025a

[root@jsefler-onprem-62server ~]# rpm -q subscription-manager
subscription-manager-0.96.2-1.git.19.47243e5.el6.x86_64

[root@jsefler-onprem-62server ~]# subscription-manager register --username=testuser1
Password: 
You must specify an organization/owner for new consumers.

                    ^^^^^^^^^^^^^^^^^^
                    Is this really what we want?
                    Can't we make up our mind?
                    How will this translate to other languages?
                    more org, less owner

fixed in candlepin in 5d02aa2a9c94ff3902e0e64d33c707343ae13576.

Verifying Version....
[root@jsefler-onprem-62server ~]# rpm -q subscription-manager
subscription-manager-0.96.11-1.git.7.15fc9d2.el6.x86_64

Verifying the use of Org/Organization in all of the following uses...

[root@jsefler-onprem-62server ~]# subscription-manager register --username=testuser1 --password=password
You must specify an organization for new consumers.


[root@jsefler-onprem-62server ~]# subscription-manager register --username=testuser1 --password=password --org=admin
The system has been registered with id: 0b4d28eb-95c4-4713-9c29-ad6d15bceca7 


[root@jsefler-onprem-62server ~]# subscription-manager register --username=testuser1 --password=password --org=foo --force
The system with UUID 0b4d28eb-95c4-4713-9c29-ad6d15bceca7 has been unregistered
Organization foo does not exist.


[root@jsefler-onprem-62server ~]# subscription-manager register --username=testuser3 --password=password
testuser3 cannot register to any organizations.


[root@jsefler-onprem-62server ~]# subscription-manager identity
Current identity is: 0b4d28eb-95c4-4713-9c29-ad6d15bceca7 
name: jsefler-onprem-62server.usersys.redhat.com 
org name: Admin Owner 
org id: 8a90f8c63296bc55013296bcd0890006


[root@jsefler-onprem-62server ~]# subscription-manager orgs --username=testuser1 --password=password
+-------------------------------------------+
          testuser1 Organizations
+-------------------------------------------+

OrgName: 	Snow White               
OrgKey: 	snowwhite                

OrgName: 	Admin Owner              
OrgKey: 	admin

Created attachment 524703 [details]
Fetching list of possible organizations

Verifying Version...
[root@jsefler-onprem-62server ~]# rpm -q subscription-manager-gnome
subscription-manager-gnome-0.96.11-1.git.7.15fc9d2.el6.x86_64

Created attachment 524704 [details]
Organization: label in the facts dialog

Moving to verified

NOTE... The use of owner still exists in the Candlepin API and JSON data.  This can be opened as a separate bug.

On candlepin server...
cd /root/candlepin/proxy
buildr candlepin:apicrawl
cat target/candlepin_methods.json | python -mjson.tool | grep owner
                "owner": {
                "owner": {
        "description": "Create a Consumer. NOTE: Opening this method up to everyone, as we have\n nothing we can reliably verify in the method signature. Instead we have\n to figure out what owner this consumer is destined for (due to backward\n compatability with existing clients which do not specify an owner during\n registration), and then check the access to the specified owner in the\n method itself.", 
                "name": "owner", 
        "url": "/consumers/{consumer_uuid}/owner", 
                "name": "owner", 
                "ownerId": {
                "name": "owner", 
        "description": "Allow the creation of an activation key from the owner resource", 
                "owner": {
        "url": "/owners/{owner_key}/activation_keys", 
            "owner_key"
        "url": "/owners", 
                "owner": {
        "url": "/owners/{owner_key}/subscriptions", 
            "owner_key"
        "url": "/owners/{owner_key}/uebercert", 
            "owner_key"
        "description": "Deletes an owner", 
        "url": "/owners/{owner_key}", 
        "url": "/owners/{owner_key}/consumers/{consumer_uuid}/atom", 
            "owner_key"
        "url": "/owners/{owner_key}/events", 
            "owner_key"
        "url": "/owners/{owner_key}/imports", 
            "owner_key"
        "description": "Return the owner identified by the given ID.", 
        "url": "/owners/{owner_key}", 
            "owner_key"
        "url": "/owners/{owner_key}/atom", 
            "owner_key"
        "description": "Return the owner's info identified by the given ID.", 
                        "ownerId": {
                            "ownerId": {
                            "ownerId": {
        "url": "/owners/{owner_key}/info", 
            "owner_key"
        "description": "Return the entitlement pools for the owner of the given id.", 
        "url": "/owners/{owner_key}/pools", 
            "owner_key"
        "url": "/owners/{owner_key}/statistics/{qtype}/{vtype}", 
            "owner_key"
        "url": "/owners/{owner_key}/subscriptions", 
            "owner_key"
        "url": "/owners/{owner_key}/uebercert", 
            "owner_key"
        "url": "/owners/{owner_key}/imports", 
            "owner_key"
        "url": "/owners", 
        "description": "Return the activation keys for the owner of the given id.", 
        "method": "org.fedoraproject.candlepin.resource.OwnerResource.ownerActivationKeys", 
        "url": "/owners/{owner_key}/activation_keys", 
            "owner_key"
        "description": "Return the consumers for the owner of the given id.", 
        "method": "org.fedoraproject.candlepin.resource.OwnerResource.ownerConsumers", 
        "url": "/owners/{owner_key}/consumers", 
            "owner_key"
        "description": "Return the entitlements for the owner of the given id.", 
        "method": "org.fedoraproject.candlepin.resource.OwnerResource.ownerEntitlements", 
        "url": "/owners/{owner_key}/entitlements", 
            "owner_key"
        "description": "'Tickle' an owner to have all of their entitlement pools synced with\n their subscriptions. This method (and the one below may not be entirely\n RESTful, as the updated data is not supplied as an argument.", 
                "name": "auto_create_owner", 
        "url": "/owners/{owner_key}/subscriptions", 
        "description": "expose updates for owners", 
        "url": "/owners/{owner_key}", 
            "owner_key"
        "url": "/owners/subscriptions", 
        "deprecated": "Use the method on /owners", 
                "description": "if both consumer and owner are given, or if a product id is specified without a consumer or owner", 
                "description": "if a specified consumer or owner is not found", 
                "name": "owner", 
                            "owner": {
                            "owner": {
                            "owner": {
                            "owner": {
                            "owner": {
                            "owner": {
                            "owner": {
                "owner": {
        "url": "/users/{username}/owners", 
[root@jsefler-onprem-62candlepin proxy]#

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.

http://rhn.redhat.com/errata/RHBA-2011-1695.html