Issue #2311 is a duplicate

Currently the force logic is entirely within the addHost call. We are passed the kerberos principal, so we could look up the user based on that.

We should probably also change the check. If there are two separate users (one with name=hostname and another principal matching the krb arg) then we should probably error and report this. This case shouldn't happen normally and we should probably leave it to an admin to fix with edit-user.

I don't think we technically have to rename the user. Koji doesn't require that the host's user name be equal to the host.name. However, I think it would be reasonable to do if force is given (unless the name is already taken, but that's the case above).

We may also want to handle the case where the user exists, but does not have the principal associated with it. I think it would be reasonable, when force is given, to add the principal to the user (as long as it's not associated to another user yet).

We are passed the kerberos principal, so we could look up the user based on that.

Well we do that, sort of. We call get_user with both name and krb_principal fields in the krb case, which only reports users that match both. This is why we don't find the desired user to use in the original case. I'm suggesting calling it twice, once for each option.

Side note for context: original feature was PR #2042