Notice "Updates are suspended" in Software Center

Bug
,
41

Hi @davidep

Is there any information here when the manual procedure is finished and how it is carried out?

Sorry, I misunderstood something and didn’t read it correctly. The fix also works perfectly for me. Thank you very much for your quick help.

Regards
Erwin

42

Some of you have tried the workaround for the bug, manually removing NS7 node(s) and their leftover Redis keys from the cluster. Since this operation carries some risk, the released fix now simply ignores those entries.

  • The bug fix is included in Core 3.2.5.
  • Redis keys created by older migration tool versions no longer trigger the Notice banner.
  • The Notice appears only if:
    • An NS7 reference is present in the Redis database, and
    • The NS7 node has been seen within the last 12 hours in the cluster VPN, or the leader node’s uptime is less than 12 hours.

If the Notice still appears shortly after a leader node reboot, it is a symptom of NS7 leftover keys. After 12 hours the updates are resumed.

For clusters with core version 3.2.4 and suspended updates a manual update to 3.2.5 is required. Run the following command on the leader node:

 api-cli run update-core --data '{"core_url":"ghcr.io/nethserver/core:3.2.5","nodes":['$(runagent -m node bash -c 'echo $NODE_ID')']}'
43

Nethserver8 core 3.2.4
…
we have the same Problem on debian12 - VM on Proxmox.
The migration had many problems, most with nextcloud. But after all it runs till core 3.2.4
We tried the workaround above - but NO success - what we should do ?

root@ns8:~# api-cli run update-core --data '{"core_url":"ghcr.io/nethserver/core:3.2.5
","nodes":['$(runagent -m node bash -c 'echo $NODE_ID')']}'
Warning: using user "cluster" credentials from the environment
_acontrol_task request attempt failed (Connection closed by server.). Retrying...
_acontrol_task request recovered successfully at attempt 2
_acontrol_task request attempt failed (Connection closed by server.). Retrying...
_acontrol_task request recovered successfully at attempt 2
<7>run-scriptdir /var/lib/nethserver/cluster/update-core-pre-modules.d/
Running /var/lib/nethserver/cluster/update-core-pre-modules.d/50update_grants...
<7>run-scriptdir /var/lib/nethserver/cluster/update-core-post-modules.d/
Running /var/lib/nethserver/cluster/update-core-post-modules.d/90disable_testing...
""
44

Did you try the removal procedure? Release notes — NS8 documentation
Scroll down to “Updates are suspended during NS7 migration” and follow the instructions.

3 Likes
45

Now we tried this - and we were able to install updates. We rebooted the VM …
But now it isn’t possible to login as admin to check the system !?!
If we try to login nextcloud or sogo, the answer is “Bad gateway”

46

Maybe the system has high load.
Before a container is fully started you always get the “Bad Gateway” error.
Please login via SSH and check the load using for example the uptime command.
You may also use top to check which process needs much resources.
Please also check the logs using journalctl.

47

…forget it all… if we login via ssh, it’s not able to get command redis-cli.
We make “apt install redis” … and this was the failure - our failure
If we login via proxmox-console (!) the command “redis-cli” is able…
But there are two numbers … which we should/could erase ??

redis-cli smembers node/2/flags
no modules
redis-cli smembers node/3/flags
no modules
48

Usually you need to remove both.

1 Like
49

Good morning,
… and thank you very much. Now we were able to install all Updates.
core mail sogo dhcp and nextcloud are the newest versions now…
… and we can login !
Have a good New Year !

1 Like