When destroying RedHat cluster, machines are not unregistered

[Christian Huebner]

I just found over 800 machine entries in a RHN account, all of them created by Fuel (3.2) but never destroyed upon destruction of the clusters.

When the cluster is destroyed, the machines must be unregistered from RHN.

Please fix.

[Matthew Mosesohn (raytrac3r)]

Mike, this needs to be created as a task in Nailgun. I created PRD-1211 in July which is assigned to Andrey.

[Mike Scherbakov (mihgen)]

It is rather a feature . If it goes deep to nailgun, I believe we need blueprint then instead. I don't see how we can fit it into 4.0 as we are close to feature freeze.

[Christian Huebner (ossarchitect)]

This is highly customer visible. After a few redeployments like in RedHat's case there are going to be hundreds of entries in the RHN host list. While this is not stopping operations, I think it should be classified a bug and fixed as soon as possible.

[Matthew Mosesohn (raytrac3r)]

We can also unregister for RHN Satellite with the following:
1 - copy delete-old-systems-interactive from spacewalk-utils (we can't use the RPM because its dependencies include Oracle client and SpaceWalk itself)
2 - install perl-Frontier-RPC-Client rpm
3 - run perl delete-old-systems-interactive --idle=1m --host=rhel-satellite.vm.mirantis.net --username=$USER --password=$PASSWORD --force
This would require setting a user and password for the account on the satellite server that has admin role for all systems in the default organization for this user.

[Ivan Kolodyazhny (e0ne)]

Is it actual for 5.0?

[Christian Huebner (ossarchitect)]

I have not been able to test 5.0 yet.

Christian

On 4/3/14, 5:50 AM, Ivan Kolodyazhny wrote:
> Is it actual for 5.0?
>