Glide update error

[xianlubird]

I want to upgrade k8s vendor to a newer version. I change github.com/openshift/origin version from v1.4.0-rc1 to v3.9.0, then run glide update --strip-vendor. There're many errors message

[ERROR]	Error looking for k8s.io/api/apps/v1beta1: Unable to get repository: Cloning into '/root/.glide/cache/src/git-git.luolix.top-openshift-kubernetes-api'...
[ERROR]	Error scanning k8s.io/api/autoscaling/v1: cannot find package "." in:
	/root/.glide/cache/src/git-git.luolix.top-openshift-kubernetes-api/autoscaling/v1
[ERROR]	Error scanning k8s.io/api/batch/v1: cannot find package "." in:
	/root/.glide/cache/src/git-git.luolix.top-openshift-kubernetes-api/batch/v1
[ERROR]	Error scanning k8s.io/api/batch/v1beta1: cannot find package "." in:
	/root/.glide/cache/src/git-git.luolix.top-openshift-kubernetes-api/batch/v1beta1
[ERROR]	Error scanning k8s.io/api/batch/v2alpha1: cannot find package "." in:
	/root/.glide/cache/src/git-git.luolix.top-openshift-kubernetes-api/batch/v2alpha1
[ERROR]	Error scanning k8s.io/api/core/v1: cannot find package "." in:
	/root/.glide/cache/src/git-git.luolix.top-openshift-kubernetes-api/core/v1

So I can't upgrade k8s vendor to a newer version. I find a issue redhat-developer/odo#377, when I clean all glide cache and vendor folder, it always show above error message.

@cdrage @hangyan Do you have some suggestion about this ? Need help.

[kadel]

Vendoring for newer versions of Kubernetes and OpenShift can can a bit tricky :-(

We already hit this problem in Kedge and we had to write special script to handle OpenShift vendoring vendor-openshift.sh. See comments in glide.yaml.

But there is another solution for this. Kompose still imports stuff from k8s.io/kubernetes and from github.com/openshift/origin. But it should be possible to replace it with k8s.io/client-go and github.com/openshif/client-go, it is not going to be easy but it will make vendoring straingforward and it will be much easier to update to new versions.

[hangyan]

Good idea!

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[cdrage]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.