Warewulf v4 needs to be updated to 4.5.6 to resolve the issue with overlay updates. #2072
Comments
|
Thanks for the report and the work-around. We will definitely provide an update with the next OpenHPC release. |
Signed-off-by: Martin Tzvetanov Grigorov <[email protected]>
|
@adrianreber do you have any ETA for the 3.3 release? It seems that Warewulf has released a major update literally a couple of hours ago, and there have been noticeable changes in well a lot of things. Now the documentation feels noticeably different and most likely will not match openhpc manuals. I could probably submit a PR for that. |
|
I would say around May. That is our usual release month. There is already #2072 which updates warewulf and has not been merged. If you want to work on an update and also update the documentation you are more than welcome. Happy to take your contributions. |
|
I have a patch written and tested that is ready to go for the 4.6.x branch (I need to re-test against the actual release). Feel free to test and provide some input.
https://github.com/MiddelkoopT/ohpc/tree/tm-warewulf-4.6
|
|
Note, the SPEC file has also been updated but the version needs to be bumped to the final release. |
|
@MiddelkoopT that's quite handy, why did you link against rocky-9 and not 9.5? |
|
To use the latest version. The "9" points at the latest version (9.5). If you want to use a specific version, then you can use the fixed image tag (e.g. - ghcr.io/warewulf/warewulf-rockylinux:9.3) |
|
@MiddelkoopT I mean, OpenHPC usually sticks to fixed versions rather than to the latest one, at least that's my understanding. |
|
Ah good point. Perhaps I should change it to 9.5 - I'll bring it up at the next TSC meeting (Tomorrow) |
At the moment some nodes can't get overlay updates after boot due to
wwclientfailing. This is caused by poordmidecodeinfo parsing as reported in warewulf/warewulf#1310 and has been resolved upstream.A temporary workaround is to uninstall
dmidecodeand rebuild the image, but this approach is not sustainable in the long term.The text was updated successfully, but these errors were encountered: