Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1647216 - Lack of edit_smart_proxies permission causes error when setting host to Build
Summary: Lack of edit_smart_proxies permission causes error when setting host to Build
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Foreman Proxy
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.8.0
Assignee: satellite6-bugs
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-06 21:25 UTC by Dylan Gross
Modified: 2020-10-27 12:58 UTC (History)
7 users (show)

Fixed In Version: foreman-1.20.0-0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 12:58:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 25248 0 Normal Closed Check before build checks required edit_smart_proxies permission 2020-10-28 17:15:28 UTC
Red Hat Knowledge Base (Solution) 3679751 0 None None None 2018-11-06 21:38:05 UTC
Red Hat Product Errata RHSA-2019:1222 0 None None None 2019-05-14 12:38:47 UTC
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 12:58:21 UTC

Description Dylan Gross 2018-11-06 21:25:20 UTC 
Description of problem:

  Lack of edit_smart_proxies permission causes error when setting host to Build.

When a non-admin user does not have the edit_smart_proxies filter on their role, they will receive an error popup saying:   
    "Failure deploying via capsule <capsule.name>: true"

  Upstream already appears aware of this: 

       https://projects.theforeman.org/issues/25248


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

  Red Hat Satellite 6.4.0

How reproducible:  Always

Steps to Reproduce:
1.  As a non-admin user without "edit_smart_proxies" filter, select a host, then click "Build"


Actual results:

   Error saying:   "Failure deploying via capsule <capsule.name>: true"

Expected results:

   No error message.
 
Additional info:
Comment 7 Lukas Pramuk 2019-02-26 13:04:02 UTC 
VERIFIED.

@satellite-6.5.0-6.beta.el7sat.noarch
foreman-1.20.1.10-1.el7sat.noarch

by the manual reproducer desribed in comment #0:

1) Have a Satellite with Internal Capsule set up 

2) Clone Manager role but edit filter for Capsule and remove "edit_smart_proxies" perm

3) Create non-admin user "tester" and assign him the only role created in previous step

4) As user "tester" provision a host

5) As user "tester" try to set the host from previous step to Build

FIX: 
Popup appears with the info but no warnings/errors

vs. 

REPRO:
Popup appears with the following error
--------------

(x) The following errors may prevent a successful build:

Capsules

    Failure deploying via capsule <SAT_FQDN>: true.

--------------
Comment 10 errata-xmlrpc 2019-05-14 12:38:40 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:1222
Comment 11 Bryan Kearney 2019-11-06 11:00:28 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25248 has been resolved.
Comment 16 errata-xmlrpc 2020-10-27 12:58:03 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4366
Note You need to log in before you can comment on or make changes to this bug.