Created attachment 878490 [details] expired manifest Description of problem: I upload expired manifest to an organization. And then I try to enable some Red Hat repository. I got internal error 'SecurityViolation'. I investigate what is wrong, but I didn't find information about expiration. Only error in log. Version-Release number of selected component (if applicable): katello-1.5.0-18.el6sat.noarch How reproducible: Always Steps to Reproduce: 1. Create expired manifest 2. Upload manifesto to Katello 3. Enable some Red Hat repository Actual results: I got error "product Red Hat Enterprise Linux Desktop repositories import: SecurityViolation occurred when contacting CDN to fetch listing files" in log Expected results: Show some message about expired manifest Additional info: ==> /var/log/foreman/production.log <== Rendered /opt/rh/ruby193/root/usr/share/gems/gems/katello-1.5.0/app/views/katello/providers/redhat/_repo_sets.haml (8829.2ms) Rendered /opt/rh/ruby193/root/usr/share/gems/gems/katello-1.5.0/app/views/katello/providers/redhat/_tab.html.haml (12001.0ms) Completed 200 OK in 13287ms (Views: 11756.6ms | ActiveRecord: 259.4ms) Processing by Katello::ProductsController#refresh_content as */* Parameters: {"content_id"=>"829", "id"=>"47"} product Red Hat Enterprise Linux Desktop repositories import: SecurityViolation occurred when contacting CDN to fetch listing files /opt/rh/ruby193/root/usr/share/gems/gems/katello-1.5.0/app/lib/katello/resources/cdn.rb:105:in `rescue in get' /opt/rh/ruby193/root/usr/share/gems/gems/katello-1.5.0/app/lib/katello/resources/cdn.rb:79:in `get'
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Created attachment 1117271 [details] Manifest with expired entitlement This has a single entitlement which expires on Dec 14 2014. It will show the behavior.
Moving 6.2 bugs out to sat-backlog.
I do not believe this will be addressed in the next few releases, so I am closing this out. If you feel this was incorrect, please feel free to re-open with additional information.