RHV now provides a script to clean up a failed SHE deployment. This likely supersedes the current info in Cleaning Up a Failed Self-hosted Engine Deployment in the SHE Guide. A new procedure is required (cleaning the shared storage appears not to be part of the script).
Assigning to Emma for review.
Hi Simone, With regards to the script to clean up a failed HE installation, could you please explain step 4. The command seems to show only how to clean up the storage. But not how to choose a different one. Also Did you mean choose a path other than /mnt/nsednev_he_4/* but use the same command rm -rf Relevant script: Interrupt hosted-engine --deploy: ^C[ ERROR ] Failed to execute stage 'Closing up': SIG2 [ INFO ] Stage: Clean up [ INFO ] Generating answer file '/var/lib/ovirt-hosted-engine-setup/answers/answers-20170206145745.conf' [ INFO ] Stage: Pre-termination [ INFO ] Stage: Termination [ ERROR ] Hosted Engine deployment failed: this system is not reliable, please check the issue,fix and redeploy Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20170206144452-sj4lh8.log 3)Run /usr/sbin/ovirt-hosted-engine-cleanup to remove any leftover from the host: # /usr/sbin/ovirt-hosted-engine-cleanup This will de-configure the host to run ovirt-hosted-engine-setup from scratch. Caution, this operation should be used with care. Are you sure you want to proceed? [y/n] y -=== Destroy hosted-engine VM ===- -=== Stop HA services ===- -=== Shutdown sanlock ===- shutdown force 1 wait 0 shutdown done 0 -=== Disconnecting the hosted-engine storage domain ===- -=== De-configure VDSM networks ===- -=== Stop other services ===- -=== De-configure external daemons ===- -=== Removing configuration files ===- ? /etc/init/libvirtd.conf already missing - removing /etc/libvirt/nwfilter/vdsm-no-mac-spoofing.xml ? /etc/ovirt-hosted-engine/answers.conf already missing - removing /etc/ovirt-hosted-engine/hosted-engine.conf - removing /etc/vdsm/vdsm.conf - removing /etc/pki/vdsm/certs/cacert.pem - removing /etc/pki/vdsm/certs/vdsmcert.pem - removing /etc/pki/vdsm/keys/vdsmkey.pem - removing /etc/pki/vdsm/libvirt-spice/ca-cert.pem - removing /etc/pki/vdsm/libvirt-spice/ca-key.pem - removing /etc/pki/vdsm/libvirt-spice/server-cert.pem - removing /etc/pki/vdsm/libvirt-spice/server-key.pem ? /etc/pki/CA/cacert.pem already missing ? /etc/pki/libvirt/*.pem already missing ? /etc/pki/libvirt/private/*.pem already missing ? /etc/pki/ovirt-vmconsole/*.pem already missing - removing /var/cache/libvirt/qemu - removing /var/run/ovirt-hosted-engine-ha/vm.conf - removing /var/run/ovirt-hosted-engine-ha/vm.conf.20170206145727 4)Clean the shared storage or choose a different one: rm -rf /mnt/nsednev_he_4/*
(In reply to Emma Heftman from comment #2) > Hi Simone, > With regards to the script to clean up a failed HE installation, could you > please explain step 4. The command seems to show only how to clean up the > storage. But not how to choose a different one. /usr/sbin/ovirt-hosted-engine-cleanup simply cleans up the host where it's run to ensure we don't have any leftover. Cleaning up the shared storage device is instead a manual action up to the user: how to clean it up depends from the specific storage technology (NFS vs iSCSI vs FC vs GlusterFS) but it's in general something it's better to do on the storage server side. The user has to necessary cleanup the shared storage if he wants to try again on it or he could also deploy on a different device (a different iSCSI or FC LUN, a different NFS share, a different gluster volume). In both the case is recommended cleaning up the host with /usr/sbin/ovirt-hosted-engine-cleanup
Hi Simone Please review and comment on the updated cleanup section in the SHE Installation guide. Note that I left the original error message that appeared in the documentation, but it appears to be different from the messages in your bug. Please confirm what should appear. http://file.tlv.redhat.com/~eheftman/bz1421003/html-single/#Cleaning_Up_a_Failed_Self-hosted_Engine_Deployment
(In reply to Emma Heftman from comment #5) > Please confirm what should appear. rm -rf /mnt/nsednev_he_4/* was specific to Nikolai Sednev's host; how to clean it up depends on how and where you tried to set it up. The error message on partial deployment could vary depending on where it got interrupted.
(In reply to Simone Tiraboschi from comment #6) > (In reply to Emma Heftman from comment #5) > > Please confirm what should appear. > > > rm -rf /mnt/nsednev_he_4/* > was specific to Nikolai Sednev's host; how to clean it up depends on how and > where you tried to set T up. > > The error message on partial deployment could vary depending on where it got > interrupted. Thanks Simone. For the storage cleanup should I just write rm -rf <storage directory>/*
Hi Nikolai Could you please review the new cleanup documentation and especially step 3 which discusses cleaning up storage. http://file.tlv.redhat.com/~eheftman/bz1421003/html-single/#Cleaning_Up_a_Failed_Self-hosted_Engine_Deployment
(In reply to Emma Heftman from comment #8) > Hi Nikolai > Could you please review the new cleanup documentation and especially step 3 > which discusses cleaning up storage. > > http://file.tlv.redhat.com/~eheftman/bz1421003/html-single/ > #Cleaning_Up_a_Failed_Self-hosted_Engine_Deployment Looks fine, I have no objections.
Hi Megan Please review this merge request: https://gitlab.cee.redhat.com/rhci-documentation/docs-Red_Hat_Enterprise_Virtualization/merge_requests/385 Link to updated documentation: http://file.tlv.redhat.com/~eheftman/bz1421003/html-single/ #Cleaning_Up_a_Failed_Self-hosted_Engine_Deployment
The published documentation is available here: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html-single/self-hosted_engine_guide/#Cleaning_Up_a_Failed_Self-hosted_Engine_Deployment