assisted-installer
assisted-installer copied to clipboard
NO-ISSUE: make dockerfile multi-arch compatible
cli image is not multiarch security scans need rpm to validate oc binaries
@rccrdpccl: This pull request explicitly references no jira issue.
In response to this:
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/test-infra repository.
/cc @adriengentil
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rccrdpccl
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [rccrdpccl]
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 56.33%. Comparing base (
f1bb876
) to head (2708f52
). Report is 41 commits behind head on master.
/test ?
@adriengentil: The following commands are available to trigger required jobs:
-
/test e2e-agent-compact-ipv4
-
/test edge-e2e-ai-operator-ztp
-
/test edge-e2e-metal-assisted
-
/test edge-format-check
-
/test edge-images
-
/test edge-lint
-
/test edge-unit-test
-
/test images
-
/test mce-images
The following commands are available to trigger optional jobs:
-
/test e2e-agent-ha-dualstack
-
/test e2e-agent-sno-ipv6
-
/test edge-e2e-metal-assisted-cnv
-
/test edge-e2e-metal-assisted-ipv6
-
/test edge-e2e-metal-assisted-lvm
-
/test edge-e2e-metal-assisted-odf
-
/test edge-e2e-metal-assisted-single-node
-
/test edge-e2e-oci-assisted
-
/test edge-e2e-oci-assisted-4-14
-
/test edge-publish-multi-arch-images-dry-run
Use /test all
to run the following jobs that were automatically triggered:
-
pull-ci-openshift-assisted-installer-master-e2e-agent-compact-ipv4
-
pull-ci-openshift-assisted-installer-master-edge-e2e-ai-operator-ztp
-
pull-ci-openshift-assisted-installer-master-edge-e2e-metal-assisted
-
pull-ci-openshift-assisted-installer-master-edge-format-check
-
pull-ci-openshift-assisted-installer-master-edge-images
-
pull-ci-openshift-assisted-installer-master-edge-lint
-
pull-ci-openshift-assisted-installer-master-edge-unit-test
-
pull-ci-openshift-assisted-installer-master-images
-
pull-ci-openshift-assisted-installer-master-mce-images
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/test-infra repository.
/test edge-publish-multi-arch-images-dry-run
let's use registry.ci.openshift.org/openshift/release:golang-1.20
for the moment, and open a ticket to move to registry.access.redhat.com/ubi9/go-toolset
here and in the other repos?
@rccrdpccl what did we decide to do here?
sorry, I've totally lost track of this, I've created https://issues.redhat.com/browse/MGMT-16720 to keep track of it, will have a look soon because I totally forgot why I was doing this :sweat:
in the meantime... /retest
Status code: 404 for https://mirror.openshift.com/pub/openshift-v4/s390x/dependencies/rpms/4.15-el8-beta/repodata/repomd.xml (IP: 18.67.76.28)
/retest
@rccrdpccl: 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/edge-publish-multi-arch-images-dry-run | 2708f5282efc3ee540fb822a5888c99291bd85f8 | link | false | /test edge-publish-multi-arch-images-dry-run |
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/test-infra repository. I understand the commands that are listed here.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
@rccrdpccl How is this one going ? we have a perma-failing CI job that tries to build multi-arch images.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen
.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Exclude this issue from closing again by commenting /lifecycle frozen
.
/close
PR needs rebase.
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.
@openshift-bot: Closed this PR.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen
. Mark the issue as fresh by commenting/remove-lifecycle rotten
. Exclude this issue from closing again by commenting/lifecycle frozen
./close
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.