Bug 1474066
Summary: | Cannot deploy RHV ISO via PXE/kickstart | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Rhys Oxenham <roxenham> |
Component: | Documentation | Assignee: | rhev-docs <rhev-docs> |
Status: | CLOSED DUPLICATE | QA Contact: | rhev-docs <rhev-docs> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.4 | CC: | lbopf, lsurette, rbalakri, srevivo, ycui, ykaul |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-07-25 01:50:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Docs | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Rhys Oxenham
2017-07-23 14:36:34 UTC
Made some progress with this, it appears that the docs are wrong - it points you towards using /path/to/LiveOS/squashfs.img as the image to be used for installation of the RHVH image, but in fact the actual squashfs is located in Packages... Packages/redhat-virtualization-host-image-update-4.1-20170706.0.el7_3.noarch.rpm As per the kickstart example in the root of the image, the squashfs can be extracted from this rpm: rpm2cpio /run/install/repo/Packages/redhat-virtualization-host-image-update*|cpio -ivd Then, when this file is used instead with "liveimg --url=http://..." installation works perfectly. This is therefore a documentation issue for when setting up a PXE/kickstart installation. Thanks for reporting, Rhys. We're actually discussing the same thing in bug 1447713, so I'm going to close this one as a duplicate. Feel free to leave any additional comments on the other bug. *** This bug has been marked as a duplicate of bug 1447713 *** (In reply to Lucy Bopf from comment #2) > Thanks for reporting, Rhys. We're actually discussing the same thing in bug > 1447713, so I'm going to close this one as a duplicate. > > Feel free to leave any additional comments on the other bug. > > *** This bug has been marked as a duplicate of bug 1447713 *** Apologies, wrong bug. The correct ID is bug 1435257. *** This bug has been marked as a duplicate of bug 1435257 *** |