Try WeKan Snap Manual upgrade to newest Candidate? #4780
Comments
|
Hi @xet7, I went ahead and followed your guide for the manual upgrade procedure from WeKan-Snap Stable v6.09 to Candidate 6.62. It seems like it was a great success! Before the upgrade:
After the upgrade:
For us, we use WeKan heavily for IT projects, tasks, and long-term strategy. I also use it for facilitating our ERP migration project, and our Accounting & HR teams also use it, although not as much as I think they should! That being said our Some notes maybe specific to our case when following your upgrade instructions:
Once I looked up that this is just a diagnostic tool, I just went ahead and forced it:
Started up and logged into WeKan and everything seems to work great! Exactly as we left it. All our attachments seem intact as well, which is mostly just PDFs and PNGs. So I hope this is big success for you!!! I did notice the Activities feed seems to spam attachment deletions, however from my spot-checking they all still seem to present on those cards: For cleanup, I should be good to delete the Moreover, some features we were excited about and looking forward to, wondering if they are working in v6.62?
2 new small bugs I noticed:
Do let me know if there's anything else I can do to help or test for you!!! Thanks very much!!! |
|
Thanks a lot! I updated these parts of wiki page: |
|
Because manual steps seem to work, I'll try can I make automatic upgrade working. |
Linked card shows the content of card that is somewhere else, like at other board. It's kind of realtime mirror. It's possible to make boards like dashboard, where you link most important cards from other boards to dashboard board, and see in realtime what is most important.
It is not fixed yet.
Can you record animated gif (e.g. with https://github.com/phw/peek) about that and add it as attachment to comment to this issue? Without any private data? |
Ask and you shall receive!! We have Lists of Current, H-P Projects, Tasks, L-P Projects, R&D, Ideas, Completed. Since the Sidebar menu overlaps the last 2 lists, any cards linked in the Activities history do not open. This was not the case back in v6.09. You can see there is 1 card that is able to open from the 3rd list from the right, our On-Hold/Research list, however it seems cut-off on the side and not fully visible. Cards in all the other lists seem to dim & open fine from that Activities history, I just specifically avoided those to do less obfuscating. Hope this is helpful! Lemme know if I can be of any further assistance. (: As you can see we heavily use this wonderful application so always happy to help. Unrelated: Is the Favicon supposed to be gone!? On the prior version we still had the default WeKan logo. My pinned WeKan tab on Firefox ESR v102 now: |
No, it's a bug. Thanks! |
|
@xet7 |
|
@mohammadZahedian Manual updating does work. Size etc is explained at: This month I try to finish some features. I maybe try to make automatic update working at next month, January 2023. (Or this month, if I have time. I don't know yet.) |
|
Related to using external file storage, upgrade info: |
|
I tried to update to newest version according to "Candidate WeKan Snap Manual Upgrade" but it failed in step 15: root@wekan-test:~# snap stop wekan root@wekan-test:~# snap start wekan.mongodb root@wekan-test:~# mongorestore --drop --port 27019 root@wekan-test:~# snap logs wekan root@wekan-test:~# ls -l /snap/wekan/2323/bin |
|
Did you do steps 13 and 14? What does this command produce? |
|
New version of mongorestore is is package mongodb-database-tools. That should be used for mongorestore. |
|
@xet7 titles are weird i think it must be some thing about language pack |
|
@mohammadZahedian |
The problem is not mongorestore, the problem ist mongodb.service in the snap: it doesnt start because it cannot find the "mongo" command as you can see from the logs:
mongorestore cant connect because the service is not running. |
|
What does this command show? |
|
It's latest:
|
|
@xet7 |
|
@mohammadZahedian No, your attachments are not gone. It's just that you have not set root-url correctly #4803 (comment) |
|
Try starting WeKan: And then mongorestore. |
|
It doesn't start because mongodb.service cannot start: 2023-01-09T11:58:22+01:00 wekan.mongodb[1403146]: error: error running snapctl: get which option? |
|
Yes, I did ... but i will start a new attempt with a fresh copy of our production system ... maybe something went wrong during copy. I will report later. |
|
@xet7:
But the attachments are missing:
mongorestore version is: |
|
From that error message it seems WeKan has too old MongoDB driver npm package. I'll try can I upgrade it. |
|
Hi @xet7, we tried to upgrade from stable (6.09) to candidate (latest up to date 6.98) and we are not being able to see attachments. Here is a report on the step by step process we followed: Migration guide reportWe have a wean snap v6.09 instance running on a ubuntu 20.04 server which is production. We are trying to migrate to Candidate version in a different server (ubuntu 20.04), we are not able to see the attachments, when we open the cards it says: “If filename is invalid, upload or rename is cancelled.”. This are the exact step by step we did:
Are we doing something wrong? Thanks, Santiago |
|
Same issue here. Updated from snap stable version 6.09 to candidate 6.99 using the instructions provided (https://github.com/wekan/wekan-snap/wiki/Candidate-WeKan-Snap-Manual-Upgrade), everything seems to work except attachments and avatars. Running Debian 11.7 here. The files are there in /var/snap/wekan/common/files/attachments/ and /var/snap/wekan/common/files/avatars/ but are zero bytes, as reported by others. No errors were reported during the mongodump and mongorestore commands: Trying to load the avatars or attachments result in a 503 error code. For example, my Avatar is linked at https://ourwebsite/cfs/files/avatars/RXZMjrbqNzfrBsCdg/Schermafbeelding%202021-11-11%20om%2022.46.03.png but results in a 503. Maybe this is relevant: We use a Nginx proxy proxy on another server to handle traffic to this wekan server, which also handles certificates and https. The wekan server hosts at port 8080. Everything else is working: Sessions were restored, logging out and in works (using Google OAuth), new cards and responses work, uploading and downloading new attachments works as expected. Only the current avatars and attachments are gone. |
|
@Milenco (or someone else) can you try this: See is attachment and avatar filename/path/URL wrong?
I think, fix would probably be to in For upgrading MongoDB from 3.x to newest, here https://github.com/wekan/wekan/blob/master/snapcraft.yaml#L93-L108 in Snap is commented out adding old version of MongoDB Tools etc. Also here https://github.com/wekan/wekan/blob/master/snap-src/bin/mongodb-control#L20 could be code to:
It is possible to build wekan Snap this way on Ubuntu amd64 I presume: And install WeKan Snap: |
Build from source and send PRIt's possible to build WeKan from source and send PR like this https://github.com/wekan/wekan/wiki/Emoji Docker
|
|
Hey @xet7, Thanks for the detailled steps. Currently I'm in holiday, but I will test it when I'm back (in ~two weeks) and report back then. Sorry this is taking some time on my side.. |
|
How would the upgrade path from 6.09 snap to latest docker look like? I presume first step would be getting 6.09 docker image to run, then somehow attempt to migrate data, then start upgrading (version by version or can larger jumps be made?) Side note, |
|
I'm developing new upgrade path. Previous incomplete migrations are not in use. |
|
Preferred way to upgrade Snap is to do nothing. There will be automatic upgrade to newest WeKan, when I get that upgrade migrations working. |
|
Looking forward! 🥰 |
|
@xet7 Is the automatic upgrade meant to be working now as the ticket has been closed? [0] # snap list; snap warnings; snap refresh wekan
Name Version Rev Tracking Publisher Notes
core 16-2.60.4 16202 latest/stable canonical✓ core
wekan 6.09 1999 latest/stable xet7 -
--
last-occurrence: 6 days ago, at 16:17 CET
warning: |
the snapd.apparmor service is disabled; snap applications will likely not start.
Run "systemctl enable --now snapd.apparmor" to correct this.
--
snap "wekan" has no updates available |
|
Your project, your rules, but losing the ability to subscribe to specific issues I care about is disappointing. Glad to see a fix is still in the works at least. |
It is much faster to look at short Big Picture Roadmap wiki page, than to receive hundreds of emails. That is why there is also upcoming WeKan feature to combine notifications to one notification. There also were many duplicates of same issues. There is nothing disappointing in about having faster progress of getting features and fixes. |
There is a possibility, that you are right. So I added this limitation to https://github.com/wekan/wekan/blob/main/FUTURE.md
I also opened those issues that were not specifically about Import/Export/Sync etc. If some closed issue needs more discussion, someone can comment in that issue, so I can open it again. |
|
I think I read almost all the posts. I think I understand all the commands I executed, but I still miss few informations. I tried to restore to a new Wekan without success for attachments and avatars. For avatars, it looks rather easy: I can request users to put new ones, for attachments it's harder. As far as I understand, we make a mongodump from old version. And we use mongorestore (new version) to restore the database. So mongo, is restoring data "knowing" the database version difference. Then what "break" attachments looks to be linked with what is/was used to handle files at the Meteor level. So, I believe some works need to be done by wekan at service startup to detect we have old file datas in the db and need to convert them to new datas. Is this right? If yes? How could we request/observe this "migration" script to try to help overcome the trouble. As it something to do with #4891 ? Can we help in anything? Other remarks:
|
|
I wrote about current status here https://github.com/wekan/wekan/discussions/5291#discussioncomment-8407744 |
|
Since I do not have a lot of attachments or boards, I ended up migrating manually to docker. In short: Export your boards as JSON from WeKan snap. 7BF5 Manually export all attachments you care about. # Clone this repo
git clone --depth 1 https://github.com/wekan/wekanEdit the wekan/docker-compose.yml for some needed parameters, in my case namely: - ROOT_URL={{ wekan_root_url }} # <=== using only at same laptop/desktop where Wekan is installed
- MAIL_URL={{ wekan_mail_url }}
- MAIL_FROM={{ wekan_mail_from }}Then spin up the docker mongo and wekan: cd wekan
docker compose up -d
# Exec into the container
docker exec -it wekan-app bash
# Make attachment imports not do anything instead of failing, so import can go through
sed -i -e 's|Attachment\.load|//|g' -e 's|Attachment\.write|//|g' /build/programs/server/app/app.js
# Exit out of the container
exit
# Restart containers to apply changes
docker compose restartImport the boards by copypasting the JSON. Manually import attachments back. Future plans are to fix this importing to allow to do this without hacks and manual attachmetn exports/imports - #5207 (comment) - but I tired of waiting. If all fails, just keep using the snap instance, these steps do not require you to take it down. |
Does someone have time to test? It's not automatic upgrade, because if there is not enough disk space, there could be data loss.
https://github.com/wekan/wekan-snap/wiki/Candidate-WeKan-Snap-Manual-Upgrade
The text was updated successfully, but these errors were encountered: