[katello-devel] Registering pre-registered system (uh)

[Bryan Kearney]

On 12/10/2012 09:37 AM, Cliff Perry wrote:
> On 12/10/2012 02:20 PM, Bryan Kearney wrote:
>> On 12/10/2012 09:14 AM, Lukas Zapletal wrote:
>>> Okay, strange subject but...
>>>
>>> Well, I have added new system using CLI/UI with name "XYZ" and then
>>> registered a system using rhsm under this name. New system entry is
>>> created while I'd expected the one I have created is
>>> reused.
>>>
>>> Is this correct behavior?
>>
>> We do have a duplicate issue. The only way to work around this is to use
>> the UUID during registration, which will pull down the latest version of
>> the consumer with the same UUID.
>>
> Any way to make this happen automagically? (my guess is new code in both
> client and server).
>
>   - I don't quite know/understand why you would allow to manually create
> a system profile within UI, prior to the attempted registration of said
> system. But the correct way today to do this, seems to be by documenting
> the usage of --consumerid at time of registering system with rhsm.


My guess is that this is background for the design on how to register a 
system record and then provision it via foreman and have it all "just work"


>
>>>
>>> I'd expect the entry in Katello to be reused. That would question the
>>> New System button in Katello completely.
>>>
>>> ps - the same for hostname as name
>>>
>>
>> We have the same "duplicate system" issue which spacewalk has,
>> unfortunately.
> Yes. I know today the rhsm client code does a good job in trying to
> prevent duplicates.
>
> I guess, the biggest kicker is, what is the use case in allowing the
> creation in UI prior to registration. And then if that use case is
> valid, is there a way to get it to do the right thing and not create a
> duplicate.

Provisioning.

You create the system record, rack the machine, turn it on, and Katello 
"does the needful". This is how foreman works today.

-- bk