Hello Marek,
Thank you for your reply.
Trying to correct it manually using the interface I still got the same taxonomy error.
Because of your suggestion I tried using hammer to correct it:
$ hammer organization add-environment --id 3 --puppet-environment-id 1
$ hammer location add-user --id 4 --user-id 7
After correcting the organization environment and user the problem with the Default Location disappeared (autocorrected?).
Now if i run:
$ hammer location info --id 2
I can see the smartproxy that was appearing on the mismatch report on the list of smartproxies.
Unfortunately this is a regression for us.
As I said before we have two locations. The Default Location where most our are machines are and a secondary one where we have some machines. The foreman/katello server does not have direct access to all the machines, so in order to use Remote Execution we added the smartproxy with which foreman/katello can communicate.
After adding the smartproxy all the remote execution jobs (for all the machines) started using it, so it were failing for most of our machines.
To workaround this, we removed the smartproxy completely and manually added it only on the secondary location.
We asked for help about this issue before here.
Best regards,
Armindo Silva.