Created attachment 1096501 [details] engine logs Description of problem: Sometimes when calling setupNetwork the operation fails with error: CallableStatementCallback; SQL [{call insertnetworkattachment(?, ?, ?, ?, ?, ?, ?, ?)}]; ERROR: duplicate key value violates unique constraint "network_attachments_network_id_key" Version-Release number of selected component (if applicable): rhevm-3.6.0.3-0.1.el6.noarch Steps to Reproduce: 1. Run tier1 network automation test Additional info: Correlation-Id: labels_create_9c0a7b3d-eeb5-4b0e (for engine.log)
Meni - why is the severity high? What is the frequency and what is the scenario? Sometimes is not clear enough.
lower the severity to low since it's happened only few time (about 2-3 times for about 500 setupNetworks)
Not reproduced anymore.
We are trying to understand why the customer sees these exception. However, it is important to note right now that when a freshly-built el7 node is added to a cluster with required networks it is *expected* to become non-operational. When a host is added, only the management network is attached to it by default. Further networks have to be attached explicitly via nics or label. If the cluster two which the host is added has multiple required networks, having the management network is not enough and the host becomes non-operational.
Looking at the attached log and the db dump in the SOS report I can see that the installation of the host failed due to a race. The host was refreshed by the vdsManager during the run of HostSetupNetworkCommand. This issue was fixed in patch https://gerrit.ovirt.org/#/c/59318/9 (bug https://bugzilla.redhat.com/1324479). The fix was introduced in 4.0.
Based on comment 7, I believe that it would be possible to backport the fix to 3.6, but it would not be fun. How disruptive is this bug for the customer? Would they want to upgrade to a hot-fixed rhvm-3.6.12 in order to avoid it? Or can they keep a stiff upper lip until their VM compatibility level is 3.6, and they can upgrade to rhvm-4 ?
Why the target milestone is 4.2?
Verified on - 3.6.12-0.1.el6
Hi
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/RHEA-2017:2737