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

Pin ironic version #93

Closed
wants to merge 1 commit into from
Closed

Conversation

elfosardo
Copy link

@elfosardo elfosardo commented Jul 24, 2020

This should grant some control on what we're installing.

@elfosardo elfosardo marked this pull request as draft July 24, 2020 09:34
@openshift-ci-robot openshift-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 24, 2020
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elfosardo

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-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 24, 2020
This should grant some control on what we're installing.
@elfosardo elfosardo marked this pull request as ready for review July 27, 2020 09:24
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 27, 2020
Copy link
Member

@dtantsur dtantsur left a comment

Choose a reason for hiding this comment

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

I'm not sure how I feel about this.. It means that we need to bump the version every time a bug fix is released?

@openshift-ci-robot
Copy link

@elfosardo: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-metal-ipi 0820b04 link /test e2e-metal-ipi

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.

@elfosardo
Copy link
Author

I'm not sure how I feel about this.. It means that we need to bump the version every time a bug fix is released?

every time a bug fix is released, we need to tag a different package anyway
this adds one more level of control directly on the image
I'm more worried about the integration between the different images to be honest, I did this PR to be able to run CI whenever we want to update a package, so update it in an explicit way instead of the silent cross-tag, but of course it has limitations.
Ideas welcome

Copy link

@juliakreger juliakreger left a comment

Choose a reason for hiding this comment

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

I don't like it... but I see the plus side

If we specify the version, then the container build breaks hard if the mirror becomes invalid, or someone tries to make changes outside of the pipeline.

The downside is equally problematic. We have to manually touch each repo should there be a minor security issue in ironic instead of allowing it to get pulled in upon rebuild.

I guess I just have super mixed feelings on this.

@elfosardo
Copy link
Author

this won't work as the repos are built using only the latest tagged package, so we incur in an issue where the build will start failing if we don't change the version, basically nullifying the reason of this PR

@elfosardo elfosardo closed this Jul 28, 2020
andfasano pushed a commit to andfasano/ironic-image that referenced this pull request Nov 18, 2020
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants