@Andy_Wismer I also noticed this, the error was not displayed after the update but only after another login.
1 Like
And it’s ONLY displayed in Software Center.
If you look in Cluster-Status, everything looks fine, no errors reported.
@Andy_Wismer I can also confirm this.
1 Like
I have reclassified this as a Bug.
FWIW, even after logout/login, or even logging in with a different browser, I’m still not seeing this.
1 Like
Thanks for confirming, your NS8 is probably not having this issue, as some of mine I also updated last night.
Some do show this, some don’t.
All are top up-to date, at least according to NS8 themselves.
The underlying Debian are all top current!
I’m not quite sure, but I think the error was only shown the next day, I did do other stuff on some of the NS8s. And I did not see the error message, even though I was in Software Center after updating…
Another note: The message always appears in english, even though the rest of the Cluster-Admin shows in the language of the installed Browser.
→ I have yet to see a possible pattern…
My 2 cents
Andy
I don’t have this. I am on 3.2.4, from a migrated system, rocky, inside KVM (UNRAID).
1 Like
Thank you all for reporting this issue. The latest core update, version 3.2.4, introduces the following feature:
When a NS7 system joins the cluster via the migration tool, a banner is displayed in the Software Center: “Updates are suspended.”
Updates will resume once the migration is complete.
It seems likely that the systems now showing this banner had some interaction with a NS7 node at some point in their history—possibly even due to a failed migration attempt. For sure, systems with an ongoing real migration must display the banner and disable updates.
During the summer, we addressed several bugs related to the NS7 migration procedure. Failed migration attempts might have left residual data in Redis, which could now be triggering this banner.
Please check if the cluster displaying the banner has undergone at least one NS7 migration attempt. If so, run the following command and share its output:
redis-cli --raw keys 'node/*/flags' | xargs -t -r -l1 -- redis-cli smembers
The output should be empty or contain an even number of lines. For example:
redis-cli smembers node/77/flags
nomodules
The nomodules flag is set by NS7 only during migration. If this is confirmed, we can work on releasing a fix to handle systems with leftover Redis keys.
2 Likes
Here are the results of the 4 I observed with this issue.
The Name in brackets (XXXX) is an internal short form for the client, if more logs, etc are needed.
Client 01 (KGAN)
redis-cli --raw keys ‘node/*/flags’ | xargs -t -r -l1 – redis-cli smembers
redis-cli smembers node/3/flags
nomodules
Client 02 (SUMA) The only one using 2 nodes, third node not used yet.
redis-cli --raw keys ‘node/*/flags’ | xargs -t -r -l1 – redis-cli smembers
redis-cli smembers node/3/flags
nomodules
redis-cli smembers node/2/flags
nomodules
(empty array)
-bash: nomodules: Kommando nicht gefunden.
Client 03 (BDUB)
redis-cli --raw keys ‘node/*/flags’ | xargs -t -r -l1 – redis-cli smembers
redis-cli smembers node/3/flags
nomodules
Client 04 (WPD)
redis-cli --raw keys ‘node/*/flags’ | xargs -t -r -l1 – redis-cli smembers
redis-cli smembers node/3/flags
nomodules
All of these systems are migrated NS7 systems, strangely, the top one closed migration without a single error - on first attempt.
My 2 cents
Andy
2 Likes
My Output :
[root@mail ~]# redis-cli --raw keys ‘node/*/flags’ | xargs -t -r -l1 – redis-cli smembers
redis-cli smembers node/3/flags
nomodules
redis-cli smembers node/2/flags
nomodules
redis-cli smembers node/4/flags
nomodules
For your information: during the migration i did abort twice.
2 Likes
2 Likes
When the UI is updated, a Ctrl + Shift + R is recommended to load the new UI code on the browser, until we implement a popup warning, automatically reload the page, or something else /cc @andre8244.
1 Like
redis-cli --raw keys ‘node/*/flags’ | xargs -t -r -l1 – redis-cli smembers
redis-cli smembers node/7/flags
nomodules
redis-cli smembers node/11/flags
nomodules
redis-cli smembers node/12/flags
nomodules
redis-cli smembers node/3/flags
nomodules
redis-cli smembers node/8/flags
nomodules
redis-cli smembers node/14/flags
nomodules
redis-cli smembers node/5/flags
nomodules
redis-cli smembers node/9/flags
nomodules
redis-cli smembers node/4/flags
nomodules
redis-cli smembers node/6/flags
nomodules
redis-cli smembers node/13/flags
nomodules
redis-cli smembers node/10/flags
nomodules
redis-cli smembers node/2/flags
nomodules
I had a lot of problems getting a connection at first.
1 Like
~# redis-cli --raw keys 'node/*/flags' | xargs -t -r -l1 -- redis-cli smembers
redis-cli smembers node/2/flags
nomodules
2 Likes
Same problem here after the update to 3.2.4.
Nethserver 8 with Rocky Linux 9.5.
command output
redis-cli --raw keys 'node/*/flags' | xargs -t -r -l1 -- redis-cli smembers
redis-cli smembers node/11/flags
nomodules
redis-cli smembers node/40/flags
nomodules
redis-cli smembers node/7/flags
nomodules
redis-cli smembers node/27/flags
nomodules
redis-cli smembers node/71/flags
nomodules
redis-cli smembers node/96/flags
nomodules
redis-cli smembers node/93/flags
nomodules
redis-cli smembers node/100/flags
nomodules
redis-cli smembers node/83/flags
nomodules
redis-cli smembers node/23/flags
nomodules
redis-cli smembers node/26/flags
nomodules
redis-cli smembers node/106/flags
nomodules
redis-cli smembers node/78/flags
nomodules
redis-cli smembers node/43/flags
nomodules
redis-cli smembers node/36/flags
nomodules
redis-cli smembers node/118/flags
nomodules
redis-cli smembers node/112/flags
nomodules
redis-cli smembers node/8/flags
nomodules
redis-cli smembers node/45/flags
nomodules
redis-cli smembers node/88/flags
nomodules
redis-cli smembers node/109/flags
nomodules
redis-cli smembers node/66/flags
nomodules
redis-cli smembers node/37/flags
nomodules
redis-cli smembers node/47/flags
nomodules
redis-cli smembers node/79/flags
nomodules
redis-cli smembers node/48/flags
nomodules
redis-cli smembers node/102/flags
nomodules
redis-cli smembers node/24/flags
nomodules
redis-cli smembers node/44/flags
nomodules
redis-cli smembers node/113/flags
nomodules
redis-cli smembers node/58/flags
nomodules
redis-cli smembers node/68/flags
nomodules
redis-cli smembers node/32/flags
nomodules
redis-cli smembers node/91/flags
nomodules
redis-cli smembers node/21/flags
nomodules
redis-cli smembers node/110/flags
nomodules
redis-cli smembers node/22/flags
nomodules
redis-cli smembers node/18/flags
nomodules
redis-cli smembers node/90/flags
nomodules
redis-cli smembers node/39/flags
nomodules
redis-cli smembers node/15/flags
nomodules
redis-cli smembers node/75/flags
nomodules
redis-cli smembers node/103/flags
nomodules
redis-cli smembers node/57/flags
nomodules
redis-cli smembers node/3/flags
nomodules
redis-cli smembers node/114/flags
nomodules
redis-cli smembers node/2/flags
nomodules
redis-cli smembers node/73/flags
nomodules
redis-cli smembers node/6/flags
nomodules
redis-cli smembers node/46/flags
nomodules
redis-cli smembers node/89/flags
nomodules
redis-cli smembers node/67/flags
nomodules
redis-cli smembers node/55/flags
nomodules
redis-cli smembers node/94/flags
nomodules
redis-cli smembers node/59/flags
nomodules
redis-cli smembers node/33/flags
nomodules
redis-cli smembers node/10/flags
nomodules
redis-cli smembers node/9/flags
nomodules
redis-cli smembers node/49/flags
nomodules
redis-cli smembers node/87/flags
nomodules
redis-cli smembers node/74/flags
nomodules
redis-cli smembers node/105/flags
nomodules
redis-cli smembers node/35/flags
nomodules
redis-cli smembers node/34/flags
nomodules
redis-cli smembers node/25/flags
nomodules
redis-cli smembers node/95/flags
nomodules
redis-cli smembers node/62/flags
nomodules
redis-cli smembers node/56/flags
nomodules
redis-cli smembers node/5/flags
nomodules
redis-cli smembers node/77/flags
nomodules
redis-cli smembers node/107/flags
nomodules
redis-cli smembers node/13/flags
nomodules
redis-cli smembers node/17/flags
nomodules
redis-cli smembers node/42/flags
nomodules
redis-cli smembers node/84/flags
nomodules
redis-cli smembers node/69/flags
nomodules
redis-cli smembers node/82/flags
nomodules
redis-cli smembers node/16/flags
nomodules
redis-cli smembers node/72/flags
nomodules
redis-cli smembers node/29/flags
nomodules
redis-cli smembers node/51/flags
nomodules
redis-cli smembers node/80/flags
nomodules
redis-cli smembers node/38/flags
nomodules
redis-cli smembers node/98/flags
nomodules
redis-cli smembers node/86/flags
nomodules
redis-cli smembers node/50/flags
nomodules
redis-cli smembers node/64/flags
nomodules
redis-cli smembers node/116/flags
nomodules
redis-cli smembers node/117/flags
nomodules
redis-cli smembers node/115/flags
nomodules
redis-cli smembers node/52/flags
nomodules
redis-cli smembers node/14/flags
nomodules
redis-cli smembers node/81/flags
nomodules
redis-cli smembers node/70/flags
nomodules
redis-cli smembers node/41/flags
nomodules
redis-cli smembers node/97/flags
nomodules
redis-cli smembers node/53/flags
nomodules
redis-cli smembers node/28/flags
nomodules
redis-cli smembers node/54/flags
nomodules
redis-cli smembers node/99/flags
nomodules
redis-cli smembers node/60/flags
nomodules
redis-cli smembers node/4/flags
nomodules
redis-cli smembers node/104/flags
nomodules
redis-cli smembers node/63/flags
nomodules
redis-cli smembers node/20/flags
nomodules
redis-cli smembers node/19/flags
nomodules
redis-cli smembers node/92/flags
nomodules
redis-cli smembers node/101/flags
nomodules
redis-cli smembers node/76/flags
nomodules
redis-cli smembers node/108/flags
nomodules
redis-cli smembers node/12/flags
nomodules
redis-cli smembers node/111/flags
nomodules
redis-cli smembers node/31/flags
nomodules
I had a lot of problems during migration…
1 Like
We are currently working on a fix, but it will likely benefit only those who have not yet updated to version 3.2.4. For clusters migrated from NS7, we recommend waiting for the core version 3.2.5 before proceeding with the update.
For those who have already encountered the issue, a manual procedure will be provided to apply the update and restore normal functionality.
This is the bug reference Updates suspended after failed NS7 migration attempt · Issue #7192 · NethServer/dev · GitHub
2 Likes
Thank you very much for the information. Is there any information here when the manual procedure is finished and how it is carried out?
The fix worked well. Thank you.