Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1762216

Summary: [build-cop] terraform packet_device provisioning time limit exceeded
Product: OpenShift Container Platform Reporter: Lukasz Szaszkiewicz <lszaszki>
Component: InstallerAssignee: Scott Dodson <sdodson>
Installer sub component: openshift-installer QA Contact: David Sanz <dsanzmor>
Status: CLOSED DUPLICATE Docs Contact:
Severity: unspecified    
Priority: unspecified    
Version: 4.3.0   
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-11 14:29:33 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:

Description Lukasz Szaszkiewicz 2019-10-16 08:44:52 UTC 
Description of problem: The following jobs https://prow.svc.ci.openshift.org/job-history/origin-ci-test/logs/release-openshift-ocp-installer-e2e-metal-4.3 and https://prow.svc.ci.openshift.org/job-history/origin-ci-test/logs/release-openshift-ocp-installer-e2e-metal-serial-4.3 fail constantly. 

The issue seems to be the inability to provision "packet device". The following error appears in the log frequently (https://ci-search-ci-search-next.svc.ci.openshift.org/?search=provisioning+time+limit+exceeded&maxAge=336h&context=2&type=all)

* packet_device.masters[0]: 1 error(s) occurred:
* packet_device.masters.0: provisioning time limit exceeded; the Packet team will investigate
* module.bootstrap.packet_device.bootstrap: 1 error(s) occurred:
* packet_device.bootstrap: provisioning time limit exceeded; the Packet team will investigate
Terraform does not automatically rollback in the face of errors.
Comment 1 Scott Dodson 2019-10-21 12:41:23 UTC 
CI broke because the images for 4.3 bare metal have changed from 'metal-bios' and 'metal-efi' to 'metal' in data/data/rhcos.json. The PR now looks for 'metal-bios' and if that's not found it looks for 'metal'. This is specific to our CI jobs so I'm not sure how QE would test this other than to look at the job history where it failed continuously early in the installation process, now it fails less frequently and usually because certain e2e tests return negative results.

https://prow.svc.ci.openshift.org/job-history/origin-ci-test/logs/release-openshift-ocp-installer-e2e-metal-4.3
Comment 3 Scott Dodson 2019-12-11 14:29:33 UTC 

*** This bug has been marked as a duplicate of bug 1776011 ***