search

ClusterLabs / anvil

The Anvil! Intelligent Availability™ Platform, mark 3
5 stars 6 forks source link

"Prepare host" button will not function without valid "Alteeve Enterprise Key" - `striker-ui` #670

Closed maholloway closed 3 weeks ago

maholloway commented 1 month ago

Hello,

This issue pertains to the following package versions: anvil-core version 2.92-1.2.9cfa anvil-node version 2.92-1.2.9cfa anvil-striker version 2.92-1.2.9cfa

I have followed the, "Build an M3 Anvil! Cluster" guide on the wiki here.

All steps in the guide work as expected until the Initializing Subnodes step.

I have two subnodes, 192.168.1.175 and 192.168.1.176 on the ifn. They both have anvil-node installed successfully as per the guide's previous steps.

Testing access works. The "Host name" field populates as expected, with a property formatted FQDN.

The next step is unavailable, due to a non-functional "Prepare host" button. Screenshot:

2024-06-02-07-19-31-190

@digimer suggests @ylei-tsubame will know what might be the matter here. If folks need any more info or have further questions for me please let me know and I'll help however I can.

maholloway commented 1 month ago

This thread on the hardware vendor's user support forum may or may not be related.

To test, I've successfully flashed the latest version of the ODROID H3+ main and net board BIOSes using this doc.

Via testing with this new BIOS version on one of my two boards I can confirm dmidecode --string system-uuid output has changed from 03000200-0400-0500-0006-000700080009 to 1e000000-4506-7407-0101-001e06450775

This will likely resolve some "flapping" I observed in the database and in striker-ui-api logs, meaning only one node would display at a time (because of the db index in postgres?) and the hostname would alternate between mh-a01n01.libre.audio and mh-a01n02.libre.audio.

I'll try initializing the subnode running on the board with the updated BIOS shortly.

maholloway commented 1 month ago

The issue persists after reinstalling anvil-node on the subnode board with the updated bios.

All 3 anvil systems now have unique uuids (both subnodes would have had the same one prior to the bios update on subnode 1) 2024-06-02-19-51-24-020

The apparent striker-ui issue still persists as depicted below: 2024-06-02-19-50-31-574

ylei-tsubame commented 4 weeks ago

The problem is the host UUID. It's not considered as a valid UUIDv4 by spec. I can reduce the restrictions on the UUID test to allow these.

ylei-tsubame commented 4 weeks ago

Patch made; should be merged when CI unblocks.

maholloway commented 3 weeks ago

Fantastic thanks Yan! I'll test it out once the change is integrated as you mentioned.

Mike

On June 7, 2024 8:17:10 PM EDT, Yanhao Lei @.***> wrote:

Patch made; should be merged when CI unblocks.

-- Reply to this email directly or view it on GitHub: https://github.com/ClusterLabs/anvil/issues/670#issuecomment-2155717485 You are receiving this because you authored the thread.

Message ID: @.***>