- **status**: unassigned --> fixed
- **assigned_to**: Rafael Odzakow
- **Comment**:
fixed in
commit 3e1d1091270fa83cb8efe5458d6050b56f41f001
Author: Rafael Odzakow
Date: Fri Jun 30 10:57:36 2017 +0200
smf: 20 seconds timeout in getting node destination is not enough [#2499]
---
** [t
This issue is as far as I could see a bug. In other campaign sequences SMF will
wait with rebootTimeout before doing any operation after reboot. In this
campaign sequence the first operation type after a reboot was to to a CLI
command on a payload node. This timed out because the CLI command is
Thank Rafael,
This is what I expected.
/Tai
---
** [tickets:#2499] SMF: 20 seconds timeout in getting node destination is not
enough**
**Status:** unassigned
**Milestone:** 5.17.08
**Created:** Fri Jun 16, 2017 08:04 AM UTC by Tai Dinh
**Last Updated:** Tue Jun 20, 2017 03:03 AM UTC
**Owner:
Hi Rafael,
It's under SmfCliCommandAction::execute() => getNodeDestination(n, &nodeDest,
NULL, -1).
-1 was passed as maxWaitTime which means 20 seconds timeout will be used.
For a rolling upgrade procedure, this should be OK sine we already wait for the
node but for cluster reboot procedure, the
waitForNodeDestination already uses smfRebootTimeout. Is it still timing out or
was getNodeDestination called without the waitFor wrapper?
---
** [tickets:#2499] SMF: 20 seconds timeout in getting node destination is not
enough**
**Status:** unassigned
**Milestone:** 5.17.08
**Created:** Fri
---
** [tickets:#2499] SMF: 20 seconds timeout in getting node destination is not
enough**
**Status:** unassigned
**Milestone:** 5.17.08
**Created:** Fri Jun 16, 2017 08:04 AM UTC by Tai Dinh
**Last Updated:** Fri Jun 16, 2017 08:04 AM UTC
**Owner:** nobody
We're now using a hard coded time
