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.
Bug 805122 - Sorting algorithm for sync history does not return correct recent status
Summary: Sorting algorithm for sync history does not return correct recent status
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: API
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Eric Helms
QA Contact: Og Maciel
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-20 15:10 UTC by Og Maciel
Modified: 2019-09-26 15:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-22 18:31:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screenshot showing the error and number of notifications (69.15 KB, image/png)
2012-03-20 15:10 UTC, Og Maciel
no flags Details

Description Og Maciel 2012-03-20 15:10:01 UTC
Created attachment 571437 [details]
Screenshot showing the error and number of notifications

Description of problem:

Visiting the Syn Management page for an Org gives me undefined method `<=>' for nil:NilClass and a 500 Internal Server error. As per discussion with Ivan, this is a regression of https://bugzilla.redhat.com/show_bug.cgi?id=798376.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create  new repo with some bigger amount of packages, e.g. http://repos.fedorapeople.org/repos/katello/katello/fedora-16/x86_64/ should be good
2. set sync plan for it
3. synchronize it manually after that
4. optionally, refresh the sync status page while synchronizing
  
Actual results:

Subsequent visits to the Sync Management page return a *undefined method `<=>' for nil:NilClass* notification. It also generates hundreds of notification messages.

Expected results:


Additional info:

Comment 4 Og Maciel 2012-03-23 14:50:27 UTC
Verified:
* candlepin-0.5.26-1.el6.noarch
* candlepin-tomcat6-0.5.26-1.el6.noarch
* katello-0.1.306-1.el6.noarch
* katello-all-0.1.306-1.el6.noarch
* katello-candlepin-cert-key-pair-1.0-1.noarch
* katello-certs-tools-1.0.4-1.el6.noarch
* katello-cli-0.1.107-1.el6.noarch
* katello-cli-common-0.1.107-1.el6.noarch
* katello-common-0.1.306-1.el6.noarch
* katello-configure-0.1.104-1.el6.noarch
* katello-glue-candlepin-0.1.306-1.el6.noarch
* katello-glue-foreman-0.1.306-1.el6.noarch
* katello-glue-pulp-0.1.306-1.el6.noarch
* katello-qpid-broker-key-pair-1.0-1.noarch
* katello-qpid-client-key-pair-1.0-1.noarch
* katello-selinux-0.1.8-1.el6.noarch
* pulp-1.0.0-4.el6.noarch
* pulp-common-1.0.0-4.el6.noarch
* pulp-selinux-server-1.0.0-4.el6.noarch

Comment 6 Anton Arapov 2012-09-07 07:37:43 UTC
*** Bug 835422 has been marked as a duplicate of this bug. ***

Comment 7 Mike McCune 2013-08-16 18:05:02 UTC
getting rid of 6.0.0 version since that doesn't exist


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