Upgrade from 6.2.0 to 7.0.0 troublesome

[maxju]

Hi!
First of all thanks to the developers!
Luckily my OpenCloud Instance is working again now but I had some trouble upgrading to 7.0.0.
I am writing this issue to give some feedback on the release notes and ask about the recommended update strategy.

Release Notes

Whenever I upgrade, I check the GitHub Release notes. When I don't see anything that says "Caution" or "Breaking Change", I upgrade.
The OpenCloud 7.0.0 Release Notes just said "⏳ First startup may take a few minutes", so I thought I was good.
The upgrade caused my container to crash loop because the config was incomplete. After looking again, I saw buried in the release note paragraph "requires config change". Okay, my bad for not reading all the way through.
Still, I would wish for a clearer warning about breaking changes.

Upgrade procedure

So I clicked the link to the upgrading guide, carefully crafted a docker run command with my volume mounts in order to use opencloud init --diff which printed a suggestion (?) on how to update the config. Because my config is in a docker volume I had to access it through the container shell. So I used vi to manually copy and paste the config suggestions (or at least the ones I thought are necessary).
Is this the intended path? Even if I had mounted the config to my filesystem this requires quite a lot of administration work.

[jasondaigo]

you can copy the patch output to a patch file in the config folder and apply it. learned that today :-)

[AlexAndBear]

Hope this helps:

https://docs.opencloud.eu/docs/next/admin/maintenance/upgrade/upgrade-guide

The docs team is currently working on make it clear how to apply the mentioned patch file

[smoothscholar]

@AlexAndBear

Why don't you guys change the release notes to clearly state "Breaking Change"? The current line is totally insufficient.

[maxju]

you can copy the patch output to a patch file in the config folder and apply it. learned that today :-)

Yes I also learned that yesterday! The patch command did't work because the file was busy, I'll have to try this again next time with lsof.

Hope this helps:

https://docs.opencloud.eu/docs/next/admin/maintenance/upgrade/upgrade-guide

The docs team is currently working on make it clear how to apply the mentioned patch file

Yes, that is the guide I followed. Making it clearer how to apply the patch file would be nice, yes.

[jgoclawski]

Here's my $0.02. I also found it a bit difficult to figure out the best approach to apply the changes (without doing it manually), so what I did for step "Verify Configuration Changes" was:

# inside container:
  opencloud init --insecure "no" --diff
# if it returns any changes, review them and apply with `patch` command
  cd /etc/opencloud
  patch -p3 -i /etc/opencloud/opencloud.config.patch

But I think it would be great if the opencloud init command could also apply the changes as an option, so that the manual "patch" command is not needed. Something like opencloud init --apply-diff or similar?
I even tried running it without the --diff param but it generated passwords and secrets from scratch ;)

[kedanli]

Yes, that is the guide I followed. Making it clearer how to apply the patch file would be nice, yes.

Yes the update process was painful for me as well. I´m not that experienced with all this and it took me quite some time and the help of chatgpt to figure out how to implement the changes in my existing docker compose files. 😓