Bug 1376408
Summary: | [RFE] Allow the 'run puppet' button to trigger a Remote Execution Job | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Rich Jerrido <rjerrido> |
Component: | Puppet | Assignee: | satellite6-bugs <satellite6-bugs> |
Status: | CLOSED WONTFIX | QA Contact: | Katello QA List <katello-qa-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2.0 | CC: | bkearney, inecas, jcallaha, mburgerh, oprazak, rlavande, swadeley |
Target Milestone: | Unspecified | Keywords: | FutureFeature |
Target Release: | Unused | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-09-04 19:13:14 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Rich Jerrido
2016-09-15 11:40:31 UTC
*** Bug 1325812 has been marked as a duplicate of this bug. *** Just realized I had a bug for this already :/ Description of problem: For each host, we show a 'Run Puppet' button, that currently requires manual set up and does not integrate nicely with the new REX framework. Ideally, the 'Run Puppet' functionality should just forward to the 'Run Puppet Once' job template. Otherwise, this eternally grayed out button will raise eyebrows and questions. Considering we have the required parts in place now (SSH authentication for REX is there anyway), we could enable it (by default) by: - editing the default /etc/foreman/settings.yaml to enable puppetrun - editing the default /etc/foreman-proxy/settings.d/puppet.yml to: - set :puppet_provider to puppetssh - set :puppetssh_keyfile to /usr/share/foreman-proxy/.ssh/id_rsa_foreman_proxy (the key we use for REX as well) This still doesn't integrate with REX nicely, but at least it works out of the box this way (for new hosts that have the public key). Alternatively, the 'Run Puppet' button could be hidden and people would just rely on 'Run job'. Version-Release number of selected component (if applicable): SNAP 7.1 How reproducible: Steps to Reproduce: 1. Open host page 2. Focus eyes on right most corner of white part of screen, next to 'Delete' 3. Actual results: 'Run Puppet' button is grayed out and visible. Expected results: Button is either hidden on usable (preferably by default, preferably through REX) Are there updates we can pass along as far as ETA or plan moving forward? Any updates? Created redmine issue http://projects.theforeman.org/issues/17973 from this bug Putting on our backlog: let's see how this stand to other priorities we have to see when this one will et fixed Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you. Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you. There was a request to re-open this, but we are keeping it closed. We do not see this feature being developed in the near future. Users can use remote execution jobs manually if they desire. |