Update to 8.0 - Stuck on “removing containers for upgrade”

[necrevistonnezr]

Pretty much the headline - clicked update, since then I see removing containers for upgrade - 60 minutes now

In the event log:

{
  "taskId": "16920",
  "errorMessage": "Task 16920 crashed with code null",
  "timedOut": false
}

[necrevistonnezr]

Nevermind, after applying UIR (Universal-IT-Rule) a.k.a turing it off and turning it on again, it works (as usual with Cloudron )

[necrevistonnezr]

Another super bug :
In the Email event view, the boxes are not aligned

[nichu42]

OK, update getting stuck is one thing. But this is unacceptable.

[necrevistonnezr]

@nichu42 Right...?!?!

[nichu42]

BTW: Everything went smooth on my VPS. Thanks, Cloudron Team!

[girish]

Ah good to know, thanks for reporting ...

We only staged it late last night Only update if you feel like an early adopter at this point .

[nichu42]

I can hardly resist when I come across an update button somewhere.

[girish]

I am sure there is some xkcd for this

[lukas]

Cloudron 8.0 is released?

[humptydumpty]

@lukas it showed up for me after manually searching for an update - will wait on updating though. I'm somewhere between the early adopter and early majority groups, so the chasm I guess

[necrevistonnezr]

BTW, love the admin notes that use markdown (previously, I "hid" my notes in the cron tab with a leading "#"...). You can do really helpful stuff....

[Kubernetes]

Just to let you guys know that upgrade to 8.0.0 on my Cloudron with 22 Apps did work without problems.
Only thing I noticed was, that I had to re-mount ALL external CIFS drives manually, and therefore had to restart some Cloudron Apps which was using those.

[nichu42]

@Kubernetes Yes, same here. Just noticed this morning that the backup had failed because CIFS storage was not mounted.

[girish]

Interesting.. There is nothing inherently in the code that affects mounts. In fact, there is no code to unmount stuff automatically . I will test what is going on. I suspect the issue is with the DNS change. We have moved to systemd-resolved instead of unbound .

[marylou]

Hi, we did not initiate an update manually. According to the logs, Cloudron updated to v8.0.3 this morning at 6:58. The message "removing containers for upgrade" was still there at midday. Error message when going to an app: "This app is currently not responding. Please try refreshing the page in a few minutes."

After a manual reboot, all apps were "Configuring (Queued)" for a while. Now the first apps are running again. Yeah