Bug #20058
closed
Erratas can't filter by Environment
Added by Mario Gamboa almost 8 years ago.
Updated almost 7 years ago.
Category:
Errata Management
|
|
Description
When i try apply erratas by environment give a 400 bad request error
17-06-20 11:40:03 caa03134 [app] [I] Empty list of operands (ScopedSearch::QueryNotSupported)
2017-06-20 11:40:03 caa03134 [app] [I] Rendered api/v2/errors/param_error.json.rabl within api/v2/layouts/error_layout (1.1ms)
2017-06-20 11:40:03 caa03134 [app] [I] Completed 400 Bad Request in 97ms (Views: 20.4ms | ActiveRecord: 3.0ms)
2017-06-20 11:40:06 5819a076 [app] [I] Started GET "/notification_recipients" for 10.210.140.132 at 2017-06-20 11:40:06 +0200
2017-06-20 11:40:06 5819a076 [app] [I] Processing by NotificationRecipientsController#index as JSON
2017-06-20 11:40:06 5819a076 [app] [I] Current user: MGamboa (administrator)
and the screen just freeze
- Category set to Errata Management
- Translation missing: en.field_release set to 267
- Difficulty set to easy
- Translation missing: en.field_release changed from 267 to 281
- Translation missing: en.field_release changed from 281 to 286
- Translation missing: en.field_release changed from 286 to 295
- Assignee set to Brad Buckingham
- Target version set to 217
- Translation missing: en.field_release changed from 295 to 250
Hi Mario,
I apologize for the delay. I installed a Katello 3.4.5 instance and have not been able to reproduce the error above.
Scenario:
- sync RHEL 7Server
- create CV with an 'exclude errata by date/type' to ensure clients will have applicable errata
- publish CV and promote to a couple of environments
- register a couple of clients/hosts to the env & content view
- go to Content-> Errata
- select a few errata from the list
- click 'Apply Errata'
- from here, i am at the screenshot above. Perform a 'Filter by environment', selecting each environment available (Library, Dev, Test, Prod).
At this point, I do see the filter applied without errors.
Would it be possible for you to confirm if this issue persists on your environment after updating to K 3.4.5? If so, we may want to see if we can get a foreman-debug with the stack trace of the 400.
Thanks!
- Status changed from New to Need more information
- Target version changed from 217 to 225
- Translation missing: en.field_release changed from 250 to 166
- Target version deleted (
225)
- Status changed from Need more information to Rejected
Closing due to inactivity, feel free to reopen if you are still seeing this on latest katello.
- File deleted (
errata.PNG)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by