2CRSI BIOS update not available

stormi

Hi!

It's not packaged yet in XCP-ng 8.3, but you can get it from https://github.com/xcp-ng/xcp-ng-xapi-plugins/blob/gtn_add_ipmitool_plugin/SOURCES/etc/xapi.d/plugins/ipmitool.py and copy the file as /etc/xapi.d/plugins/ipmitool.py.

Dezerd

Hi,

I have just copy the ipmitool on my two hosts but no changes.
Is there nothing else to do?

I have reboot the host and XOA.

Thanks.

stormi

@Dezerd What does sha256sum /etc/xapi.d/plugins/ipmitool.py report?

Dezerd

Hop : f12475ad40702dd8ae2817d4446c360d380edda4d846a1bfee3ec88853e7060c /etc/xapi.d/plugins/ipmitool.py

stormi

The checksum is valid. Pinging @gthvn1 who worked on this plugin.

gthvn1

I don't know exactly how it is used in XOA but it looks like it has been merged last week in XO(see https://github.com/vatesfr/xen-orchestra/pull/8144) and I know that Cecile tested it on her setup. So maybe there is a mismatch with the version of XOA you are using?
Otherwise from the point of view of xcp-ng you just need to copy the python file in /etc/xapi.d/plugins/ and there is nothing else to do.

MathieuRA opened this pull request in vatesfr/xen-orchestra

closed feat(xo-server,xo-web/host): replace 2crsi-plugin.py -> ipmitool.py #8144

olivierlambert

@MathieuRA can you check if we are maybe too strict with the model? Or if we are missing something in that case.

Dezerd

@gthvn1 I just have the latest version of XOA (latest branch).

MathieuRA

Hi.
The IPMI plugin is only used to display hardware information if you are using mona_1.44gg.

To display if a BIOS update is available, we mainly fetch this endpoint: https://pictures.2cr.si/Images_site_web_Odoo/Pages_produit/VATES-BIOS_BMC_last-version.json

Does your host have access to this endpoint?
What is the ouput of xo-cli host.getBiosInfo id=<host-id>

Dezerd

Hi,

The output is "True".
My two hosts have acces to the json script.

Sans titre.png

My servers are not 1.44gg but 1.4SR which is clearly visible in the script output (by the way, there's an error -> there is an extra "_" at the end of the last URL)

Is it possible to modify the script to work with the 1.4SR model?

Thank's

MathieuRA

Good catch for the extra underscore, it will be fixed, BTW xo-cli should not return true. In your host's Advanced tab, what is shown in Manufacturer Information and BIOS Information?

Dezerd

@MathieuRA
Here is the information :
Sans titre.png

MathieuRA

Well, the problem is here then.
The XAPI reports NULL (NULL) so XO can't compare your bios version and display if it is up to date or not.

@olivierlambert Do you know why there is no value here?

Dezerd

@MathieuRA I think, i found a problem.
I have just check the Bios version during the boot of my host.
The Product Name is also NULL

It seems to be a factory configuration problem (2CRSI)

What type of information do I need to find in the product name (or Manufacturer Info on XOA) ? Just Server model?

olivierlambert

I think they provided a fix in a recent BIOS, but it's a catch-22 since they sold you the server with the BIOS version before the fix, so you can't have the info displayed in XO to tell you to update the BIOS

Dezerd

Ahah ok, it's fun!
I need to find the procedure for the update and I'll let you know.

Thanks!

Dezerd

Hey,

We have update the Bios to the latest version.
alt text

There is a new problem.. We cannot boot now.
The boot device 'XCP-NG' is missing
alt text

There doesn't seem to be any problem detecting disks in the BIOS (or clusters).

alt text

Do you know this problem ?
2CRSI support seems to say that the only solution is a reinstallation

Thanks and happy New Year

olivierlambert

I'm not aware of this problem, have you changed the mode (BIOS vs UEFI) after BIOS update? I think we already tested a BIOS update and it worked well. Let me ping @AtaxyaNetwork about this.

Dezerd

@olivierlambert No, i changed nothing.The boot Mode is UEFI (see first screenshot).
I will check if a downgrade (if it's possible) fix this issue.

Dezerd

@olivierlambert said in 2CRSI BIOS update not available:

I'm not aware of this problem, have you changed the mode (BIOS vs UEFI) after BIOS update? I think we already tested a BIOS update and it worked well. Let me ping @AtaxyaNetwork about this.

Hi,

Have you had any feedback on this issue?

Thanks