| Summary: | ISE when adding packages to a custom channel | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Network | Reporter: | Sebastian Skracic <sskracic> |
| Component: | RHN/Web Site | Assignee: | Sebastian Skracic <sskracic> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Red Hat Network Quality Assurance <rhn-qa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | RHN Stable | CC: | aowens, nbronson, vambati |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | US=7680 | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-03-23 20:23:45 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: | 678547 | ||
|
Description
Sebastian Skracic
2011-02-18 11:47:35 UTC
*** Bug 617345 has been marked as a duplicate of this bug. *** This is very likely caused by race condition between Java and Perl tiers, who all want to insert the same row into rhnSet. In "normal" environments, usually the Java layer processes the AJAX requests (spawned by clicking on the checkboxes) fast enough to have rhnSet populated before user has clicked on the 'Add' button. In that case, Perl tier sees those entries populated and decides not to do any more work on them. However, if Java processing is stuck or simply slow, there is a fair amount of chance that not all AJAX requests will be processed at the time Perl has started the processing of the form submission. In that situation, Perl will see only part of the user selected checkbox values actually inserted into rhnSet table and it will helpfully try to insert the missing values. At the same time, Java is trying to insert the same rows on its own. Most of the time it works without error, given the db and the Java layer is responsive enough. Fix provided in d12ce181a12c9901163e706f72420548f6d9231c. And available on WEBDEV. verified in webdev. *** Bug 548084 has been marked as a duplicate of this bug. *** verified in webqa |