Closed mike-nguyen closed 1 month ago
@mike-nguyen: This pull request references COS-2769 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.17.0" version, but no target version was set.
/hold until ART plashet gets added to internal repos. Reviews welcomed still.
There are a few more places that need to be updated. Try a git grep 4\\.16
.
There are a few more places that need to be updated. Try a
git grep 4\\.16
.
Thanks there were a lot more! I will update the branching doc with this PR as a reference.
/hold cancel ART repos are are added and merged.
/retest
/approve /lgtm
/retest-required
Remaining retests: 0 against base HEAD 8e6ac83347763adc87103b48596eb4bd8f42cb72 and 2 for PR HEAD 55abc92addd41a80aa3ffce712ca5cdd067f344c in total
/retest-required
Remaining retests: 0 against base HEAD 353d297e733c75a9269c06652c6c9a9bbd5cb395 and 1 for PR HEAD 55abc92addd41a80aa3ffce712ca5cdd067f344c in total
rpm-md repo 'rhel-9.4-baseos'; generated: 2024-05-02T07:02:38Z solvables: 0 rpm-md repo 'rhel-9.4-appstream'; generated: 2024-05-02T07:16:36Z solvables: 0
Huh, the repos are empty. Ahh, I think we need https://github.com/openshift/release/pull/52325 at least.
/retest
there are rhaos packages are old in the ART plashet causing kola test failures
Also seeing this in the prow/validate job which I've never seen before. Did something change or is something more strict than before?
+ git clone /go/src/github.com/openshift/os os
Cloning into 'os'...
fatal: detected dubious ownership in repository at '/go/src/github.com/openshift/os/.git'
To add an exception for this directory, call:
git config --global --add safe.directory /go/src/github.com/openshift/os/.git
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
{"component":"entrypoint","error":"wrapped process failed: exit status 128","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:84","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2024-05-22T01:06:47Z"}
[36mINFO[0m[2024-05-22T01:06:49Z] Ran for 2m56s
[31mERRO[0m[2024-05-22T01:06:49Z] Some steps failed:
[31mERRO[0m[2024-05-22T01:06:49Z]
* could not run steps: step validate failed: test "validate" failed: could not watch pod: the pod ci-op-7tttzwgt/validate failed after 52s (failed containers: test): ContainerFailed one or more containers exited
Container test exited with code 128, reason Error
Do you have a ticket already for the rebuilds necessary? We could also temporarily denylist it.
Also seeing this in the prow/validate job which I've never seen before. Did something change or is something more strict than before?
Added another commit for that one!
Do you have a ticket already for the rebuilds necessary? We could also temporarily denylist it.
Also seeing this in the prow/validate job which I've never seen before. Did something change or is something more strict than before?
Added another commit for that one!
@haircommander helped us by building conmon and cri-o with the correct brew tags. We are still waiting for conmon-rs which is usually built by @jnovy
/retest
The cri-o rebuild is blocked on RHEL-35883. We may need to skip the test for now.
Running test: iso-offline-install.bios
FAIL: iso-offline-install.bios (10m0.002s)
timed out after 10m0s
Running test: iso-offline-install.mpath.bios
FAIL: iso-offline-install.mpath.bios (10m0.004s)
timed out after 10m0s
Running test: iso-offline-install-fromram.4k.uefi
FAIL: iso-offline-install-fromram.4k.uefi (10m0.001s)
timed out after 10m0s
Running test: miniso-install.bios
FAIL: miniso-install.bios (10m0.002s)
timed out after 10m0s
Running test: miniso-install.nm.bios
FAIL: miniso-install.nm.bios (10m0.007s)
timed out after 10m0s
Running test: miniso-install.4k.uefi
FAIL: miniso-install.4k.uefi (10m0s)
timed out after 10m0s
Running test: miniso-install.4k.nm.uefi
FAIL: miniso-install.4k.nm.uefi (10m0.001s)
timed out after 10m0s
Running test: pxe-offline-install.bios
FAIL: pxe-offline-install.bios (10m0s)
timed out after 10m0s
Running test: pxe-offline-install.4k.uefi
FAIL: pxe-offline-install.4k.uefi (10m0.002s)
timed out after 10m0s
Running test: pxe-online-install.bios
FAIL: pxe-online-install.bios (10m0.005s)
timed out after 10m0s
Running test: pxe-online-install.4k.uefi
FAIL: pxe-online-install.4k.uefi (10m0.008s)
timed out after 10m0s
Error: harness: test suite failed
Hum, why is SCOS running the UEFI tests? 🤔
Edit: Nevermind, it's EFI only, not Secure Boot.
/hold
/retest
/retest
Updated this now to pin selinux-policy due to https://github.com/openshift/os/issues/1514.
/hold cancel
/retest
@mike-nguyen: all tests passed!
Full PR test history. Your PR dashboard.
/lgtm jonathan's changes
And Mike's changes /lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jlebon, mike-nguyen, travier
The full list of commands accepted by this bot can be found here.
The pull request process is described here
4.16 branched so bump the version in main development to 4.17.