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

UPSTREAM: 52324: Fix bug on kubelet failure to umount mount points. #18225

Merged
merged 1 commit into from
Jan 31, 2018

Conversation

humblec
Copy link
Contributor

@humblec humblec commented Jan 23, 2018

Signed-off-by: Humble Chirammal [email protected]

@openshift-merge-robot openshift-merge-robot added the vendor-update Touching vendor dir or related files label Jan 23, 2018
@openshift-ci-robot openshift-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 23, 2018
@humblec
Copy link
Contributor Author

humblec commented Jan 23, 2018

/assign @jsafrane

@humblec
Copy link
Contributor Author

humblec commented Jan 23, 2018

/retest

@jsafrane
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 23, 2018
@openshift-bot
Copy link
Contributor

/retest

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

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

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

@humblec
Copy link
Contributor Author

humblec commented Jan 24, 2018

I havent updated the bazel inside the vendor directory, not sure is that causing unit test to fail.

@openshift-bot
Copy link
Contributor

/retest

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

4 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.

// util.go uses api.Codecs.LegacyCodec so import this package to do some
// resource initialization.
_ "k8s.io/kubernetes/pkg/apis/core/install"
"k8s.io/kubernetes/pkg/apis/core/v1/helper"
"k8s.io/kubernetes/vendor/k8s.io/kubernetes/pkg/util/mount"
Copy link
Contributor

Choose a reason for hiding this comment

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

you should not import vendor packages.

can't load package: package k8s.io/kubernetes/vendor/k8s.io/kubernetes/pkg/util/mount: cannot find package "k8s.io/kubernetes/vendor/k8s.io/kubernetes/pkg/util/mount" in any of:
	/usr/local/go/src/k8s.io/kubernetes/vendor/k8s.io/kubernetes/pkg/util/mount (from $GOROOT)
	/go/src/github.com/openshift/origin/_output/local/go/src/k8s.io/kubernetes/vendor/k8s.io/kubernetes/pkg/util/mount (from $GOPATH)

@openshift-bot
Copy link
Contributor

/retest

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

4 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-merge-robot openshift-merge-robot removed the lgtm Indicates that a PR is ready to be merged. label Jan 29, 2018
@humblec
Copy link
Contributor Author

humblec commented Jan 29, 2018

Thanks @jsafrane . All tests are green now :).

@jsafrane
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 30, 2018
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: humblec, jsafrane

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

Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@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

/test all [submit-queue is verifying that this PR is safe to merge]

@openshift-ci-robot
Copy link

@humblec: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/openshift-jenkins/extended_conformance_install 0727d1d link /test extended_conformance_install

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

@openshift-merge-robot
Copy link
Contributor

Automatic merge from submit-queue (batch tested with PRs 18225, 18351, 18331, 18340, 18326).

@openshift-merge-robot openshift-merge-robot merged commit f2b1e42 into openshift:master Jan 31, 2018
@DanyC97
Copy link
Contributor

DanyC97 commented Mar 7, 2018

@humblec any chance this can be merged in 3.7 origin too ? otherwise everyone using Origin 3.7 is ... stuck

@jarrpa fyi which came as result of https://bugzilla.redhat.com/show_bug.cgi?id=1489082

We on 3.7 origin hitting it everytime now and honestly is a NO-GO for prod

@humblec
Copy link
Contributor Author

humblec commented May 8, 2018

@DanyC97 this is fixed in OCP 3.7 some time back, so if you are running latest OCP 3.7 version you should not hit this issue.

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. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants