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

Bump K8s.io version to v0.19.0 #4266

Merged
merged 4 commits into from Oct 15, 2020

Conversation

nirarg
Copy link
Contributor

@nirarg nirarg commented Oct 13, 2020

No description provided.

* Bump k8s.io modules version to v0.19.0
* Change machine-config-operator to latest master
* Move from k8s.io/klog to k8s.io/klog/v2
@nirarg
Copy link
Contributor Author

nirarg commented Oct 13, 2020

/test e2e-crc

.gitignore Outdated
Comment on lines 2 to 3
*.swp
*dev.log
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think the installer repo needs to add user-specific files to git ignore.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I agree about the dev.log, will drop it
Regarding the *.swp, this is temporary file used by the vi/vim editor and might be accidentally added to commits. as this type file never should be added, isn't it good enough reason to add it (and maybe also other editor's specific files)

Copy link
Contributor

Choose a reason for hiding this comment

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

I think people should use https://stackoverflow.com/a/1753078 to add any editor ignore files. Forcing repos to include ignore files for all editors is too much of a slippery slope imo, so i would personally not add anything here.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks @abhinavdahiya
I removed this change

Comment on lines 14 to 15
"k8s.io/klog"
klogv2 "k8s.io/klog/v2"
Copy link
Contributor

Choose a reason for hiding this comment

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

so the vendor update doesn't reflect that klog was dropped or not used anymore by anyone.

so how can we ensure no logs end up into stderr from both versions

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I can use here both klog versions, do you think this is better approach?

Copy link
Contributor

Choose a reason for hiding this comment

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

I can use here both klog versions, do you think this is better approach?

i think that would be safer for now.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks @abhinavdahiya
I changed it, please review

@nirarg
Copy link
Contributor Author

nirarg commented Oct 13, 2020

/test e2e-ovirt

@nirarg
Copy link
Contributor Author

nirarg commented Oct 13, 2020

/test e2e-metal-ipi

@nirarg
Copy link
Contributor Author

nirarg commented Oct 14, 2020

/test e2e-ovirt
/test e2e-aws-fips
/test e2e-aws

@nirarg
Copy link
Contributor Author

nirarg commented Oct 14, 2020

/test e2e-aws
/test e2e-aws-fips
/test e2e-metal-ipi
/test e2e-crc
/test e2e-libvirt

@openshift-ci-robot
Copy link
Contributor

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

Test name Commit Details Rerun command
ci/prow/e2e-aws-workers-rhel7 6f6c7b7 link /test e2e-aws-workers-rhel7
ci/prow/e2e-openstack 6f6c7b7 link /test e2e-openstack
ci/prow/e2e-aws-fips 6f6c7b7 link /test e2e-aws-fips
ci/prow/e2e-aws 6f6c7b7 link /test e2e-aws
ci/prow/e2e-libvirt 6f6c7b7 link /test e2e-libvirt
ci/prow/e2e-crc 6f6c7b7 link /test e2e-crc
ci/prow/e2e-metal-ipi 6f6c7b7 link /test e2e-metal-ipi
ci/prow/e2e-ovirt 6f6c7b7 link /test e2e-ovirt

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.

@@ -28,8 +29,10 @@ func main() {
// to log anything.
var fs flag.FlagSet
klog.InitFlags(&fs)
klogv2.InitFlags(&fs)
Copy link
Contributor

Choose a reason for hiding this comment

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

@abhinavdahiya
Copy link
Contributor

/approve
/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 15, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya

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 Oct 15, 2020
@openshift-bot
Copy link
Contributor

/retest

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

6 similar comments
@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-bot
Copy link
Contributor

/retest

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

@openshift-merge-robot
Copy link
Contributor

openshift-merge-robot commented Oct 15, 2020

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

Test name Commit Details Rerun command
ci/prow/e2e-libvirt 7055e9b link /test e2e-libvirt
ci/prow/e2e-crc 7055e9b link /test e2e-crc

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.

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.

None yet

5 participants