ipmi sel time set is setting 30 mins less than given time in OOB, and 30 mins more than given time in in-band method (ipmitool)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ipmitool (Ubuntu) |
Fix Released
|
Undecided
|
Mathieu Trudel-Lapierre | ||
Xenial |
Fix Released
|
Undecided
|
Mathieu Trudel-Lapierre |
Bug Description
[Impact]
Setting time via ipmi (inband or out of band) between systems that aren't on the same timezone where the timezone is stepped by the minute (as opposed to the typical stepping by hour in many timezones).
[Test Case]
See below: '---Steps to Reproduce---'.
[Regression potential]
Minimal, this adds comparing the minutes as well as hour for timezone differences. If timezone data was inconsistent or broken where the timezone should be stepped by the hour and actually includes a minute difference; it may be seen that the time value set as a result of the 'ipmitool sel time' commands would differ from the value passed to the command.
---
== Comment: #0 - Mukesh K. Ojha <email address hidden> - 2016-05-09 13:50:48 ==
---Problem Description---
ipmi sel time set is setting 30 mins less than given time in OOB, and 30 mins more than given time in in-band method (ipmitool)
---uname output---
Ubuntu 16.04
Machine Type = All Power System
---Debugger---
A debugger is not configured
---Steps to Reproduce---
Install a Open Power Firmware(OP810) on BMC machine and try to set sel time using ipmitool.
ipmi sel time set is setting 30 mins less than given time in Out-of-band(OOB), and 30 mins more than given time in in-band method.
Here there are two problems
1. sel time set function setting time incorrectly.
2. same ipmi command behaves differently in in-band and out-of-band.
[pridhiviraj@
03/02/2016 11:43:07
[pridhiviraj@
03/02/2016 11:13:07
[pridhiviraj@
[pridhiviraj@
03/02/2016 11:15:20
Here we can observe in OOB method sel time set is setting 30 minutes less than given time.
This is tried on a machine which is having custom firmware for SL GA2 testing.
Tried on another machine having OP810 firmware, same problem appears.
[pridhiviraj@
02/20/2014 23:51:35
[pridhiviraj@
02/20/2014 23:21:35
[pridhiviraj@
Try to set sel time using in-band method:
[root@ite037 ~]# ipmitool sel time get
03/02/2016 11:06:55
[root@ite037 ~]# ipmitool sel time set "03/02/2016 11:06:55"
03/02/2016 11:36:55
[root@ite037 ~]#
[root@ite037 ~]#
[root@ite037 ~]# ipmitool sel time get
03/02/2016 11:37:17
[root@ite037 ~]#
Contact Information = <email address hidden>
Userspace tool common name: ipmitool
The userspace tool has the following bit modes: both
Userspace package: ipmitool
Userspace tool obtained from project website: na
*Additional Instructions for <email address hidden>:
-Attach ltrace and strace of userspace application.
== Comment: #7 - Breno Henrique Leitao <email address hidden> - 2016-05-25 14:55:13 ==
Canonical,
The solution for this problem is a fix already accepted upstream on commit:
* c7169bc27ee4072
git://git.
tags: | added: architecture-ppc64le bugnameltc-141165 severity-high targetmilestone-inin16041 |
Changed in ubuntu: | |
assignee: | nobody → Taco Screen team (taco-screen-team) |
affects: | ubuntu → ipmitool (Ubuntu) |
Changed in ipmitool (Ubuntu Xenial): | |
status: | New → Triaged |
Changed in ipmitool (Ubuntu): | |
assignee: | Taco Screen team (taco-screen-team) → Mathieu Trudel-Lapierre (cyphermox) |
Changed in ipmitool (Ubuntu Xenial): | |
assignee: | nobody → Mathieu Trudel-Lapierre (cyphermox) |
Changed in ipmitool (Ubuntu): | |
status: | New → Triaged |
This is already fixed in yakkety.