Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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:
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.
--------------
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
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
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: