Project

General

Profile

Bug #11094

Cannot publish content view as non-admin user

Added by Justin Sherrill about 6 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1236740
Description of problem:
When trying to publish a content view as a unprivileged user, with limited access it will fail to clone and publish if you cannot view any orgs or locations on the 'default' capsule.

Version-Release number of selected component (if applicable):
Satellite 6.0.8

How reproducible:
Easily

Steps to Reproduce:
1. Create a Organization and Location outside of the defaults.
2. Create user with limited access associated to the Organization and Location. (I have provided ACL list for the user.)
3. Create Content View
4. Publish Content View

Actual results:
Failed to publish with error "Validation failed: Organization ids Invalid organizations selection, you must select at least one of yours, Location ids Invalid locations selection, you must select at least one of yours"

Expected results:
It should provide feedback as to why it failed.

Additional info:

Associated revisions

Revision 2de120a2 (diff)
Added by Justin Sherrill about 6 years ago

fixes #11094 - assign default location to new puppet environments

this way non-admin users can create them, as they need to be assigned
to at least one location if a non-admin user creates them

Also fixes a class loading issue seen in development during publish

Revision df4fa492
Added by Justin Sherrill about 6 years ago

Merge pull request #5350 from jlsherrill/11094

fixes #11094 - assign default location to new puppet environments

History

#1 Updated by The Foreman Bot about 6 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/5350 added
  • Pull request deleted ()

#2 Updated by Eric Helms about 6 years ago

  • Legacy Backlogs Release (now unused) set to 31
  • Triaged changed from No to Yes

#3 Updated by Justin Sherrill about 6 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF