non-utf8 char in Lan_Conf_Security_Keys from BMC

[Ike Panhc]

[Bug Description]
Non UTF-8 char in `ipmi-config --checkout` output after BMC power cycle.

[Steps to Reproduce]
1) BMC power cycle
2) sudo apt install freeipmi-tools
3) sudo /usr/sbin/ipmi-config --checkout --lan-channel-number 1 | grep -a -A5 '^Section Lan_Conf_Security_Keys'

[Actual Results]
Section Lan_Conf_Security_Keys
 ## Give string or blank to clear. Max 20 chars
 K_R Ӷ:΁,ء�Z��*�N��
 ## Give string or blank to clear. Max 20 bytes, prefix with 0x to enter hex
 K_G 0x0000000000000000000000000000000000000000
EndSection

[Expected Results]
All chars are in utf8

[Reproducibility]
It can be clear with ipmi-config, but coming back after BMC power cycle

[Additional information]
Platforms impacted: d06-3

[Resolution]

[dann frazier (dannf)]

hey @Tai - can you clarify what ipmi-config tool is used to clear it? Is the command designed to clear it, or does it happen as a side-effect?

[Ike Panhc (ikepanhc)]

@dannf,

Those non-utf8 chars are from BMC and automatically restored after BMC power cycle.

The command to clear it is

1) Create a txt file as
$ cat test.txt
Section Lan_Conf_Security_Keys
 ## Give string or blank to clear. Max 20 chars
 K_R
 ## Give string or blank to clear. Max 20 bytes, prefix with 0x to enter hex
 K_G 0x0000000000000000000000000000000000000000
EndSection

2) use `ipmi-config` and update into BMC
$ sudo ipmi-config --commit --lan-channel-number 1 --filename=test.txt

[Taihsiang Ho (tai271828)]

More tips about workaround:

If your system is unable to access for any reason, for example, fails to deploy or commission by MaaS, you may invoke the command similar to the `ipmi-config` in comment#2 to apply the workaround remotely by:

$ ipmi-config --commit --lan-channel-number 1 --filename=test.txt -u <BMC username> -p <BMC password> -h <BMC IP> -D LAN_2_0

[Andrew Cloke (andrew-cloke)]

HiSilicon have no current plans to address this issue. Closing out with "won't fix".

[Taihsiang Ho (tai271828)]

additional info: d05-4 also has this issue https://bugs.launchpad.net/scalebot/+bug/1947771/comments/24