Bug 1830917
| Summary: | [IPI][OSP] Install fails on 4.2 when creating volumes for master instances | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | David Sanz <dsanzmor> | |
| Component: | Installer | Assignee: | Martin André <maandre> | |
| Installer sub component: | OpenShift on OpenStack | QA Contact: | David Sanz <dsanzmor> | |
| Status: | CLOSED WONTFIX | Docs Contact: | ||
| Severity: | high | |||
| Priority: | high | CC: | m.andre, pprinett | |
| Version: | 4.2.z | |||
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1836110 (view as bug list) | Environment: | ||
| Last Closed: | 2020-05-28 14:39:45 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1836110 | |||
| Bug Blocks: | ||||
The problem is that in 4.2, the base image is hardcoded to rhcos and BFV won't read the new image name from the OPENSHIFT_INSTALL_OS_IMAGE_OVERRIDE variable. I think it's OK since OPENSHIFT_INSTALL_OS_IMAGE_OVERRIDE is only intended for developers. This request came from QE - they use a shared tenant where they cannot make assumption about an `rhcos` image always pointing at an 4.2 rhcos image. This will allow them to test boot from volume. The team considers this bug as valid. Considering this bug priority and our capacity, we are deferring this bug to an upcoming sprint. If there are reasons for us to reprioritise, please let us know. Fixed in 4.3, we don't plan on backporting. |
Description of problem: Installing 4.2 on OSP using booting from volumes for master has started to fail. Working with latest nightly version: 01:48:58 + ./openshift-install version 01:48:58 ./openshift-install v4.2.32 01:57:18 level=error 01:57:18 level=error msg="Error: Your query returned no results. Please change your search criteria and try again." 01:57:18 level=error 01:57:18 level=error msg=" on ../../../../tmp/openshift-install-844377072/bootstrap/main.tf line 112, in data \"openstack_images_image_v2\" \"bootstrap_image\":" 01:57:18 level=error msg=" 112: data \"openstack_images_image_v2\" \"bootstrap_image\" {" 01:57:18 level=error 01:57:18 level=error 01:57:18 level=error 01:57:18 level=error msg="Error: Your query returned no results. Please change your search criteria and try again." 01:57:18 level=error 01:57:18 level=error msg=" on ../../../../tmp/openshift-install-844377072/masters/main.tf line 1, in data \"openstack_images_image_v2\" \"masters_img\":" 01:57:18 level=error msg=" 1: data \"openstack_images_image_v2\" \"masters_img\" {" 01:57:18 level=error 01:57:18 level=error 01:57:18 level=error msg="Failed to read tfstate: open /tmp/openshift-install-844377072/terraform.tfstate: no such file or directory" 01:57:18 level=fatal msg="failed to fetch Cluster: failed to generate asset \"Cluster\": failed to create cluster: failed to apply using Terraform" Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Install 4.2 using boot from volume features on install-config.yaml file 2. 3. Actual results: Installation fails Expected results: Installation is completed creating volumes for master nodes Additional info: Installation of 4.2 works fine without booting from volume