Description of problem: We added a check for the dmi.system.uuid fact in commit 20fda4baa6bcaf7897189ef775b28df0f8b97478 Author: Jonathon Turel <jturel> Date: Thu Feb 28 16:10:05 2019 +0000 BZ #1652652 - Registering a system fails randomly (409 Conflict) Fixes #26191 - Find existing system by UUID during registration (cherry picked from commit 94fdc4456bffe91590be2294e90cad548f8dae24) This prevents users from registering systems that don't have this fact set (like QEMU VMs). I think the empty UUID should be specialcased here. Version-Release number of selected component (if applicable): 6.5.0 Snap 26 How reproducible: 100% Steps to Reproduce: 1. start two VMs with QEMU 2. register both to satellite 3. Actual results: on second register, you get "HTTP error (500 - Internal Server Error): Multiple profiles found. Consider removing XXX which match this host." Expected results: Subscribed systems. Additional info:
Created redmine issue https://projects.theforeman.org/issues/26825 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26825 has been resolved.
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