Smells like race condition. Try without --push-facts-parallel and also indlude full backtrace of the error.

I ran into the same issue. When Debian 10 facts are uploaded only the OS' major version is set in the title and description fields of the operatingsystems table. This results in those fields always being set to "Debian 10" independent of the minor version fact, which is detected properly though and written to the minor column of the table. This means that if Debian 10.0 facts have been uploaded before, the upload of Debian 10.1 facts will result in the Description has already been taken, Title has already been taken error message.

Sounds like a bug, here is the relevant code can you investigate? It should match minor and major versions:

https://github.com/theforeman/foreman/blob/develop/app/services/puppet_fact_parser.rb#L4-L40

Relevant discussion: https://community.theforeman.org/t/facts-upload-failed-description-has-already-been-taken/17573

Perhaps the core issue is that we don't deal with the change in Debian? Since Debian 7 the use of minor versions was dropped. Previously, Debian 6.0 and Debian 6.1 were seen as separate releases. With Debian 7, 7.0 an 7.1 are the same release. The .x is more like a .z in that sense. You can see this in the facter output as well:

$ facter os
{
  architecture => "amd64",
  distro => {
    codename => "buster",
    description => "Debian GNU/Linux 10 (buster)",
    id => "Debian",
    release => {
      full => "10",
      major => "10" 
    }
  },
  family => "Debian",
  hardware => "x86_64",
  name => "Debian",
  release => {
    full => "10.3",
    major => "10",
    minor => "3" 
  },
  selinux => {
    enabled => false
  }
}

Foreman still tries to parse the legacy facts itself and be smarter.

From Debian 9:

# facter lsbdistrelease
9.11

$ facter lsbdistrelease
10

I suspect the following code isn't smart enough about that.

major, minor = orel.split('.', 2)
major = major.to_s.gsub(/\D/, '')
minor = minor.to_s.gsub(/[^\d\.]/, '')

Lukas Zapletal wrote:

Requesting 2.0 backport, multiple users have reported this.

Can we also receive a backport to 1.xx?