Bug 1637042
Summary: | undefined method `[]' for nil:NilClass when more virt-who reports are sent a short time after other | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Pavel Moravec <pmoravec> |
Component: | Subscriptions - virt-who | Assignee: | Partha Aji <paji> |
Status: | CLOSED ERRATA | QA Contact: | Perry Gagne <pgagne> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.3.3 | CC: | aeladawy, arahaman, bbuckingham, ehelms, gscarbor, hsun, jbhatia, jturel, khowell, knakai, ktordeur, kuhuang, mverma, paji, satellite6-bugs, shisingh, suarora, wpinheir, wpoteat |
Target Milestone: | 6.5.0 | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | tfm-rubygem-katello-3.10.0 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-05-14 12:38:11 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Pavel Moravec
2018-10-08 13:47:28 UTC
Brad, this looks like a Katello issue. Katello should handle a status of "WAITING " similar to "PENDING". Thoughts? My change was not intended to remove the needinfo. Adding it back. Connecting redmine issue https://projects.theforeman.org/issues/25643 from this bug Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25643 has been resolved. Verified fix in sat 6.5 snap 11. I ran : curl -k -X POST --user $SATUSER:$SATPASS https://$SATHOST/rhsm/hypervisors/Default_Organization -H "Content-Type: application/json" -d @"/root/foo.json" Multiple times in quick succession. foo.json contained a fairly large number of reports. All of the Hypervisors tasks were successful *** Bug 1667545 has been marked as a duplicate of this bug. *** Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:1222 |