unmapVmfsVolumeEx_Task timeout after 30 minutes

[David788]

Hello,

I'm struggling with running UNMAP from vRO against VMFS LUNs, while in case of bigger LUNs, which task takes longer that 30 minutes, which is somehow default timeout value.
Once after 30 minutes vCenter task triggered by but action time out, I do not have any information if and when UNMAP process ended.

Is there a way how to modify timeout of triggered VC:Task ?

I've already tried following:

TASK = unmapHost.configManager.storageSystem.unmapVmfsVolumeEx_Task(dsUuid);

TASK.createEndOfTaskTrigger(3600);

But it seems VC:Task modification does not returning any error, but also having no effect in terms of when task in vCenter will timeout.
For example, if I will try: TASK.createEndOfTaskTrigger(15);
I would expect, that vCenter task will timeout in 15 seconds, but it is not the case.

Regards

[iiliev]

Hi,

For configuring the task timeout at vCenter side, check the following KB article - https://kb.vmware.com/s/article/1017253

[David788]

Hi Illian,

many thanks for your answer, I'm aware of posibility to modify default timeout on vCenter side.

Anyway I consider this as really last possible option, as this change will then influence every single task, which could lead in case of unvanted scenario of whatever troubles to very long time of waiting for any task to "timeout".

As I would go for this single task even for 24 hours, then every single timeout will take 24 hours.

I'm rather looking for way how to modify this single task.

Like for example Enter Maintenance mode function is even explicitly expecting number <=0 for infinite timeout, any other number >1 is actuall timeout for this single "Enter maintenance mode" task.

Regards

[iiliev]

I see your point.

But I'm not sure this configuration of timeout-per-task is exposed in vCenter API. Could you post your question also in vCenter forum? If they provide a way to do this via vCenter API, then it should be possible to figure out how to do the same in vRO scripting.