Red Hat Bugzilla – 1207077 – Can't add storage domain with error: CanDoAction of action 'AddStorageServerConnection' failed for user admin@internal. Reasons: VAR__ACTION__ADD,VAR__TYPE__STORAGE__CONNECTION,ACTION_TYPE_FAILED_OBJECT_LOCKED
Can't add storage domain with error: CanDoAction of action 'AddStorageServerConnection' failed for user admin@internal. Reasons: VAR__ACTION__ADD,VAR__TYPE__STORAGE__CONNECTION,ACTION_TYPE_FAILED_OBJECT_LOCKED
Created attachment 1008262[details]
engine log
Description of problem:
Can't add storage domain with error: CanDoAction of action 'AddStorageServerConnection' failed for user admin@internal. Reasons: VAR__ACTION__ADD,VAR__TYPE__STORAGE__CONNECTION,ACTION_TYPE_FAILED_OBJECT_LOCKED.
Looks very familiar to other bug i opened with such object_locked see BZ 1169879.
Storage domain adding is locked and so is the engine.
The engine is stacked for ever trying to add storage domain, when trying to add another one, i got error:
Operation canceled:
Error while executing action: Cannot add Storage Connection. Related operation is currently in progress. Please try again later.
Version-Release number of selected component (if applicable):
3.6.0-0.0.master.20150329172249.git660d494.el6
Steps to Reproduce:
1. To reproduce this issue, need first to get to situation like mine, the engine is stacked for ever trying to add first storage domain without any timeout for this,
- Is there a time-out for adding storage domain to engine if failing to add one?
- Restarting engine doesn't solving this.
- I pretty sure i got to this situation cause of this BZ 1205575,
- I guess the behavior in this issue is like in BZ 1169879 - fist command locks the engine or the storage domain adding, we have here multiple requests.
Buy the way, the first and original request for adding storage domain never been resolved, succeed or actually failed.
looks like you Host encountered some python error.
"error = local variable 'lines' referenced before assignment"
Can u please attach the Host logs and the RPM versions you are using
It looks like your VDSM Host had a problem.
If you can reproduce this bug with the latest build and verify that there is a problem which so we can resolve, it could be great.
Perhaps we can move this to ON_QA or close it until it will be reproduce and re-opened with the full relevant logs and reproduce steps.
I can't reproduce this issue, it's a specific scenario in which the engine trying to add host for ever without any time out(for some reason), from this stage you will try to add another host and will fail cause the object is locked in db.
This is an issue for sure, but i can't reproduce the point in which engine trying to add host for ever without any time out.
Closing this report until it will be reproducible and will re-open it again.