Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Status of jobs in etcd doesn't reflect true state of job #33

Closed
fbalak opened this issue Dec 5, 2016 · 13 comments
Closed

Status of jobs in etcd doesn't reflect true state of job #33

fbalak opened this issue Dec 5, 2016 · 13 comments
Assignees
Labels

Comments

@fbalak
Copy link
Contributor

fbalak commented Dec 5, 2016

When calling GET /1.0/:cluster_id:/GlusterCreateVolume it returns job_id. When checking job_id through etcd api /v2/keys/queue/:job_id: there is written "status": "finished", but no gluster volume is created. There should be some error state when job fails.

@sankarshanmukhopadhyay
Copy link
Contributor

Have we addressed this topic in any of the recent builds? This may not be a test blocker but the failure condition needs to be handled.

@r0h4n
Copy link
Contributor

r0h4n commented Feb 23, 2017

We have added detailed job statuses after Dec 5

@fbalak can you reproduce this bug using latest builds?

@fbalak
Copy link
Contributor Author

fbalak commented Feb 24, 2017

@r0h4n When I call API request with invalid data then job won't finish and status remains new or processing. For example calling CreateVolume without specified Volume.bricks keeps job in processing status but it should be failed.
Tested with tendrl-api-1.2-02_24_2017_01_51_03.noarch.

shtripat pushed a commit to shtripat/bridge_common that referenced this issue Feb 26, 2017
tendrl-bug-id: Tendrl/api#33

Signed-off-by: Shubhendu <shtripat@redhat.com>
shtripat pushed a commit to shtripat/bridge_common that referenced this issue Feb 26, 2017
Also added check if mandatory arguments are passed for a
flow while execution.

tendrl-bug-id: Tendrl/api#33

Signed-off-by: Shubhendu <shtripat@redhat.com>
@shtripat
Copy link
Member

Sent Tendrl/commons#172 to fix the issue.
This PR marks the job failed is some atom fails execution. Additionally if mandatory parameters are not passed the job is marked as failed.

@sankarshanmukhopadhyay
Copy link
Contributor

With Tendrl/commons#172 merged, is it available in a build? @shtripat - can you add the package NVR which contains the fix?

@shtripat
Copy link
Member

shtripat commented Mar 6, 2017

The build tendrl-commons-1.2.1-2.el7.centos.noarch.rpm contains the fix which was done 5 days back.

@sankarshanmukhopadhyay
Copy link
Contributor

I am closing this issue. We can revisit it if required.

@mbukatov
Copy link
Contributor

mbukatov commented Mar 23, 2017

@fbalak Do you agree that this has been fixed? We would need to verify this on a cluster (when we have working builds again) and state the result here.

Based on description here so far, I don't think that enough evidence for closing this issue has been presented.

@mkudlej
Copy link

mkudlej commented Mar 23, 2017

I'm reopening this issue because we cannot be sure that it works. We cannot import cluster( #94 ) or create it so we cannot verify this.

@mkudlej
Copy link

mkudlej commented Mar 31, 2017

@fbalak Please open this issue.

@fbalak
Copy link
Contributor Author

fbalak commented Mar 31, 2017

@mkudlej I am not authorized to do that.
CC: @sankarshanmukhopadhyay

@r0h4n
Copy link
Contributor

r0h4n commented Apr 1, 2017

This is fixed in v1.2.2

Please verify again

@fbalak
Copy link
Contributor Author

fbalak commented Apr 3, 2017

It seems ok. Failed jobs have 'failed' status. --> closing
Tested with:
tendrl-api-1.2.1-04_03_2017_01_51_03.noarch
tendrl-performance-monitoring-1.2.1-04_03_2017_13_14_13.noarch
tendrl-commons-1.2.1-04_01_2017_00_59_17.noarch

@fbalak fbalak closed this as completed Apr 3, 2017
fbalak added a commit to fbalak/usmqe-tests that referenced this issue May 15, 2017
fbalak added a commit to fbalak/usmqe-tests that referenced this issue Jun 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants