Comment 15 for bug 2017701

Performing verification for jammy

My user installed ipmitool 1.8.18-11ubuntu2 from jammy -release, and attempted
to set a persistent efiboot of their arm64 device:

$ apt policy ipmitool
ipmitool:
  Installed: 1.8.18-11ubuntu2
  Candidate: 1.8.18-11ubuntu2.1
  Version table:
     1.8.18-11ubuntu2.1 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy-proposed/universe arm64 Packages
 *** 1.8.18-11ubuntu2 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages
        100 /var/lib/dpkg/status
$ sudo ipmitool chassis bootdev pxe options=persistent,efiboot
Set Boot Device to pxe
$ sudo ipmitool raw 0x00 0x09 0x05 0x0 0x0
 01 05 a0 04 00 00 00 <--- "a0", but should be "e0"

The efiboot option was dropped incorrectly, showing "a0" in hexidecimal raw
view, versus the expected "e0" and efiboot being set.

My user then installed 1.8.18-11ubuntu2.1 from -proposed, and ran the same
command:

$ apt policy ipmitool
ipmitool:
  Installed: 1.8.18-11ubuntu2.1
  Candidate: 1.8.18-11ubuntu2.1
  Version table:
 *** 1.8.18-11ubuntu2.1 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy-proposed/universe arm64 Packages
        100 /var/lib/dpkg/status
     1.8.18-11ubuntu2 500
        500 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages
$ sudo ipmitool chassis bootdev pxe options=persistent,efiboot
Set Boot Device to pxe
$ sudo ipmitool raw 0x00 0x09 0x05 0x0 0x0
 01 05 e0 04 00 00 00 <--- is "e0" now

Efiboot is now set in a persistent fashion, and the raw values show "e0".

The package in -proposed fixes the issue, happy to mark verified for jammy.