[katello-devel] moving of systems between environments

[Sachin Ghai]

On 08/15/2012 06:05 AM, Mike McCune wrote:
> On 08/14/2012 07:25 AM, Lukas Zapletal wrote:
>> On Tue, Aug 14, 2012 at 01:56:29PM +0100, Dmitri Dolguikh wrote:
>>> Hey all,
>>>
>>> the above functionality is in master as of yesterday.
>>>
>>> To move the system using web ui: on system detail screen, change the
>>> environment name to the one you intend to move the system to. Once
>>> completed, the system will reside in the new environment.
>>> To move the system via cli: katello system update --org=Blah
>>> --name=My_system --new_environment=<environment name goes here>
>>>
>>> To verify that the system has been moved successfully: pull
>>> entitlement certificate and verify that the content urls have been
>>> updated to use the new environment. Please note that if the content
>>> that the system has been subscribed to is not available in the new
>>> environment, the entitlement certificate is not going to have it
>>> either.
>>>
>>
>> Great. And how does a real-world scenario look like? I mean, does rhsm
>> automatically pull entitlement certs every X hours? Or do I need to take
>> some explicit action on the client?
>>
>>
>
> I would imagine a 'subscription-manager refresh' would do it... that
> said, I tried out the above with an install of the latest from git. Some
> notes:
>
> * The webUI worked fine, the system shows up in the next environment I
> moved it to
>
> * Tried a 'subscription-manager refresh' and took a look at the
> redhat.repos file and it still pointed at /dev/ but I had moved the
> system to test
>
> * tried 'yum repolist', same thing

I observed same behaviour. Since I moved the system from 'test' to 'dev' 
env, the redhat.repo was still showing the 'test' in URL.

Content URLs in entitlement cert also points to 'test' env instead of 
dev.  Logs are here:
http://pastebin.test.redhat.com/102204

Regards,
-Sachin