Bug 1376703 - Cannot cancel build and now explain
Summary: Cannot cancel build and now explain
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Copr
Classification: Community
Component: cli
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: clime
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-16 08:12 UTC by Honza Horak
Modified: 2017-01-11 13:05 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-11 13:05:26 UTC


Attachments (Terms of Use)

Description Honza Horak 2016-09-16 08:12:16 UTC
Description of problem:
Based on the build.log I decided the build is stalled. I want to cancel it, so I run:
$> copr cancel 453584 

And get:

Something went wrong:
Error: Cannot cancel build 453584

I don't have a clue why the build cannot be canceled, so I'd expect explanation.

The copr seems to be running still:
$> copr status 453584
running

Version-Release number of selected component (if applicable):
copr-cli-1.53-1.fc24.noarch

How reproducible:
every-time

Steps to Reproduce:
1. $> copr cancel 453584 

Actual results:
Something went wrong:
Error: Cannot cancel build 453584

Expected results:
Canceling works and if it does not, a better error message is given.

Comment 1 clime 2016-09-16 09:07:29 UTC
There is a chroot in 'running' state in your build 453584. It's not (currently) possible to cancel builds in progress.

Comment 2 clime 2016-09-22 08:52:22 UTC
Fixed by https://github.com/fedora-copr/copr/commit/c6426b69.

Comment 3 John Ellson 2016-10-13 19:04:18 UTC
My build is also hung in a running state...

https://copr.fedorainfracloud.org/coprs/johnellson/graphviz/build/464766/

Cancelling also fails:


$ copr cancel 464766

Something went wrong:
Error: Cannot cancel build 464766


The same build works fine on other distros,  and works fine on a local Rawhide machine.


Note You need to log in before you can comment on or make changes to this bug.