How to increase fog timeout for OpenStack snapshots?


#1

HiHo,
I connect MIQ to an OpenStack environment and everything works fine so far.

OpenStack is using Ceph as a backend storage. Apparently creating a snapshot takes too much time, causing MIQ to cancel the action.

Is it possible to increase the default timeout from 5 minutes to something like 20 minutes? (That’s how long it currently takes OpenStack to create the snapshot).

Here are the relevant messages from the evm.log:
[----] I, [2015-08-17T15:48:36.779019 #37612:fc1ea8] INFO – : MIQ(MiqQueue.get_via_drb) Message id: [49000001671049], MiqWorker id: [49000000001775], Zone: [default], Role: [smartstate], Server: [], Ident: [generic], Target id: [], Insta
nce id: [49000000000023], Task id: [], Command: [Job.signal], Timeout: [600], Priority: [100], State: [dequeue], Deliver On: [], Data: [], Args: [:abort, “job timed out after 346.399386357 seconds of inactivity. Inactivity threshold [3000
seconds]”, “error”], Dequeued in: [5.638601999] seconds
[----] I, [2015-08-17T15:48:36.779148 #37612:fc1ea8] INFO – : MIQ(MiqQueue.deliver) Message id: [49000001671049], Delivering…
[----] I, [2015-08-17T15:48:36.791850 #37612:fc1ea8] INFO – : MIQ(Event.raise_evm_event): Event Raised [vm_scan_abort]
[----] I, [2015-08-17T15:48:36.860858 #37612:fc1ea8] INFO – : MIQ(Event.raise_evm_event): Alert for Event [vm_scan_abort]
[----] I, [2015-08-17T15:48:36.861076 #37612:fc1ea8] INFO – : MIQ(MiqAlert.evaluate_alerts) [vm_scan_abort] Target: VmOpenstack Name: [cfme167], Id: [49000000000374]
[----] E, [2015-08-17T15:48:36.867684 #37612:fc1ea8] ERROR – : action-abort: job aborting, job timed out after 346.399386357 seconds of inactivity. Inactivity threshold [3000 seconds]
[----] I, [2015-08-17T15:48:36.878189 #37612:fc1ea8] INFO – : action-finished: job finished, job timed out after 346.399386357 seconds of inactivity. Inactivity threshold [3000 seconds]

Thanks,
Christian


#2

@cjung this is smartstate(SSA) correct? This doesn’t look like Fog timeout, seems like it didn’t even start the job. Check it you have allowed ‘smartproxy’ in you configure/configuration/server in server control area. If your SSA is in pending state and then in timeout, it means it didn’t even started.

Otherwise all timeouts of workers can be set in advanced tab.