[USHIFT-2971] EL94 Periodics
/test metal-periodic-test
/retest
/test metal-periodic-test
/retest
Failed during infra deployment
@pmtk The current release version has shifted to 4.17 but there are no ec's/rc's available yet. This causes the edge commits for crel builds to be skipped, resulting in the scenarios which expect these commits to fail during the vm creation. Instead of deleting the scenarios (which we'll need in the near future) I've added the extension .pending_crel to the filenames. This should exempt them from the ci boot phase. If this works, I'll create a ticket to remind us to reenable them once 4.17 is available.
The logic I'm abusing here is this line: https://github.com/openshift/microshift/blob/42e8f09731d51273384d19f97eacdb4c389e2f1e/test/bin/ci_phase_iso_boot.sh#L33
*Obviously we need to make the scripts a little smarter about handling this situation.
The images built and booted, but for some reason the cos9 scenarios never installed microshift.
cos9-src@rpm-standard{1,2}.sh scenarios are also affected by the 4.17 rpms not being available yet, so these will also need to be disabled temporarily
Infra failures prevented the metal host from starting
/retest
- microshift-metal-periodic test failed due to aws infra issue.
- microshift-metal-test failed due to curl timeout. The error should not have been fatal but the RF logic only checks for the string
errorin the rpm install output. Install actually succeeded - microshift-metal-tests-arm failed during OS install when it timed out while trying to download a dependency from the local repo:
[ 190.440070] anaconda[2595]: Failed to pull from repository: g-io-error-quark: While fetching http://192.168.
[ 190.440746] anaconda[2595]: 122.1:8080/repo/objects/59/1a8d6991f9804a1674cf7cb8d9a8be39dcbc65281bc00f8c527e7
[ 190.441431] anaconda[2595]: b43a296cf.filez: [28] Timeout was reached (0)
/retest
More infra failures, will try again tomorrow
/retest
Infra failure
/test metal-periodic-test
/lgtm
/test metal-periodic-test
We need the https://github.com/openshift/microshift/pull/3415 PR to merge before we can get a successful run. These amount of VMs seems to be too heavy for the default nginx config.
/retest-required
Remaining retests: 0 against base HEAD d9ed4258fd388e28297cc989d187ea84e7b9649e and 2 for PR HEAD 3d82dafbba8060b2bb4929791a2898ab914294a9 in total
/retest-required
Remaining retests: 0 against base HEAD e368f305874f634715834b42de06104dc9d0766d and 1 for PR HEAD 3d82dafbba8060b2bb4929791a2898ab914294a9 in total
el93 OS installation has consistently failed with the following:
[ 132.686196] anaconda[2622]: Failed to pull from repository: g-io-error-quark: While fetching http://192.168.
[ 132.686289] anaconda[2622]: 122.1:8080/repo/objects/1e/a4dd1d5fe17f4b061e40837e14c58f923e8750fabeba6d9955f9b
[ 132.686374] anaconda[2622]: 6b06f8b51.filez: [28] Timeout was reached (0)
/retest-required
Remaining retests: 0 against base HEAD 0f9c968f32178179fab77673aa07c145526c0ebe and 0 for PR HEAD 3d82dafbba8060b2bb4929791a2898ab914294a9 in total
/retest-required
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: copejon, ggiguash
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [copejon,ggiguash]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/retest-required
Remaining retests: 0 against base HEAD 1363db4ff49d099b4fb5d572f9e11bc3f9cfbc8e and 2 for PR HEAD 93d60901f86a024d1831dfd5a46d9b233bc2a37a in total
/test metal-periodic-test-arm
/test metal-periodic-test-arm
/retest-required
@copejon: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/metal-bootc-test-arm | fd0464c09b94ab78df334859bddb6ceab73b7091 | link | true | /test metal-bootc-test-arm |
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.
/test metal-bootc-test metal-periodic-test-arm
/override ci/prow/metal-bootc-test