Bug 1553840

Summary: 'boinccmd --get_tasks' doesn't tell if an unstarted workunit has been suspended
Product: [Fedora] Fedora Reporter: Adri Verhoef <bugzilla>
Component: boinc-clientAssignee: Laurence Field <Laurence.Field>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 27CC: bugzilla, germano.massullo, greatauk37, Laurence.Field, mmahut, xjakub
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1575785 1575786 (view as bug list) Environment:
Last Closed: 2018-03-10 01:05:31 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 Adri Verhoef 2018-03-09 17:03:33 UTC 
Description of problem:
(This is after upgrading from 7.8.4 to 7.9.2.)
After suspending an unstarted workunit you cannot tell which one you suspended via boinccmd.

Version-Release number of selected component (if applicable):
boinc-client-7.9.2-3.fc27.x86_64

How reproducible:
Select an unstarted workunit, suspend it, try using boinccmd to find out which one you suspended.

Steps to Reproduce:
1. Select a workunit to suspend via 'boinccmd --get_tasks',
   e.g. this name: OET1_0005398_x4O6HchD_rig_40103_0
2. Run: boinccmd --task http://www.worldcommunitygrid.org OET1_0005398_x4O6HchD_rig_40103_0 suspend
3. Run: boinccmd --get_tasks | grep suspended | uniq

Actual results:
After suspending an unstarted workunit, no workunits are found suspended according to 'boinccmd --get_tasks':
$ boinccmd --get_tasks | grep suspended | uniq
   suspended via GUI: no

Expected results:
At least one suspended workunit found in the output of 'boinccmd --get_tasks',
like it used to be in version boinc-client-7.8.4-4.fc27.x86_64.

Additional info:
You have to use the GUI to find out which unstarted workunits have been suspended.
Comment 1 Germano Massullo (Thetra) 2018-03-09 17:23:05 UTC 
Hi Adri, I think this problem should really be reported to upstream developers at https://github.com/BOINC/boinc/issues

Before doing that, could you please test the new 7.9.3 release?
https://bodhi.fedoraproject.org/updates/FEDORA-2018-e379ac6a55

$ bodhi updates download --updateid FEDORA-2018-e379ac6a55
# dnf update *

I suggest you to restart boinc-client service after the upgrade, even if it should not be necessary.

Have a nice day
Comment 2 Adri Verhoef 2018-03-09 19:02:03 UTC 
Hi Germano, thank you for replying, I've installed the 7.9.3 release
$ rpm -qa boinc-\*
boinc-manager-7.9.3-1.fc27.x86_64
boinc-client-7.9.3-1.fc27.x86_64

and the boinc-client service was restarted.  Then I suspended a workunit and checked if it was visible with 'boinccmd --get_tasks'.  The issue is still there, I'm afraid.

I landed here through the last URL in this command:
$ rpm -qi boinc-client | grep URL
URL         : http://boinc.berkeley.edu/
Bug URL     : https://bugz.fedoraproject.org/boinc-client
Comment 3 Germano Massullo (Thetra) 2018-03-10 01:05:10 UTC 
(In reply to Adri Verhoef from comment #2)
> I landed here through the last URL in this command:
> $ rpm -qi boinc-client | grep URL
> URL         : http://boinc.berkeley.edu/
> Bug URL     : https://bugz.fedoraproject.org/boinc-client

Yes but for this kind of bug you have to fill a bugreport on upstream website https://github.com/BOINC/boinc/issues