| Summary: | [RFE] Dashboard - Handle errors when pulp not responsive. | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Corey Welton <cwelton> |
| Component: | Dashboard | Assignee: | Christine Fouant <cfouant> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Katello QA List <katello-qa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.0 | CC: | bkearney, mmccune |
| Target Milestone: | Unspecified | Keywords: | FutureFeature, PrioBumpQA, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-03-30 19:22:45 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
we need a general heartbeat process that checks CP/Pulp/Foreman and provides big notifs or an outage page Moving this to an RFE to add a small feature that will handle all backend service errors giving the users a friendly notice that something major went wrong and pointing them to the About page to check services. The new dashboard logix should address this. |
Description of problem: When pulp is down (and possibly, changesets exist), user gets a really ugly dashboard message that we should probably make a little more user-friendly. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: You may or may not have to create changesets for this to show up. Go ahead and do it.... 1. Create a new promotion changeset, "bugtest2" - add content, review it, but do not yet promote 2. Do something that would trigger a failure - this can be done by executing `service mongod stop` 3. Attempt to promote changeset; wait for failure 4. While mongod is still down, nav to the dashboard. Actual results: Error message in notification: Pulp::Consumer: 500 Internal Server Error "Traceback (most recent call last):\n File \"/usr/lib/python2.6/site-packages/pulp/server/webservices/controllers/decorators.py\", line 48, in report_error\n return method(self, *args, **kwargs)\n File \"/usr/lib/python2.6/site-packages/pulp/server/webservices/controllers/decorators.py\", line 112, in _auth_decorator\n user = check_oauth(username, meth, url, auth, query)\n File \"/usr/lib/python2.6/site-packages/pulp/server/auth/authentication.py\", line 216, in check_oauth\n return _check_username_password_local(username)\n File \"/usr/lib/python2.6/site-packages/pulp/server/auth/authentication.py\", line 105, in _check_username_password_local\n user = _user_api.user(username)\n File \"/usr/lib/python2.6/site-packages/pulp/server/api/user.py\", line 92, in user\n users = self.users({'login': login}, fields)\n File \"/usr/lib/python2.6/site-packages/pulp/server/api/user.py\", line 85, in users\n users = list(self.collection.find(spec=spec, fields=fields))\n File \"/usr/lib/python2.6/site-packages/pulp/server/api/base.py\", line 32, in collection\n return self._getcollection()\n File \"/usr/lib/python2.6/site-packages/pulp/server/api/user.py\", line 31, in _getcollection\n return model.User.get_collection()\n File \"/usr/lib/python2.6/site-packages/pulp/server/db/model/base.py\", line 126, in get_collection\n return cls._get_collection_from_db()\n File \"/usr/lib/python2.6/site-packages/pulp/server/db/model/base.py\", line 102, in _get_collection_from_db\n _ensure_indices(collection, cls.unique_indices, True)\n File \"/usr/lib/python2.6/site-packages/pulp/server/db/model/base.py\", line 99, in _ensure_indices\n unique=unique, background=True)\n File \"/usr/lib/python2.6/site-packages/pulp/server/db/connection.py\", line 80, in retry\n return method(*args, **kwargs)\n File \"/usr/lib64/python2.6/site-packages/pymongo/collection.py\", line 713, in ensure_index\n ttl, **kwargs)\n File \"/usr/lib/python2.6/site-packages/pulp/server/db/connection.py\", line 89, in retry\n Expected results: Handle such errors gracefully - provide some contextual clue that perhaps the pulp service is down. Additional info: