There needs to be some sort of force option to remove it from the Pulp server even if the release command fails on the CDS. It's not ideal in that case, but we need to be able to remove CDS instances that are not running.
Going to address this as a more general story in Sprint 24.
commit 20d28c3aa382e40ba8a9feb5e196ab881859e23e Author: Jay Dobies <jason.dobies> Date: Thu Jun 9 14:52:43 2011 -0400 697206 - Added force option to CDS unregister to be able to remove it even if the CDS is offline. src/pulp/client/api/cds.py src/pulp/client/core/cds.py src/pulp/client/server.py src/pulp/server/api/cds.py src/pulp/server/webservices/controllers/cds.py
Included in 0.189.
verified [root@preethi upload]# rpm -q pulp pulp-0.0.213-1.fc14.noarch [root@preethi upload]# [root@preethi upload]# pulp-admin cds list +------------------------------------------+ CDS Instances +------------------------------------------+ Name pulp-cds.usersys.redhat.com Hostname pulp-cds.usersys.redhat.com Description None Cluster None Sync Schedule None Repos f14 Last Sync 2011-07-27 13:45:06-04:00 Status: Responding No Last Heartbeat 2011-07-27 20:03:17.586553+00:00 [root@preethi upload]# pulp-admin cds unregister Usage: pulp-admin <options> cds unregister <options> pulp-admin: error: Option --hostname is required; please see --help [root@preethi upload]# pulp-admin cds unregister --hostname=pulp-cds.usersys.redhat.com error: operation failed: PulpException: u'Timeout occurred attempting to release CDS [pulp-cds.usersys.redhat.com]' [root@preethi upload]# [root@preethi upload]# [root@preethi upload]# pulp-admin cds unregister --hostname=pulp-cds.usersys.redhat.com --force Successfully unregistered CDS [pulp-cds.usersys.redhat.com] [root@preethi upload]# pulp-admin cds list +------------------------------------------+ CDS Instances +------------------------------------------+ [root@preethi upload]#
Closing with Community Release 15 pulp-0.0.223-4.