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
Comments
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. |
We have added detailed job statuses after Dec 5 @fbalak can you reproduce this bug using latest builds? |
@r0h4n When I call API request with invalid data then job won't finish and status remains |
tendrl-bug-id: Tendrl/api#33 Signed-off-by: Shubhendu <shtripat@redhat.com>
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>
Sent Tendrl/commons#172 to fix the issue. |
With Tendrl/commons#172 merged, is it available in a build? @shtripat - can you add the package NVR which contains the fix? |
The build tendrl-commons-1.2.1-2.el7.centos.noarch.rpm contains the fix which was done 5 days back. |
I am closing this issue. We can revisit it if required. |
@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. |
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. |
@fbalak Please open this issue. |
@mkudlej I am not authorized to do that. |
This is fixed in v1.2.2 Please verify again |
It seems ok. Failed jobs have 'failed' status. --> closing |
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.
The text was updated successfully, but these errors were encountered: