| Summary: | Deleting Activation Key via API Fails. | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Dimitar Yordanov <dyordano> | ||||||||
| Component: | API | Assignee: | Tomas Lestach <tlestach> | ||||||||
| Status: | CLOSED DEFERRED | QA Contact: | Red Hat Satellite QA List <satqe-list> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 540 | CC: | cperry, dyordano, jhutar, jpazdziora, slukasik | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2014-07-04 13:24:34 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 462714 | ||||||||||
| Attachments: |
|
||||||||||
Created attachment 476349 [details]
Proxy Log
Created attachment 476351 [details]
Satellite Log
Comment on attachment 476349 [details]
Proxy Log
Fixing proxy log MIME type.
Comment on attachment 476351 [details]
Satellite Log
Fixing Satellite log MIME type.
Possibly related to bug 683004? The issue seems the same but I an not convinced that one fix will solve both problems. |
Created attachment 476348 [details] Reproducer Description of problem: Sequence of api calls finishing with activationkey.delete cause Satellite to generate traceback but just time to time. Version-Release number of selected component (if applicable): Satellite 5,4, RHN Proxy 5.4 How reproducible: 1 from 5 Steps to Reproduce: 1.Execute the code attached to the bug to RHN Proxy or RHN Satellite. Actual results: At some point traceback is generated. Expected results: All goes smoothly. Additional info: Log provided are from executing the code to RHN Proxy 5.4 connected to Satellite 5.4.