Created attachment 552377 [details]
failure notice

Description of problem:
Selecting an org to work from the orgs list which had a RHEL content already synchronized brings to the error and forever loop of the "Sync overview" panel 

Version-Release number of selected component (if applicable):
katello-0.1.174-2.el6.noarch
katello-cli-0.1.34-2.el6.noarch
candlepin-0.5.8-1.el6.noarch
pulp-0.0.256-1.el6.noarch


How reproducible:
always choosing org with synced RHEL content

Steps to Reproduce:
1. create and org like: v1-scen-org
2. choose to work with that org from UI.
3. import stage manifest and sync RHEL 6.2 64 bit RPMs
4. Close browser and reopen it (default: ACME_Corporation is chosen by default)
5. Switch to work with v1-scen-org again
6. Error
  
Actual results:
Error notification: "undefined method `start_time' for #"
---
Started GET "/katello//dashboard/sync?quantity=-1" for 10.34.30.194 at Thu Jan 12 05:38:10 -0500 2012
  Processing by DashboardController#sync as
  Parameters: {"quantity"=>"-1"}
Rendered dashboard/_sync.haml (695.5ms)
undefined method `start_time' for #<Product:0x7fef46548570>
undefined method `start_time' for #<Product:0x7fef46548570>
#<NoMethodError: undefined method `start_time' for #<Product:0x7fef46548570>>
/usr/lib/ruby/gems/1.8/gems/activemodel-3.0.10/lib/active_model/attribute_methods.rb:392:in `method_missing'
/usr/lib/ruby/gems/1.8/gems/activerecord-3.0.10/lib/active_record/attribute_methods.rb:46:in `method_missing'
/usr/share/katello/app/helpers/dashboard_helper.rb:77:in `products_synced'
/usr/share/katello/app/helpers/dashboard_helper.rb:75:in `sort'
/usr/share/katello/app/helpers/dashboard_helper.rb:75:in `products_synced'
/usr/share/katello/app/views/dashboard/_sync.haml:2:in `_app_views_dashboard__sync_haml___1545822607_70332827723980_5820396'
/usr/lib/ruby/gems/1.8/gems/actionpack-3.0.10/lib/action_view/template.rb:135:in `send'
/usr/lib/ruby/gems/1.8/gems/actionpack-3.0.10/lib/action_view/template.rb:135:in `render'
...
---

Expected results:
No error

Additional info:
Attached is the screenshot of the issue.