Bug 1200952
| Summary: | [RFE] Quicker Installs by presenting ISO domain hosted kernel images to Run Once Screen | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Robert McSwain <rmcswain> | ||||
| Component: | ovirt-engine | Assignee: | jniederm | ||||
| Status: | CLOSED ERRATA | QA Contact: | Israel Pinto <ipinto> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 3.5.0 | CC: | bazulay, gklein, iheim, ipinto, istein, jniederm, lsurette, lveyde, mavital, mgoldboi, michal.skrivanek, rbalakri, Rhev-m-bugs, sherold, yeylon, ykaul | ||||
| Target Milestone: | ovirt-3.6.0-rc | Keywords: | FutureFeature | ||||
| Target Release: | 3.6.0 | Flags: | sherold:
Triaged+
|
||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 3.6.0-4 alpha3 | Doc Type: | Enhancement | ||||
| Doc Text: |
With this release, the Linux Boot Options section of the Run Once window allows users to select kernel and initrd files for Linux virtual machines. Available files are files from the ISO domain of type Unknown (i.e. not ISO, floppy, or disk).
|
Story Points: | --- | ||||
| Clone Of: | |||||||
| : | 1260666 (view as bug list) | Environment: | |||||
| Last Closed: | 2016-03-09 20:59:13 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1260666 | ||||||
| Attachments: |
|
||||||
ovirt-3.6.0-3 release Created attachment 1051125 [details]
Linux boot options
Start Verify with 3.6.0-03 I open the the tab 'Linux boot options' under 'Run once' dialog The combo box are not indent to label. See attached screen shot (comment 6) which browser? both firefox and chrome. 3 issues described above:
1 - UI - the indentation of the kernel path
2 - filtering for the relevant fields
3 - misleading name of of engine-ISO-uploader (it uploads not only ISOs ... for a
long time now)
I think only #1 & #2 should be addressed
Michal please assign to a virt group member.
(In reply to Barak from comment #13) > 3 issues described above: > 1 - UI - the indentation of the kernel path that is fixed in comment 9-10 in 3.6.0-4 > 2 - filtering for the relevant fields we don't have a conclusive list. Making it configurable sounds like an overkill. *initrd* and *vmlinuz* may make sense, but there are instanes when this is named differently. Since this whole option is for advanced users we can also expect less common file names like vmlinux, bzImage. I would track that separately > 3 - misleading name of of engine-ISO-uploader (it uploads not only ISOs ... > for a > long time now) > > I think only #1 & #2 should be addressed > > Michal please assign to a virt group member. Than open an RFE on the filtering side, and move it to PM for prioritization. see bug 1260666 Verify with: RHEVM:3.6.1.3-0.1.el6 vdsm: vdsm-4.17.13-1.el7ev libvirt: libvirt-1.2.17-13.el7_2.2 Scenario: 1. Upload to ISO domain: vmlinuz and initrd.img of rhel7.2 2. In RunOnce -> Linux Boot Options i can see the the vmlinuz and initrd.img in the drop dowm list. I choose for linux kernel path: vmlinuz and for initrd path: initrd.img i set in kernel param to run from live os: root=live:http://<download tlv>/pub/rhel/released/RHEL-7/7.2/Server/x86_64/os/LiveOS/squashfs.img rd.dm=0 rd.md=0 repo=http://<download tlv>/pub/rhel/released/RHEL-7/7.2/Server/x86_64/os/ The installation started and download the iso,it failed since it does not found: /dev/root see attached screen shot. What are the parameters that is need to put in order to make it work? I don't know and I think this is a RHEL installation/usage problem, not RHEV's (In reply to Michal Skrivanek from comment #18) > I don't know and I think this is a RHEL installation/usage problem, not > RHEV's Moran, there is any reference for this feature that we can learn which parameters should we use? any Documents? an example would be useful? (In reply to Israel Pinto from comment #17) > Verify with: > RHEVM:3.6.1.3-0.1.el6 > vdsm: vdsm-4.17.13-1.el7ev > libvirt: libvirt-1.2.17-13.el7_2.2 > > Scenario: > 1. Upload to ISO domain: vmlinuz and initrd.img of rhel7.2 > 2. In RunOnce -> Linux Boot Options i can see the the vmlinuz and initrd.img > in the drop dowm list. > I choose for linux kernel path: vmlinuz and for initrd path: initrd.img > i set in kernel param to run from live os: > root=live:http://<download > tlv>/pub/rhel/released/RHEL-7/7.2/Server/x86_64/os/LiveOS/squashfs.img > rd.dm=0 rd.md=0 repo=http://<download > tlv>/pub/rhel/released/RHEL-7/7.2/Server/x86_64/os/ > > > The installation started and download the iso,it failed since it does not > found: /dev/root > see attached screen shot. > > What are the parameters that is need to put in order to make it work? Retested with different ISO image and installation worked. PASS Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-0376.html |
1. Proposed title of this feature request Quicker Installs by presenting ISO domain hosted kernel images to Run Once Screen 3. What is the nature and description of the request? a) An ISO domain currnetly does not show any "vmlinuz" or "initrd.img" files on the Storage page. It would be nice to know which kernel images are available without manually searching the NFS/SCSI storage device. b) Once the ISO domain can read those files, it could present them as options from a drop down selector on the Run Once screen. 4. Why does the customer need this? (List the business requirements here) To speed up installations 5. How would the customer like to achieve this? (List the functional requirements here) Unstated 6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. Unstated 7. Is there already an existing RFE upstream or in Red Hat Bugzilla? No 8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? Unstated 9. Is the sales team involved in this request and do they have any additional input? No 10. List any affected packages or components. RHEV-M admin portal and Run Once dialogue boxes 11. Would the customer be able to assist in testing this functionality if implemented? Unstated