Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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:
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.
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: