-
Notifications
You must be signed in to change notification settings - Fork 40
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
Conversation
[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 |
This should grant some control on what we're installing.
There was a problem hiding this 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?
@elfosardo: The following test failed, say
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. |
every time a bug fix is released, we need to tag a different package anyway |
There was a problem hiding this 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.
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 |
Move to Train branch
This should grant some control on what we're installing.