-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
Check CentOS-Base.repo exists for CentOS 7 #11402
Conversation
@tico88612 PTAL:-) |
Signed-off-by: tu1h <[email protected]>
5976094
to
351832b
Compare
/ok-to-test |
Thanks @tu1h |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tu1h, yankay 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 |
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.
/lgtm
thanks
/retest |
HI @tu1h |
/cherry-pick release-2.25 |
@tico88612: new pull request created: #11438 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-sigs/prow repository. |
/cherry-pick release-2.24 |
@tico88612: new pull request created: #11546 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-sigs/prow repository. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
It's should check the existence of the
CentOS-Base.repo
before we make changes with it. Because we cannot assume the system is clean enough, and the files in/etc/yum.repos.d
may be changed already.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: