Description of problem: The pod info details are missing in the web UI Version-Release number of selected component (if applicable): OCP 3.7 Verified the below output and it's available: # oc get ep,svc,route
Hi, there's no detail in this bug. Can you describe what the issue is? Is this a problem in 3.7 or 3.11?
The issue is that console is comparing the service `spec.selector` to the labels in the deployment config `spec.template.metadata.labels`. In this case, the service is selecting on a value that is added to the pod automatically by the deployment controller, so it's not matching what's in the pod template in the deployment config itself. We might need to special case this specific scenario.
The workaround is to add `deploymentconfig: <name>` to `spec.template.metadata.labels` in the deployment config. Then the networking information will appear in the overview. Moving the Bugzilla to medium severity since it's an uncommon use case and there's a workaround. (We will still look at addressing this.)
https://github.com/openshift/origin-web-console/pull/3131
1. Create project and resources $ oc new-project gdsp-test $ oc create -f ui/dc_pingtokengenerator deploymentconfig.apps.openshift.io/pingtokengenerator created $ oc create -f Case_02396062_05June2019/svc_pingtokengenerator service/pingtokengenerator created $ oc create -f Case_02396062_05June2019/route_pingtokengenerator route.route.openshift.io/pingtokengenerator created 2. Go to project Overview, click on Deployment Configs to show its details, Networking details are shown on page Verified on OpenShift Web Console: v3.11.117
Created attachment 1580631 [details] NetworkingDetails
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:1605