Bug 1309101

Summary:	copr-cli doesn't handle string input for 'status'
Product:	[Community] Copr	Reporter:	John M. Harris, Jr. <johnmh>
Component:	cli	Assignee:	clime
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	clime, johnmh
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-05 13:06:23 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:

Description John M. Harris, Jr. 2016-02-16 20:21:06 UTC

Description of problem:
I understand that 'status' is supposed to take a build id, but it's a simple misunderstanding for a user to think they could do something like `copr status mypackage` to see the status of their package, perhaps expecting something similar to the "monitor" tab on on the web frontend. Instead, you're presented with 

How reproducible:


Steps to Reproduce:
1. run `copr status any-string`

Actual results:
HTML error page

Expected results:
Something along the lines of "Something went wrong:\n Error: build id expected."

Comment 1 clime 2016-03-18 07:26:15 UTC

Fixed by 50cfd70c. Thank you.

Comment 2 Miroslav Suchý 2016-05-05 13:06:23 UTC

Package including this fix has been deployed on production instance of Copr.