Bug 1184597

1. Proposed title of this feature request  
      Rebooting content hosts

Question 2 is private for internal only      
      
    3. What is the nature and description of the request? 

To be able to reboot content hosts after pushing packages out through the webui since some packages such as kernel updates require a reboot 
      
    4. Why does the customer need this? (List the business requirements here)  

So the customer does not have to ssh to each machine for large enviroments and manually reboot each machine. 
      
    5. How would the customer like to achieve this? (List the functional requirements here)  

Add a section in the webui or a checkbox where a reboot option can be scheduled or added after a package update
      
    6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.  

once its added to the webui, spin up a rhel 6.5 system, push all updates, do the new reboot options and see if client reboots and is on the 6.6 kernel.
      
    7. Is there already an existing RFE upstream or in Red Hat Bugzilla? Not that I can find, talked in satellite6 channel and nothing like this has been created 
      
    8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  6.1/6.2/6.3
      
    9. Is the sales team involved in this request and do they have any additional input?  no
      
    10. List any affected packages or components.  


Installed Packages

    candlepin-0.9.23.1-1.el7.noarch
    candlepin-common-1.0.1-1.el7.noarch
    candlepin-guice-3.0-2_redhat_1.el7.noarch
    candlepin-scl-1-5.el7.noarch
    candlepin-scl-quartz-2.1.5-6.el7.noarch
    candlepin-scl-rhino-1.7R3-3.el7.noarch
    candlepin-scl-runtime-1-5.el7.noarch
    candlepin-selinux-0.9.23.1-1.el7.noarch
    candlepin-tomcat-0.9.23.1-1.el7.noarch
    elasticsearch-0.90.10-6.el7sat.noarch
    katello-1.5.0-30.el7sat.noarch
    katello-certs-tools-1.5.6-1.el7sat.noarch
    katello-default-ca-1.0-1.noarch
    katello-installer-0.0.64-1.el7sat.noarch
    katello-server-ca-1.0-1.noarch
    pulp-admin-client-2.4.3-1.el7sat.noarch
    pulp-katello-0.3-4.el7sat.noarch
    pulp-nodes-common-2.4.3-0.1.beta.el7sat.noarch
    pulp-nodes-parent-2.4.3-0.1.beta.el7sat.noarch
    pulp-puppet-plugins-2.4.3-1.el7sat.noarch
    pulp-puppet-tools-2.4.3-1.el7sat.noarch
    pulp-rpm-admin-extensions-2.4.3-1.el7sat.noarch
    pulp-rpm-plugins-2.4.3-1.el7sat.noarch
    pulp-selinux-2.4.3-1.el7sat.noarch
    pulp-server-2.4.3-1.el7sat.noarch
    python-gofer-qpid-1.3.0-1.el7sat.noarch
    python-isodate-0.5.0-1.pulp.el7sat.noarch
    python-kombu-3.0.15-12.pulp.el7sat.noarch
    python-pulp-bindings-2.4.3-1.el7sat.noarch
    python-pulp-client-lib-2.4.3-1.el7sat.noarch
    python-pulp-common-2.4.3-1.el7sat.noarch
    python-pulp-puppet-common-2.4.3-1.el7sat.noarch
    python-pulp-rpm-common-2.4.3-1.el7sat.noarch
    python-qpid-0.22-15.el7.noarch
    python-qpid-qmf-0.22-37.el7.x86_64
    qpid-cpp-client-0.22-42.el7.x86_64
    qpid-cpp-server-0.22-42.el7.x86_64
    qpid-cpp-server-linearstore-0.22-42.el7.x86_64
    qpid-java-client-0.22-7.el7.noarch
    qpid-java-common-0.22-7.el7.noarch
    qpid-proton-c-0.7-2.el7.x86_64
    qpid-qmf-0.22-37.el7.x86_64
    qpid-tools-0.22-13.el7.noarch
    ruby193-rubygem-katello-1.5.0-93.el7sat.noarch
    rubygem-hammer_cli_katello-0.0.4-14.el7sat.noarch
    rubygem-smart_proxy_pulp-1.0.1-1.1.el7sat.noarch
    satellite1.released-el7.satellite.lab.eng.rdu2.redhat.com-qpid-broker-1.0-1.noarch
    satellite1.released-el7.satellite.lab.eng.rdu2.redhat.com-qpid-client-cert-1.0-1.noarch
     
    11. Would the customer be able to assist in testing this functionality if implemented?  yes

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Our environment is big, managing the systems manually is too much of time consuming. In satellite5 its possible to schedule reboot and applying patches for a host, but this is not available in sat6. 

If you can apply this to a host collection group that would be great.

*** Bug 1293553 has been marked as a duplicate of this bug. ***

Moving 6.2 bugs out to sat-backlog.

Moving 6.2 bugs out to sat-backlog.

Hi,

This can be fixed with Remote Execution in 6.2.

Closing this out.

Thanks,

- Chris Roberts