Cloudron 6.2 released

[girish]

There will be a 6.2.5 tomorrow or the day after that will fix some of the regressions in the release.

• update: set memory limit properly
• Fix bug where renew certs button did not work
• sftp: fix rebuild condition that prevents apps from being uninstalled
• Fix display of user management/dashboard visiblity for email apps
• graphite: disable tagdb and reduce log noise
• graphs: fix graph display
• backups: fix linode storage backend

[martin]

@girish

Hi, I saw the notification that 6.2.5 is available, but when I attempt the update I receive "No update available".

Is it a matter of waiting a bit?

[d19dotca]

@martin Is it actually 6.2.5 for you? I just checked after seeing your message and I see 6.2.6. I wonder if they had to quickly pull 6.2.5 and issue 6.2.6 instead.

[ccfu]

@d19dotca @martin I currently have three Cloudrons, two showing update available to 6.2.6 and one showing 6.2.5. It doesn't seem to be possible to recheck manually once update available is shown in place of the check update button on the settings page.

[d19dotca]

@ccfu I could be wrong but I think if you logout of Cloudron and then back in and go to Settings, it will not show an update and then you can recheck it again.

[girish]

@ccfu you can go to an app's update section and there is a button there.

[girish]

@d19dotca Yeah, there was an issue with graphs. In fact, I am just staging 6.2.7.

[jdaviescoates]

@girish 6.2 seems to caused quite a few issues for quite a few people (at least the is the impression I'm getting from the forum, relative to most updates that seem to mostly go without issue).

Why do you think that is? Just because the new base images is a big change? or something else?

[martin]

@ccfu @d19dotca Sorry for the slow response.. the whole needing to sleep thing kicked in. Here it was indeed 6.2.5, and around an hour ago the 6.2.6 notification came through. Without needing to log out the update has now brought the cloudron automagically to 6.2.6

[nebulon]

@jdaviescoates we did have some issues and generally this is more a function of how large the feature set for a release is, as well as our user-base is also growing, so there are more cases which can fail. This time, as you indicated, the base images and more importantly the addon/services upgrades are adding quite a lot of complexity.