ipmipower ignores timeout settings during RMCP handshake
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
freeipmi (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
freeipmi: 1.4.11
Ubuntu Bionic
MAAS 2.5.2
Using ipmipower with opensesspriv work-around enabled to power up/down my servers.
However, due to my network connectivity, some packages may face longer latency on delivery.
I can see on tcpdump that messaging follows:
1) ipmipower --> RMCP+ OpenSession Request --> BMC
2) ipmipower --> RMCP+ OpenSession Request --> BMC (retransmission)
3) BMC --> RMCP+ OpenSession Response --> ipmipower
4) ipmipower --> RMCP+ RAKP Message 1 --> BMC
5) ipmipower --> RMCP+ RAKP Message 1 --> BMC (retransmission)
6) BMC --> RMCP+ RAKP Message 2 --> ipmipower
7) ipmipower replies ICMP Port Unreachable to BMC
I've set all available timeouts, as described on ipmipower manual, to bigger than 5 seconds, still, retransmissions were taking place before 1st second was over (as per tcpdump timestamps).
Also tried to set timeouts via /etc/freeipmi, with similar results.
I've pulled 1.6.3 from [1] and compiled on a brand new VM (to make sure only my commands were using ipmipower) and I've got the same result.
[1] https:/
Thank you for taking the time to report this bug and helping to make Ubuntu better.
This sounds like an upstream bug then, rather than anything specific to do with Ubuntu's packaging of freeipmi? If so, we can track the status of the bug appearing in Ubuntu packages here, but to make any progress an upstream bug report will be needed. If you take action on that, please link the report here to help keep everyone informed.
Importance: Low since "Bugs that affect unusual end-user configurations or uncommon hardware" from https:/ /wiki.ubuntu. com/Bugs/ Importance