Bug 1717533
| Summary: | Networking details are missing for some deployment configs in web console overview | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Samuel Padgett <spadgett> | ||||
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 4.2.0 | CC: | aabhishe, aos-bugs, hasha, jokerman, mmccomas, yapei | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.2.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Previously, a service would not correctly show up in the project status page when it selected the `deploymentconfig` label that is automatically set for pods created by a deployment config. We now correctly show services that select the `deploymentconfig` label on the project status page.
|
Story Points: | --- | ||||
| Clone Of: | 1717028 | ||||||
| : | 1717535 (view as bug list) | Environment: | |||||
| Last Closed: | 2019-10-16 06:31:10 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: | |||||||
| Bug Depends On: | 1717028 | ||||||
| Bug Blocks: | 1717535 | ||||||
| Attachments: |
|
||||||
|
Comment 1
Samuel Padgett
2019-06-05 18:28:16 UTC
The project overview page will show route, service info correctly. see attachment Verified this bug. quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:439c96093beb009cad05594ef48cde4a4e6cc920aa3ef72015d4a36a62588b39 4.2.0-0.nightly-2019-06-23-223647 Created attachment 1584587 [details]
network
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:2922 |