Bug 1637185
Summary: | [RHV] ISO provisioning fails with undefined SDK method | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> |
Component: | Providers | Assignee: | Boriso <bodnopoz> |
Status: | CLOSED ERRATA | QA Contact: | Jan Zmeskal <jzmeskal> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 5.9.4 | CC: | bodnopoz, dmetzger, fdewaley, gblomqui, istein, jfrey, jhardy, jprause, mperina, obarenbo, sheda |
Target Milestone: | GA | Keywords: | ZStream |
Target Release: | 5.9.5 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 5.9.5.2 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1613326 | Environment: | |
Last Closed: | 2018-11-05 13:59:40 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | RHEVM | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1613326 | ||
Bug Blocks: |
Comment 2
Boriso
2018-10-11 13:23:26 UTC
New commits detected on ManageIQ/manageiq-providers-ovirt/gaprindashvili: https://github.com/ManageIQ/manageiq-providers-ovirt/commit/dadbea59d0bf5cd473051548ddda12a4195a695e commit dadbea59d0bf5cd473051548ddda12a4195a695e Author: Piotr Kliczewski <piotr.kliczewski> AuthorDate: Mon Oct 8 10:13:46 2018 -0400 Commit: Piotr Kliczewski <piotr.kliczewski> CommitDate: Mon Oct 8 10:13:46 2018 -0400 Merge pull request #296 from borod108/bugs/1613326iso_prov Fix ISO provisioning with kickstart (cherry picked from commit 9d27961b57a542a3259984fdd436d0a25c187435) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1637185 app/models/manageiq/providers/redhat/infra_manager/ovirt_services/strategies/v4.rb | 10 + spec/models/manageiq/providers/redhat/infra_manager/provision/configuration_spec.rb | 39 +- 2 files changed, 44 insertions(+), 5 deletions(-) https://github.com/ManageIQ/manageiq-providers-ovirt/commit/cc975a02f4e985772f13d8db24000fd797f0fe8b commit cc975a02f4e985772f13d8db24000fd797f0fe8b Author: Piotr Kliczewski <piotr.kliczewski> AuthorDate: Wed Oct 10 10:42:36 2018 -0400 Commit: Piotr Kliczewski <piotr.kliczewski> CommitDate: Wed Oct 10 10:42:36 2018 -0400 Merge pull request #298 from borod108/bugs/1613326iso_prov_2 Fix attach_floppy to pass "floppy" type (cherry picked from commit db724df0af9fe3e9dd8fbb136807c2967cbc3cbd) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1637185 app/models/manageiq/providers/redhat/infra_manager/ovirt_services/strategies/v4.rb | 2 +- spec/models/manageiq/providers/redhat/infra_manager/provision/configuration_spec.rb | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) So I tried to verify that this bug has been fixed. All the logs and other materials I refer to here can be found in attached archive called "Verification materials". So, firstly, my setup: - I tried to provision a RHEL7.5 server ISO image. - I modified this image in two ways: a) In the root of directory structure, I put file called ks.cfg. You can find its contents in attached file ks.cfg.b) I added "inst.ks=cdrom" to all append lines in isolinux/isolinux.cfg. - For provisioning, I used customization template that can be found in customization_template.txt. This KS script was generated by anaconda during my previous manual installation of RHEL7.5 and I also verified its sanity with ksvalidator. - In Schedule tab I made sure that the VM is not scheduled to power on after provision. The outcome: 1) The original problem (undefined SDK method) is not present anymore. 2) The ISO provisioning however still does not seem to be working. The provisioning request gets stuck on this: [EVM] VM [test_vmix65eg] Step [CheckProvisioned] Status [Creating VM] Message [Waiting for provider PowerOff of Vm id: [70], name: [test_vmix65eg]] Current Retry Number [19] VM is stuck during boot. In the attached screenshot, you can see the error that is thrown there. Follow-up: I think we can verify that the original bug does not affect the product anymore. According to e-mail conversation with Boris, Martin, Ilanit and others, it seems that the current problem might actually by located in RHV. However, before I move this to VERIFIED, I think it would be a very good idea to reference the new bug here. Boris, please, do we have one? 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://access.redhat.com/errata/RHSA-2018:3466 |