Skip to content
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

updating to beta causes loss of privileges #523

Closed
jt196 opened this issue Apr 5, 2021 · 9 comments
Closed

updating to beta causes loss of privileges #523

jt196 opened this issue Apr 5, 2021 · 9 comments

Comments

@jt196
Copy link

jt196 commented Apr 5, 2021

Version

On update from 0.14.5 to the beta (0.15) as of about 12pm today in Docker.
Version:

Bug description

Get a warning message on front page saying user isn't part of a group, so can't do anything.

I solved this by going into the user > admin > users > my user, assigning a group and rights to the user as the user had none of either after the update.

@vabene1111
Copy link
Collaborator

that is actually expected behavior as a user always needs to have some kind of group (guest, user or admin) to work properly.

Did you use that user before the update ? Because it should not have been usable except maybe if it was a superuser ...

@jonahwh
Copy link

jonahwh commented Apr 5, 2021

This happened to me with my superuser account as well.

@vabene1111
Copy link
Collaborator

yea this is a little dumb as superusers created with the old/manual setup dont have any groups .. i will see if i can add a little piece of code that automatically assigns superusers a group

@jt196
Copy link
Author

jt196 commented Apr 6, 2021

It was the main user on the system. So pre-upgrade, everything worked fine, afterwards, user wasn't in any groups and lacked permissions.

@vabene1111
Copy link
Collaborator

fixed this in 0.15.1. A default group (admin) is assigned to each existing superuser. This is only required for older installations as the newer ones add the groups automatically when creating the first user during the initial setup

@IxsharpxI
Copy link

been watching my logs for watchtower and it hasnt pulled the new image yet. im currently locked out of everything. looks like the fix is made. How long does it take to be available?

@MaxJa4
Copy link
Contributor

MaxJa4 commented Apr 6, 2021

Just some more minutes, building needs some time.

You can check at: https://github.com/vabene1111/recipes/actions/runs/723157207 and https://github.com/vabene1111/recipes/actions/runs/723157206

Judging by the build yesterday, it'll be done at 08:25 pm CEST (~ 55 min)

@jt196
Copy link
Author

jt196 commented Apr 6, 2021

been watching my logs for watchtower and it hasnt pulled the new image yet. im currently locked out of everything. looks like the fix is made. How long does it take to be available?

Follow the steps I outlined in the original post. You just check a box in the admin area.

@vabene1111
Copy link
Collaborator

Yea the build is extremly slow because libxml takes forever and the images are build for many architectures

@IxsharpxI you should have a superuser account which can assign groups to all users. If not i can help you restore it if needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants