Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1334485 - Empty Overview page
Empty Overview page
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console (Show other bugs)
3.2.0
Unspecified Unspecified
medium Severity medium
: ---
: 3.2.1
Assigned To: Jakub Hadvig
Yadan Pei
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-05-09 14:30 EDT by Fabiano Franz
Modified: 2016-06-27 11:06 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When a project had no services but had a deployment configuration with no deployments, the empty Overview page in the web console displayed a "No services to show" message. This bug fix updates the message to more specifically read "There are no services and no running deployments or pods."
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-06-27 11:06:59 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
empty-overview (106.94 KB, image/png)
2016-05-09 14:30 EDT, Fabiano Franz
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1343 normal SHIPPED_LIVE Red Hat OpenShift Enterprise 3.2.1.1 bug fix and enhancement update 2016-06-27 15:04:05 EDT

  None (edit)
Description Fabiano Franz 2016-05-09 14:30:42 EDT
Created attachment 1155410 [details]
empty-overview

Description of problem:

Overview page displayed empty with the "no services to show" message and without the "Add to project" button. 

I had mostly leftovers from deletes resources in my project: 1 build config with the latest build in "failed" state, one pod in an error state and 2 routes without services.

Steps to reproduce it: I'm not exactly sure how I got there, but I was mostly doing a number of 'oc new-app' and 'oc run' with subsequent 'oc expose' and deleting the resources after they were created.
Comment 1 Yadan Pei 2016-05-10 23:17:04 EDT
Hi Fabiano,

Please help check if all resources are deleted successfully by iterating all secondary menus under Browse

When all resources(buildconfig&builds, deploymentconfig&deployments, etc.) are deleted successfully, you could get "Get started with your project" and "Add to Project" button on overview page

If buildconfig/deloymentconfig or other resources which is not intended to show on Overview page exists, you will got "no services to show" message and without the "Add to project" button(that's the scenario in your case)
Comment 2 Jessica Forrester 2016-05-24 10:29:13 EDT
I narrowed down when this occurs and its technically the correct behavior.  It is when you have no services and you have a deployment config that has no associated replication controllers (deployments).  So we don't show you the "empty project" screen because your project is not empty, you have a DC.  For the 3.2.1 / dev preview timeframe the message just needs to get updated to be more clear, 3.3+ we are reworking the overview and will take this case into account and show a DC even if it has no deployments yet.
Comment 3 Jessica Forrester 2016-05-24 10:34:32 EDT
Jakub can you put together a PR that updates the "No services to show" message on the overview to something like "There are no services and no running deployments or pods."
Comment 6 Yadan Pei 2016-06-06 05:53:46 EDT
Now we get clear message "There are no services and no running deployments or pods." if we have none of these in our project.

Compared with message "No Services", it is more reasonable


Message "There are no services and no running deployments or pods." indicated that none of these resources(services, running deployments, pods) we would like to show on Overview page don't exist, maybe other resources exist but we will not print them on overview
Comment 8 errata-xmlrpc 2016-06-27 11:06:59 EDT
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-2016:1343

Note You need to log in before you can comment on or make changes to this bug.