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')']}'