Bug 1713769
Summary: | 'duplicate key value violates unique constraint "index_roles_on_name"' when installing 6.5.0 | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Stephen Gallagher <sgallagh> | ||||
Component: | Users & Roles | Assignee: | Ondřej Pražák <oprazak> | ||||
Status: | CLOSED ERRATA | QA Contact: | Radovan Drazny <rdrazny> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 6.5.0 | CC: | ekohlvan, mhulan, wesley.fowler.ctr, zhunting | ||||
Target Milestone: | 6.6.0 | Keywords: | Triaged | ||||
Target Release: | Unused | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | foreman-1.22.0.12-1 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2019-10-22 19:47:47 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: | 1589625 | ||||||
Bug Blocks: | |||||||
Attachments: |
|
Description
Stephen Gallagher
2019-05-24 18:46:01 UTC
Created attachment 1573003 [details]
Full satellite install log
(In reply to Stephen Gallagher from comment #0) > Description of problem: > Unique constraint errors displayed when installing Satellite 6.4 This should read "Satellite 6.5", of course. Must have mis-typed. The summary and RPM version is otherwise accurate. On a whim, I tried exactly the same steps today and it successfully installed. The only difference was that I tried it on a VM with more CPUs and memory. When I reported this bug, I was installing on a system with 6 vCPUs (from a VM host with 24 logical CPUs) and 16GiB of RAM (out of 32GiB on the VM host). Today my VM had 12 vCPUs and 24 GiB of RAM (from the same VM host system). I suspect there's a race condition somewhere and that my new VM, having more CPUs and RAM, managed to skip. To confirm this problem... We got the same error with a clean 6.5 installation on a new VM. Following Mr. Gallagher's success with increasing resources, I tried doing likewise (reverting to a pre-install snapshot and then temporarily increasing the virtual resources from 4 to 8 CPUs and from 20 to 40GB ram). With the increased resources, I didn't run into the error at all. A race condition as previously suggested would make sense (Thank you Mr. Gallagher for saving me a support call). Created redmine issue https://projects.theforeman.org/issues/27380 from this bug Upstream bug assigned to oprazak Upstream bug assigned to oprazak As we don't have a reliable reproducer, I was unable to reproduce the bug. I have tested the installation scenario without any issues. VERIFIED 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:3172 |