Closed razo7 closed 1 year ago
Can one of the admins check and authorise this run please: https://ci.kronosnet.org/job/fence-agents/job/fence-agents-pipeline/job/PR-554/1/input
Can one of the admins check and authorise this run please: https://ci.kronosnet.org/job/fence-agents/job/fence-agents-pipeline/job/PR-554/2/input
Can one of the admins check and authorise this run please: https://ci.kronosnet.org/job/fence-agents/job/fence-agents-pipeline/job/PR-554/3/input
We want to keep those. They could be used by external agents, and also we dont want to change the return code numbers as pcs and other utilities map their values to know what has happened.
The EC_OK/result parts look good though. Makes the code easier to read IMO.
I understand. What about the Add error message for EC_GENERIC_ERROR
commit? Should it stay with EC_OK/result commit?
Yeah. That looks good to me. I dont think it was intended for that, but shouldnt hurt.
Can one of the admins check and authorise this run please: https://ci.kronosnet.org/job/fence-agents/job/fence-agents-pipeline/job/PR-554/4/input
Can one of the admins check and authorise this run please: https://ci.kronosnet.org/job/fence-agents/job/fence-agents-pipeline/job/PR-554/5/input
Can one of the admins check and authorise this run please: https://ci.kronosnet.org/job/fence-agents/job/fence-agents-pipeline/job/PR-554/6/input
Thanks.
- Four error codes (EC_INVALID_PRIVILEGES, EC_STATUS_HMC, EC_FETCH_VM_UUID, and EC_BAD_ARGS) have not been used, thus they can be dismissed.