[release-4.16] USHIFT-3503: Properly apply greenboot timeout increase in blueprints and container files

[ggiguash]

Manual cherry-pick of the following PRs:

• USHIFT-3503: Properly apply greenboot timeout increase in blueprints and container files #3615
• NO-ISSUE: Move upgrade tests back to periodics #3616
• NO-ISSUE: Fix common versions script not to produce errors for non-existent repos #3627

[openshift-ci-robot]

@ggiguash: This pull request references USHIFT-3503 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.z" version, but no target version was set.

In response to this:

Manual cherry-pick of the following PRs:

• USHIFT-3503: Properly apply greenboot timeout increase in blueprints and container files #3615
• NO-ISSUE: Move upgrade tests back to periodics #3616
• NO-ISSUE: Fix common versions script not to produce errors for non-existent repos #3627

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[ggiguash]

/test ?

[openshift-ci]

@ggiguash: The following commands are available to trigger required jobs:

• /test images
• /test metal-periodic-test
• /test metal-periodic-test-arm
• /test microshift-metal-cache
• /test microshift-metal-cache-arm
• /test microshift-metal-tests
• /test microshift-metal-tests-arm
• /test ocp-conformance-rhel-eus
• /test ocp-conformance-rhel-eus-arm
• /test ocp-full-conformance-rhel-eus
• /test test-rpm
• /test test-unit
• /test verify

The following commands are available to trigger optional jobs:

• /test test-rebase

Use /test all to run the following jobs that were automatically triggered:

• pull-ci-openshift-microshift-release-4.16-images
• pull-ci-openshift-microshift-release-4.16-metal-periodic-test
• pull-ci-openshift-microshift-release-4.16-metal-periodic-test-arm
• pull-ci-openshift-microshift-release-4.16-microshift-metal-tests
• pull-ci-openshift-microshift-release-4.16-microshift-metal-tests-arm
• pull-ci-openshift-microshift-release-4.16-test-unit
• pull-ci-openshift-microshift-release-4.16-verify

In response to this:

/test ?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ggiguash]

/test microshift-metal-cache
/test microshift-metal-cache-arm

[ggiguash]

/test verify

[ggiguash]

/test microshift-metal-tests
/test microshift-metal-tests-arm

[pmtk]

/lgtm

[ggiguash]

/test metal-periodic-test-arm

[ggiguash]

/test metal-periodic-test-arm

[ggiguash]

/label backport-risk-assessed
/label jira/valid-issue

[openshift-ci]

@ggiguash: The label(s) /label jira/valid-issue cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, approved, backport-risk-assessed, bugzilla/invalid-bug, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/label backport-risk-assessed
/label jira/valid-issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ggiguash]

/label jira/valid-bug

[pmtk]

/retest

[ggiguash]

/label cherry-pick-approved
/retest-required

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 0afcb57 and 2 for PR HEAD 62e820b in total

[pmtk]

/test metal-periodic-test-arm

[ggiguash]

/hold

We seem to have rather consistent failure on ARM when retrying VM creation. The termination of a running VM does not work and scenario.sh script exits with errors.

[   86.154793] anaconda[2594]: Installing software 81%
[  344.425743] anaconda[2594]: Installing software 80%
[  440.111364] anaconda[2594]: Installing software 79%
timeout: sending signal TERM to command ‘unbuffer’
+ 11:56:45.306993509 ./bin/scenario.sh:523 	(( attempt++ ))
+ 11:56:45.308210751 ./bin/scenario.sh:524 	'[' 2 -gt 2 ']'
+ 11:56:45.309281184 ./bin/scenario.sh:530 	local backoff=10
+ 11:56:45.310359466 ./bin/scenario.sh:531 	echo 'Error running virt-install: retrying in 10s on attempt 2'
Error running virt-install: retrying in 10s on attempt 2
+ 11:56:45.311466796 ./bin/scenario.sh:532 	sleep 10
+ 11:56:55.314052920 ./bin/scenario.sh:536 	remove_vm host1 true
+ 11:56:55.315174198 ./bin/scenario.sh:609 	local -r vmname=host1
+ 11:56:55.316613498 ./bin/scenario.sh:610 	local -r keep_pool=true
++ 11:56:55.317941215 ./bin/scenario.sh:611 	full_vm_name host1
++ 11:56:55.319027706 ./bin/scenario.sh:36 	local base=host1
++ 11:56:55.320086808 ./bin/scenario.sh:37 	echo el94-src-rpm-standard1-host1
+ 11:56:55.321308729 ./bin/scenario.sh:611 	local -r full_vmname=el94-src-rpm-standard1-host1
+ 11:56:55.322331828 ./bin/scenario.sh:614 	sudo virsh dumpxml el94-src-rpm-standard1-host1
+ 11:56:55.347730802 ./bin/scenario.sh:615 	sudo virsh dominfo el94-src-rpm-standard1-host1
+ 11:56:55.347796090 ./bin/scenario.sh:615 	grep '^State'
+ 11:56:55.347946290 ./bin/scenario.sh:615 	grep -q 'shut off'
+ 11:56:55.369724408 ./bin/scenario.sh:616 	sudo virsh destroy el94-src-rpm-standard1-host1
error: Failed to destroy domain 'el94-src-rpm-standard1-host1'
error: Failed to terminate process 897099 with SIGKILL: Device or resource busy

+ 11:57:35.404261921 ./bin/scenario.sh:1 	rc=1
+ 11:57:35.405594618 ./bin/scenario.sh:2 	'[' 1 -ne 0 ']'
+ 11:57:35.406903338 ./bin/scenario.sh:2 	record_junit setup scenario_create_vms FAILED

[ggiguash]

/test metal-periodic-test-arm

[ggiguash]

/unhold

[ggiguash]

/test all

[ggiguash]

/test microshift-metal-tests-arm

[pmtk]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pmtk

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ggiguash,pmtk]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@ggiguash: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.