Opened 5 years ago

Closed 3 years ago

#59524 closed defect (fixed)

ipmitool 1.8.18.20190905: ipmitool sel time set: "Specified time could not be parsed"

Reported by: pioto (Mike Kelly) Owned by: drkp (Dan Ports)
Priority: Low Milestone:
Component: ports Version: 2.6.2
Keywords: Cc:
Port: ipmitool

Description

I have an existing script which I occasionally use to set IPMI SEL times.

The script hasn't changed, but it seems a more recent build of ipmitool can't parse the timestamps I provide anymore.

I'm invoking it like this: 

ipmitool -I lanplus -H example.ipmi.example.com -U admin -P topsecret sel time set "10/30/2019 09:45:17"

And that just yields: 

Specified time could not be parsed

I'm not sure if there are any patches you're applying, or some macOS platform oddities, which could be causing this, or if I just need to submit this upstream, but I'm starting downstream first.

Change History (4)

comment:1 Changed 5 years ago by jmroot (Joshua Root)

Cc: drkp removed
Owner: set to drkp
Status: new → assigned

No patches in the port, and nothing that would affect this that I can see. There have been fairly major relevant changes upstream however: ​https://github.com/ipmitool/ipmitool/commit/f0d5c17ea7b2b5b815f24b101d35ddda1a88d8a4#diff-b2d309077852911f3595ed8fb8714088R2746

That would make strptime look for a "national representation of the date" and "national representation of the time", which I suspect means that what it recognises is affected by your locale settings.

comment:2 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)

Please try upgrading to ipmitool 1.8.18.20200616. Let us know if that fixes it. If not, please report the problem to the developers and let us know the URL of that bug report.

comment:3 Changed 4 years ago by pioto (Mike Kelly)

Thanks, the latest revision seems to work with my scripts.

comment:4 Changed 3 years ago by jmroot (Joshua Root)

Resolution: → fixed
Status: assigned → closed
Note: See TracTickets for help on using tickets.