Project

Profile

Help

Issue #617

closed

pulp-consumer rpm repo unbind non-existent repo fails with unexpected error

Added by ipanova@redhat.com about 9 years ago. Updated about 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.5
Platform Release:
2.6.1
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Description of problem:

  1. pulp-consumer -u admin -p admin rpm unbind --repo-id invalid-repo
    An unexpected error has occurred. More information can be found in the client
    log file ~/.pulp/consumer.log.
  1. tail -15 ~/.pulp/consumer.log
    return self.method(*arg_list, **clean_kwargs)
    File "/usr/lib/python2.7/site-packages/pulp_rpm/extensions/consumer/pulp_cli.py", line 101, in unbind
    bind_id = e.extra_data['resources']['bind_id']
    KeyError: 'bind_id'
    2014-11-14 14:20:30,304 - ERROR - Client-side exception occurred
    Traceback (most recent call last):
    File "/usr/lib/python2.7/site-packages/pulp/client/extensions/core.py", line 478, in run
    exit_code = Cli.run(self, args)
    File "/usr/lib/python2.7/site-packages/okaara/cli.py", line 974, in run
    exit_code = command_or_section.execute(self.prompt, remaining_args)
    File "/usr/lib/python2.7/site-packages/pulp/client/extensions/extensions.py", line 224, in execute
    return self.method(*arg_list, **clean_kwargs)
    File "/usr/lib/python2.7/site-packages/pulp_rpm/extensions/consumer/pulp_cli.py", line 101, in unbind
    bind_id = e.extra_data['resources']['bind_id']
    KeyError: 'bind_id'

Meanwhile:

  1. pulp-consumer -u admin -p admin puppet unbind --repo-id invalid-repo
    The following resource(s) could not be found:
    invalid-repo (repo_id)
    puppet_distributor (distributor_id)

Version-Release number of selected component (if applicable):
2.5.0-0.18.rc

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:

Expected results:

Additional info:

+ This bug was cloned from Bugzilla Bug #1164276 +

Also available in: Atom PDF