-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Anonymous group, Thredds config page, not working after upgrade from 1.7.3 to 3.5.1 #401
Comments
@tlvu |
Provided via private messaging. |
@tlvu |
Provided tarball of |
@tlvu |
@fmigneault Sorry I do not have the state before the migration since the new broken Magpie was autodeployed directly on my dev VM the moment that PR was merged. Normally, PR is merged only after throughout testing so that has never been an issue before. |
Revert "Merge pull request #107 from bird-house/magpie-thredds" This reverts commit 7be3eea, reversing changes made to c0ffb41. PR #107 upgrade path is unstable, see issue Ouranosinc/Magpie#403 and issue Ouranosinc/Magpie#401. Revert so we can remove the autodeploy block on production instances and give us time to properly test any upcoming fixes. Also unblock Finch to go to production #138. Branch https://github.com/bird-house/birdhouse-deploy/tree/restore-previous-broken-magpie-upgrade-so-we-can-work-on-a-fix created so we have a place to work on a fix. Matching notebooks revert: Ouranosinc/pavics-sdi#211
Describe the bug
Going here https://lvupavics.ouranos.ca/magpie/ui/groups/anonymous/thredds
Result in this page:
With the following error in
docker logs magpie
.Note that the Jenkins test suite actually passed on that instance after the upgrade: https://daccs-jenkins.crim.ca/job/PAVICS-e2e-workflow-tests/job/master/239/console
Also when the magpie container was recreated at the moment of the upgrade, there was no error related to DB migration.
To Reproduce
Steps to reproduce the behavior:
My dev server autodeployed the PR bird-house/birdhouse-deploy#107
Expected behavior
Being able to see the permissions for Thredds for the anonymous group.
The text was updated successfully, but these errors were encountered: