When specifying an invalid consumer ID, the task seems to spin for a while. I assume it's waiting to time out since it can't find the consumer to contact. We should do a sanity check first to ensure the consumer actually exists before starting off a task that can't be cancelled. $ pulp-admin package install -n emoticons --consumerid foo Created task id: dc51ee4a-1ffb-11e0-97e0-5254003d10ee Task is scheduled for: 2011-01-14 11:32 ....................................................
Followup: 20 minutes later the CLI is still rendering periods and the process hasn't ended yet.
Added validate_consumer and validate_consumergroup functions to ConsumerActions and ConsumerGroupActions classes. $ sudo pulp-admin consumer list +------------------------------------------+ Consumer Information +------------------------------------------+ Id test-consumer Description None Subscribed Repos [] Additional info $ sudo pulp-admin package install -n origin --consumerid=test-consumer11 error: operation failed: Consumer [test-consumer11] does not exist
Fixed in 0.134.
verified [root@preethi ~]# pulp-admin package install -n zsh --consumerid=test-consumer11 error: operation failed: Consumer [test-consumer11] does not exist [root@preethi ~]# rpm -q pulp pulp-0.0.135-1.fc14.noarch
Closing with community release pulp-0.0.139-1.fc14.noarch