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

1.6 post-rebase tasks #13732

Closed
14 of 32 tasks
sttts opened this issue Apr 12, 2017 · 10 comments
Closed
14 of 32 tasks

1.6 post-rebase tasks #13732

sttts opened this issue Apr 12, 2017 · 10 comments
Assignees
Labels
area/techdebt kind/post-rebase lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P1
Milestone

Comments

@sttts
Copy link
Contributor

sttts commented Apr 12, 2017

Blockers:

 --- FAIL: TestEtcd2StoragePath (34.55s)
        etcd_storage_path_test.go:960: failed to create stub for Pod from github.com/openshift/origin/vendor/k8s.io/kubernetes/pkg/api/v1:
n:""}, Status:"Failure", Message:"pods \"pod1\" is forbidden: service account etcdstoragepathtestnamespace/default was not found, retry af
        etcd_storage_path_test.go:960: failed to create stub for PolicyBinding from github.com/openshift/origin/pkg/authorization/api/v1:
:""}, Status:"Failure", Message:"policybindings.authorization.openshift.io \":default\" already exists", Reason:"AlreadyExists", Details:(
        etcd_storage_path_test.go:960: failed to create stub for Policy from github.com/openshift/origin/pkg/authorization/api/v1: &errors
tatus:"Failure", Message:"policies.authorization.openshift.io \"default\" already exists", Reason:"AlreadyExists", Details:(*v1.StatusDeta
        etcd.go:126: dumping etcd to "/tmp/openshift/test-integration/etcd-dump-TestEtcd2StoragePath.json"

Further work:

@mfojtik
Copy link
Contributor

mfojtik commented Jun 27, 2017

@sttts @enj @deads2k @smarterclayton for the kube alpha API's i found that we already have a way to disabled them: kubernetesMasterConfig.disabledAPIGroupVersions. I don't think we want to disable them by default, but if users want they can selectively disable. Is that enough?

@enj
Copy link
Contributor

enj commented Jun 27, 2017

Why shouldn't they be disabled by default? I would want all half done features to be off, and then I can turn them on if I understand the risks.

@mfojtik
Copy link
Contributor

mfojtik commented Jun 27, 2017

@enj if we start setting this now, it will probably break existing clusters? ;-)

@liggitt
Copy link
Contributor

liggitt commented Jun 27, 2017

if we start setting this now, it will probably break existing clusters? ;-)

we don't intentionally enable alpha types... what existing 1.6 clusters are you referring to?

@mfojtik
Copy link
Contributor

mfojtik commented Jun 27, 2017

@liggitt where we disabling them? the kubernetesMasterConfig.disabledAPIGroupVersions seems to be empty for me.

@deads2k
Copy link
Contributor

deads2k commented Jun 27, 2017

@liggitt where we disabling them? the kubernetesMasterConfig.disabledAPIGroupVersions seems to be empty for me.

As I recall, there is a default whitelist too. Hardcoded.

@mfojtik
Copy link
Contributor

mfojtik commented Jul 12, 2017

@deads2k @liggitt @sttts anything critical missing from this list for 3.6?

@sttts
Copy link
Contributor Author

sttts commented Jul 12, 2017

@mfojtik the item about alpha versions is solved via #14941 I guess. In there, settings.k8s.io is disabled.

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 21, 2018
@soltysh
Copy link
Contributor

soltysh commented Feb 22, 2018

I think at this point all of the points are either handled or already outdated.
/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/techdebt kind/post-rebase lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P1
Projects
None yet
Development

No branches or pull requests

9 participants