Bug 1335300
Summary: | Features are not being associated correctly to job templates | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Stephen Benjamin <stbenjam> |
Component: | Remote Execution | Assignee: | Stephen Benjamin <stbenjam> |
Status: | CLOSED ERRATA | QA Contact: | jcallaha |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2.0 | CC: | bbuckingham, cwelton, omaciel |
Target Milestone: | Unspecified | Keywords: | Regression, Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rubygem-foreman_remote_execution-0.3.0.11-1 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-07-27 11:28:38 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Stephen Benjamin
2016-05-11 20:12:49 UTC
Created from redmine issue http://projects.theforeman.org/issues/15017 Upstream bug assigned to stbenjam WORKAROUND: If not approved for 6.2, the user will have to go to the Administer / Remote Execution Features and assign all of the various katello templates to the features. Not a very pleasant experience. Verification steps: 1. Go to Administer / Remote Execution Features and verify that "Katello: Package Install" has a template associated 2. Test a package install in Katello via Remote execution (Hosts/ Content Hosts/ package install / Install via Remote Execution) Moving to POST since upstream bug http://projects.theforeman.org/issues/15017 has been closed Failed QA in Satellite 6.2 Beta 2. foreman-1.11.0.39-1.el7sat.noarch Remote Execution Features are currently not populated by default. Verified in Satellite 6.2 Beta Snap 18.1. The defaults are now correctly populated as expected. 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/RHBA-2016:1501 |