Skip to content

Conversation

@elmiko
Copy link

@elmiko elmiko commented Nov 12, 2021

This change updates the go.mod and Dockerfiles to use golang 1.17, it
also updates the vendor directory. The vendor directory was updated by
running go mod vendor && go mod tidy && go mod verify.

@pierreprinetti
Copy link
Member

/retest

@mandre
Copy link
Member

mandre commented Nov 15, 2021

Not sure if the openstack-proxy job is supposed to pass. Let's give it another try:
/test e2e-openstack-proxy

@elmiko
Copy link
Author

elmiko commented Nov 16, 2021

update

  • changed golang version in ci-operator.yaml file

This change updates the go.mod, ci-operator.yaml and Dockerfiles to
use golang 1.17, it also updates the vendor directory. The vendor
directory was updated by running
`go mod vendor && go mod tidy && go mod verify`. Also ran `go fmt` to
cleanup the build tags for 1.17.
@elmiko
Copy link
Author

elmiko commented Nov 19, 2021

update

  • ran go fmt on the repo to fix tag issues with 1.17

@openshift-ci
Copy link

openshift-ci bot commented Nov 19, 2021

@elmiko: 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-openstack-proxy e647abc link false /test e2e-openstack-proxy

Full PR test history. Your PR dashboard.

Details

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.

@pierreprinetti pierreprinetti mentioned this pull request Nov 22, 2021
RUN go build -o ./machine-controller-manager ./cmd/manager

FROM registry.ci.openshift.org/origin/4.8:base
FROM registry.ci.openshift.org/openshift/origin-v4.0:base
Copy link
Member

Choose a reason for hiding this comment

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

4.0? Is this intentional, or was it meant to be 4.10?

Copy link
Author

Choose a reason for hiding this comment

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

i tried to make this look like our other community-facing images, see the aws provider for example https://github.com/openshift/cluster-api-provider-aws/blob/master/Dockerfile#L8

my thinking here is that the "Dockerfile" files are for making publicly available images and the "Dockerfile.rhel" is for making the subscription-based images. so i was basically trying to make the community ones look similar, and afaik they all work with that 4.0 base.

Copy link
Member

Choose a reason for hiding this comment

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

oh, ok.

@pierreprinetti
Copy link
Member

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 22, 2021
@openshift-ci
Copy link

openshift-ci bot commented Nov 22, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pierreprinetti

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

The pull request process is described here

Details 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 Nov 22, 2021
@openshift-bot
Copy link

/retest-required

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 2ef68a8 into openshift:master Nov 22, 2021
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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants