"firmware-nic-intel-1.30.0-1.1/hpsetup -d" failed to create the discovery XML

[shanyin]

Tried to create the discovery XML file using firmware-nic-intel-1.30.0-1.1's hpsetup extracted but failed. The discover operation also fails with 1.29.0 and 1.28.0 versions but it works with version 1.27.30. What's the exact cause and how to make the dircover operation succeed for version 1.30.0?

------------

g9rms001-0-1-0:/u/ainet/fw_hpe-12.10.7/test-# rpm2cpio ../PKGS/firmware-nic-intel-1.30.0-1.1.x86_64.rpm | cpio -id
122356 blocks
g9rms001-0-1-0:/u/ainet/fw_hpe-12.10.7/test-# find . -name hpsetup |cut -c3-128
usr/lib/x86_64-linux-gnu/firmware-nic-intel-1.30.0-1.1/hpsetup
g9rms001-0-1-0:/u/ainet/fw_hpe-12.10.7/test-# usr/lib/x86_64-linux-gnu/firmware-nic-intel-1.30.0-1.1/hpsetup -d /u/ainet/fw_hpe-12.10.7/test/tmpi0.txt
Copyright (c) 2024 Hewlett Packard Enterprise Development LP
HPE Intel Online Firmware Upgrade Utility Linux x86_64 for HPE ProLiant Gen9 and Gen10 server series Only. - v1.30.0

Failed to create the discovery XML. Please see log file for more information
The 'discover' (oem_do_discovery_with_files) operation has failed

g9rms001-0-1-0:/var/cpq-# tail -25 CP059761.log

Installation started: [Thu May 9 16:51:09 2024]

Installing: CP059761.scexe
Version: 1.30.0

OS: Red Hat Enterprise Linux 8.3 (Ootpa)
Kernel Release: 4.18.0-240.22.1.el8_3.x86_64
Driver Info: ixgbe-5.1.0-k-rh8.2.0
Adapters: "HPE Ethernet 1Gb 4-port 331i Adapter"; "HP Ethernet 1Gb 4-port 331FLR Adapter"; "HP Ethernet 10Gb 2-port 560SFP+ Adapter\x00"; "HP Ethernet 1Gb 4-port 331T Adapter"; "HP Ethernet 10Gb 2-port 560SFP+ Adapter\x00";

Command: ./.setup -d /u/ainet/fw_hpe-12.10.7/test/tmpi0.txt

[INFO] Entry Point: oem_do_discovery_with_files
[ERROR] Failed to create the discovery XML. Please see log file for more information
[ERROR] The 'discover' (oem_do_discovery_with_files) operation has failed
[ERROR] 'discover' (oem_do_discovery_with_files) return code: 12

Return Value: FWUPG_FAIL_TO_CREATE_DISC_XML [12]

Installation complete: [Thu May 9 16:51:11 2024]
================================================================

g9rms001-0-1-0:/var/cpq-# tail -15 Component.log
Installation started: Thu May 9 16:51:09 CDT 2024

Installing: CP059761.scexe
Version: 1.30.0
Description: HPE Intel Online Firmware Upgrade Utility Linux x86_64 for HPE ProLiant Gen9 and Gen10 server series Only.

Return code: 7

Installation complete: Thu May 9 16:51:11 CDT 2024

=================================================================

[shanyin]

BTW, product_id value="HPE Ethernet 10Gb 2-port 560SFP+ Adapter". So it seems that firmware-nic-intel-1.28.0-1.1.x86_64.rpm and newer firmware packages do not support HPE Ethernet 10Gb 2-port 560SFP+ Adapter anymore as the release notes are saying.

[Mr_Techie]

@shanyin 

What product are you referring to? Any Network product? 

[shanyin]

Gen9 DL380

[Mr_Techie]

Thanks for confirming. It looks there's an issue specifically with version 1.30.0 of the firmware package. The error logs don't provide detailed information about why the creation of the discovery XML failed. However, since the issue only occurs with version 1.30.0 and not with version 1.27.30, it suggests that there might be a change or a bug introduced in version 1.30.0 causing this problem. Can you try roll back to the previous version and see of that fixes.

Let me know..

[TVVJ · Accepted solution]

Hello,

If in case, the "HPE Intel Online Firmware Upgrade Utility Linux x86_64 for HPE ProLiant Gen9 and Gen10 server series Only", was used for this purpose, then, the update would fail as the package does not contain the software for the "HPE Ethernet 10Gb 2-port 560SFP+ Adapter".

The section "Notes:" contains information to this effect. As found there, please use this "HPE Intel Online Firmware Upgrade Utility for Linux x86_64" for updating the firmware.

Please use the above and see if it helps.

Regards,

[shanyin]

Thanks. Yes I already appled version 1.27.30-1.1 and it works. 

[Sunitha_Mod]

Hello @shanyin,

That's Excellent!

We are extremely glad to know the problem has been resolved and we appreciate you for keeping us updated.