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 1278639 - Orchestration error does not prevent reboot of a discovered host
Summary: Orchestration error does not prevent reboot of a discovered host
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Discovery Plugin
Version: 6.1.3
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: 1287901
TreeView+ depends on / blocked
 
Reported: 2015-11-06 04:24 UTC by Jacob Hunt
Modified: 2019-11-14 07:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-03 10:01:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
on error, discovered host doesn't reboot. (66.32 KB, image/png)
2016-03-03 09:52 UTC, Sachin Ghai 		no flags Details
View All

Description Jacob Hunt 2015-11-06 04:24:10 UTC 
Description of problem:

When provisioning a system with discovery I can fill out the needed information (hostgroup etc.) but if any part of the form is missing satellite will reboot the discovered machine but does not let the user continue to finish provisioning.


How reproducible:

Always

Steps to Reproduce:

1. boot a new host in discovery mode
2. click provision host in satellite
3. fill out the information. If root password is missing or any form data causes an error (network conflict) and you click submit the form will error out and stay on the "provision host page"
4. Satellite reboots the host even though provisioning is not complete
5. Correct form data and click submit again
6. Satellite will now hang on the "rebooting host" step because the host was already rebooted in step 3

Actual results:

At that point there is no way to continue provisioning. You have to cancel the  provisioning, delete the discovered host and reboot the host into discovery mode again. This also usually leaves orphened information in dhcpd.leases file and sometimes in dns. Those two sources will need to be manually deleted before provisioning the host again.
Comment 2 Lukas Zapletal 2015-11-16 10:00:11 UTC 
This reboot error will be fixed in 6.1.4.

*** This bug has been marked as a duplicate of bug 1196658 ***
Comment 3 Lukas Zapletal 2015-11-16 12:13:13 UTC 
Ok I have reproduced. We've fixed similar bug already in 6.1.1 (not 6.1.4 that was a typo), but there is still one.

WORKAROUND: Fix the cause of the orchestration error that triggers reboot.
Comment 4 Lukas Zapletal 2016-03-03 09:34:42 UTC 
Can't reproduce on Satellite 6.2 build, sending to QE.
Comment 5 Sachin Ghai 2016-03-03 09:51:19 UTC 
Its not reproducible with Satellite 6.2 snap1. Please see the screenshot for verification where host is not rebooted even though error messages are populated on form submission.
Comment 6 Sachin Ghai 2016-03-03 09:52:34 UTC 
Created attachment 1132706 [details]
on error, discovered host doesn't reboot.
Comment 7 Sachin Ghai 2016-03-03 10:01:45 UTC 
Closing this bz, Please feel free to re-open or file a new if you come across this issue again.
Note You need to log in before you can comment on or make changes to this bug.