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

Non-admin creating volume with same name as an admin-only stack gives ownership of the stack #3273

Closed
ghost opened this issue Oct 16, 2019 · 0 comments · Fixed by #3337
Closed
Assignees
Milestone

Comments

@ghost
Copy link

ghost commented Oct 16, 2019

Bug description
As a non-admin, creating a volume with same name as an admin-only stack gives ownership of the stack to the non-admin user

Expected behavior
Creating a volume with the same name as a stack should not give ownership of a stack to another user

Steps to reproduce the issue:

  1. Deploy a stack as an admin named test
    image

  2. Log in as a non-admin and create a volume named test

  3. See that non-admin user now has ownership of the stack
    image

Technical details:

  • Portainer version: 1.22.1
  • Docker version (managed by Portainer): 19.03.03
  • Platform (windows/linux): Linux (Ubuntu 18.04.02 LTS)
  • Command used to start Portainer (docker run -p 9000:9000 portainer/portainer): docker run
  • Browser: chrome
@ghost ghost added this to Need triage in Bug triage via automation Oct 16, 2019
@deviantony deviantony added this to the next milestone Oct 16, 2019
@deviantony deviantony removed this from the next milestone Oct 31, 2019
@deviantony deviantony self-assigned this Oct 31, 2019
@deviantony deviantony added priority/high Core team priority and removed shortlist labels Oct 31, 2019
@deviantony deviantony added this to the next milestone Nov 12, 2019
@ghost ghost moved this from Need triage to Confirmed in Bug triage Nov 28, 2019
@ghost ghost removed this from Confirmed in Bug triage Nov 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant