| Summary: | Should only show filtered PetSet | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Yadan Pei <yapei> |
| Component: | Management Console | Assignee: | bpeterse |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.4.0 | CC: | aos-bugs, jforrest, jokerman, mmccomas, tdawson, yanpzhan |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Prior to this release we did not have a dedicated StatefulSets page. Link on the overview page would then go to the Other Resources page and did not filter. We have added both a StatefulSets list & details page which supports filtering in the same way our other resource list pages do.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-04-12 19:16:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Yadan Pei
2016-11-09 05:28:48 UTC
The PetSet won't necessarily have labels on it, so using the label filter may not even help. In 3.5 we are probably implementing actual pages for PetSets. Since PetSets are an alpha feature in 3.4 I'm marking this UpcomingRelease Ben assigning to you since your PetSet story will resolve this Reducing severity since its working as intended right now. This was resolved during 3.5 with the stateful set pages that were added. https://github.com/openshift/origin-web-console/pull/1088 This has been merged into ocp and is in OCP v3.5.0.34 or newer. Checked on openshift v3.5.0.34 When create several statefulsets in project, click one statefulset name on overview page, it will jump to this statefulset detail page directly. The bug has been fixed, so move it to Verified. 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-2017:0884 |