Bug 1459964
| Summary: | [5.6] DEADLOCK: reactivation-key, snapshot_server(), register/delete | ||
|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Grant Gainey <ggainey> |
| Component: | Server | Assignee: | Grant Gainey <ggainey> |
| Status: | CLOSED ERRATA | QA Contact: | Radovan Drazny <rdrazny> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 560 | CC: | jhutar, rdrazny, satqe-list, tlestach |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | spacewalk-backend-2.0.3-47-sat spacewalk-schema-2.0.2-27-sat satellite-schema-5.6.0.36-1-sat | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1459963 | Environment: | |
| Last Closed: | 2017-07-05 14:28:07 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: | |||
| Bug Depends On: | 1458880, 1459963 | ||
| Bug Blocks: | 1452353 | ||
|
Description
Grant Gainey
2017-06-08 17:01:06 UTC
Tested on spacewalk-backend-2.0.3-47-sat spacewalk-schema-2.0.2-27-sat satellite-schema-5.6.0.36-1-sat using: - the reproducer scripts from bug 1388160 running on four clients - two systems doing rhnreg_ks in a loop - and manually deleting hundreds of previously registered systems using the SSM No deadlocks in tomcat logs nor PG logs, all deletions, registrations and re-activations were successful. Only error encountered was in PG logs: <...> 2017-06-29 06:15:17.756 EDT LOG: unexpected EOF on client connection 2017-06-29 06:15:22.568 EDT LOG: unexpected EOF on client connection 2017-06-29 06:15:45.619 EDT LOG: unexpected EOF on client connection 2017-06-29 06:15:52.843 EDT LOG: unexpected EOF on client connection 2017-06-29 06:16:17.802 EDT LOG: unexpected EOF on client connection <...> These messages look harmless, as there wasn't any other problem. VERIFIED Just to add - I have tested both the PG and Oracle backend. I was able to reproduce the error only on PG. (In reply to Radovan Drazny from comment #7) > Just to add - I have tested both the PG and Oracle backend. I was able to > reproduce the error only on PG. Correct - we've never seen this particular issue in ORA. The two dbs have subtly-different locking strategies. 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/RHBA-2017:1683 |