elemental-operator
elemental-operator copied to clipboard
Failure during registration of SL-micro 6.0 baremetal iso
Running the stable operator and trying to register an sl-micro 6.0 baremetal iso from a seedimage fails the registration with the following error in the operator:
I0521 07:03:55.330991 1 log.go:42] Operator version 1.4.3, commit 11599b74, commit date 20240315
...
I0521 07:13:27.384820 1 log.go:42] Adding labels from system data
E0521 07:13:27.384979 1 log.go:70] Error during serve-loop: %!w(*fmt.wrapError=&{failed to extract labels from system data: unknown drive type: "virtual" 0xc000decf30})
E0521 07:13:27.385035 1 log.go:70] registration: failed to extract labels from system data: unknown drive type: "virtual"
Seems to be caused by a version mismatch in jaypipes/ghw, we are using v0.9.0 in stable and virtual drive seems to be added in v0.10.0 (we are using v0.12.0 in current main branch).
SLE Micro v2.0.4 includes elemental-register v1.5.1 SLE Micro v2.0.4 is included in the ManagedOSChannel v1.4.3 shipped with the Elemental Operator chart v1.4.3. This issue is present on the current released version of the stable Elemental Operator, so registration is broken if the SeedImage is built with SLE Micro v2.0.4.
Note that SLE Micro v2.0.2 (present in the channe v1.4.3 too) has the synced elemental-register v1.4.3 version and works perfectly.
Error from the client side:
Error: registering machine: failed to send system data: websocket: close 1006 (abnormal closure): unexpected EOF
IMHO with #741 backported for v1.5 and v1.6 we should focus now on a fix/improvement on server side before closing this issue. Would be nice that our first release of v1.6 includes a proper fix for that matter, just added a milestone for that.
all done