Bug 1120013

Summary:	ambigious error message when calling add-pkg
Product:	[Fedora] Fedora	Reporter:	Salim Badakhchani <sal>
Component:	koji	Assignee:	Dennis Gilmore <dennis>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	dennis, mikem, nobody
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-29 21:36:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Salim Badakhchani 2014-07-16 05:02:30 UTC

Description of problem:

When calling add-pkg and attempting to add a package to tag that does not exist an ambigious error message is created which can be hard for users to degub.  This is a common mistake as users evoke the command with typo and then submit a ticket asking what has gone wrong.

Version-Release number of selected component (if applicable):

koji-1.8.0-2.el6.noarch

How reproducible:

Always

Steps to Reproduce:
1. brew add-pkg jp-ip-6.1 org.infinispan.protostream-protostream-aggregator --owner ncross

Actual results:

TypeError: 'NoneType' object has no attribute '__getitem__'

Expected results:

Error: Tag does not exist

Additional info:

Might be an idea to do the same for tag-build call as well.

Comment 1 Fedora End Of Life 2015-05-29 12:23:05 UTC

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-06-29 21:36:41 UTC

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.