Red Hat Bugzilla – Bug 967608
engine: create storage domain is failing after 2 minutes although command completed successfully in vdsm after 2:04
Last modified: 2015-09-22 09:09 EDT
Description of problem:
problem: timeout in web-admin is not synced with vds for creatStorageDomain command (guess for sync command).
timeout is set to 120 seconds while in engine\vdsm its 180.
in my case, createStorageDomain is taking longer than 2 minutes (2:04) hence transaction is rolled back and operation fails in engine although it was successful in vdsm.
- engine and vdsm are not synced, domain is created but engine doesn't know about it
1) install engine + vdsm based on 3.3 version
2) add new host
3) run 'yum install gluster* -y'
4) reboot host
5) add new storage domain from type glusterfs
due to bz 967596, creation of SD took more then 2 minutes, so operation failed.
Created attachment 753648 [details]
Created attachment 753650 [details]
Storage side the only way to solve this is change all verbs to be async.
Wrt 180/120 - engine has a 180s timeout for all vdsm ops and this timeout has been heavily tested and it would be a very bad idea to change it.
The only relevant solution I see here is to change the webadmin timeout to 120.
(In reply to Ayal Baron from comment #3)
> Storage side the only way to solve this is change all verbs to be async.
> Wrt 180/120 - engine has a 180s timeout for all vdsm ops and this timeout
> has been heavily tested and it would be a very bad idea to change it.
> The only relevant solution I see here is to change the webadmin timeout to
I am not aware of any timeout - but assigning Alex to investigate.
I checked and I am not aware of any timeout either, I double checked with Vojtech and he didn't know of any timeout either. May I ask what you mean with webadmin timeout. I checked the configuration between the engine and VDSM and I found a couple of potential candidates but I am not 100% sure what they mean:
1. ServerRebootTimeout (???)
2. NetworkConnectivityCheckTimeoutInSeconds (Timeout to wait when making network changes?)
3. ExternalSchedulerResponseTimeout (Related to scheduler?)
Other than that I have no clue what you mean by webadmin timeout, could you please elaborate?