Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MGMT-18965: Update docker files to use universal base image #905

Open
wants to merge 1 commit into
base: release-4.16
Choose a base branch
from

Conversation

paul-maidment
Copy link
Contributor

This updates the docker files of this project to use the universal base image

This updates the docker files of this project to use the universal base image
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 19, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 19, 2024

@paul-maidment: This pull request references MGMT-18965 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 task to target the "4.16.z" version, but no target version was set.

In response to this:

This updates the docker files of this project to use the universal base image

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 openshift-ci bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Sep 19, 2024
@paul-maidment
Copy link
Contributor Author

/test ?

Copy link

openshift-ci bot commented Sep 19, 2024

@paul-maidment: The following commands are available to trigger required jobs:

  • /test e2e-agent-compact-ipv4
  • /test images

The following commands are available to trigger optional jobs:

  • /test e2e-agent-ha-dualstack
  • /test e2e-agent-sno-ipv6
  • /test okd-scos-images

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

  • pull-ci-openshift-assisted-installer-release-4.16-e2e-agent-compact-ipv4
  • pull-ci-openshift-assisted-installer-release-4.16-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-sigs/prow repository.

@openshift-ci openshift-ci bot added the downstream-change-needed Requires updating downstream image label Sep 19, 2024
Copy link

openshift-ci bot commented Sep 19, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: paul-maidment

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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 19, 2024
@paul-maidment
Copy link
Contributor Author

/test e2e-agent-compact-ipv4

1 similar comment
@paul-maidment
Copy link
Contributor Author

/test e2e-agent-compact-ipv4

Copy link

openshift-ci bot commented Sep 20, 2024

@paul-maidment: 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/e2e-agent-compact-ipv4 00cdffd link true /test e2e-agent-compact-ipv4

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.

ARG TARGETPLATFORM
ENV GOFLAGS=-mod=mod
WORKDIR /go/src/github.com/openshift/assisted-installer

# Workaround for creating build folder
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why using a workaround when we can use this image the way it's meant to?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@danmanor
Copy link
Contributor

@paul-maidment Can you explain the reasoning for this branch ?

@paul-maidment
Copy link
Contributor Author

paul-maidment commented Sep 22, 2024

@paul-maidment Can you explain the reasoning for this branch ?

The 4.16 branch is broken unless we do something, try running

skipper make build on it

I think moving to UBI would be the correct course of action, consistent with what we did on master to fix the same issue?

Were some backports were missed at the time?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. downstream-change-needed Requires updating downstream image jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants