Bug 1697658
| Summary: | Please rebase onto https://github.com/openshift/api/pull/278 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Eric Paris <eparis> |
| Component: | Node | Assignee: | ravig <rgudimet> |
| Status: | CLOSED ERRATA | QA Contact: | Weinan Liu <weinliu> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.0 | CC: | aos-bugs, jokerman, mmccomas, sjenning |
| Target Milestone: | --- | ||
| Target Release: | 4.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-04 10:47:18 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Eric Paris
2019-04-08 22:45:07 UTC
which won't work until https://github.com/openshift/cluster-kube-scheduler-operator/pull/72 merges, I think.... Hi Seth, and Ravi, as per current info provided, what I can verify is the PR listed below have been merged. If it's for a new feature, I think we'll need a jira task/story tracking this. @Seth, Could you help to confirm if the verification of merging status good enough? Get feature gates and using them while starting kube-scheduler https://github.com/openshift/cluster-kube-scheduler-operator/pull/72 Bump with switch to klog https://github.com/openshift/cluster-kube-scheduler-operator/pull/93 Enable BlockVolume support tech preview for 4.1 https://github.com/openshift/api/pull/278 Yes the bug was to rebase and KSO has been. Verified by confirming the contents of https://github.com/openshift/api/pull/278 are now in the /vendor tree of https://github.com/openshift/cluster-kube-scheduler-operator. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758 |