SHA host fingerprint cannot be trusted with supplementary hosts enabled

[luixxiul]

It seems that the SHA host fingerprint values cannot be trusted on the first installation command for a new server, if a supplementary host is enabled.

Steps to reproduce the issue:
1, Remove known hosts by running rm ~/.ssh/known_hosts
2. On the remote server, enable public key authentication with SSH (maybe irrelevant; I am not sure)
3. Enable a supplementary host for a service which needs Valkey
4. Run the installation command: rust-just install-all -K
5. Input Yes on the dialog

Expected result:
The host (local machine) should be trusted

Actual result:
Sending Yes returns another same prompt which requests to send Yes again

Note: If the supplementary host is disabled and the installation command is executed, then it is possible to trust the fingerprint value with inputting Yes once.

$ rust-just install-all -K
/usr/local/lib/node_modules/rust-just/node_modules/rust-just-linux-x64/bin/just --justfile /home/user/mash-playbook/justfile run --tags=install-all,start -K
ansible-playbook -i inventory/hosts setup.yml --tags=install-all,start -K
BECOME password: 

PLAY [Set up a self-hosted server] ***************************************************************************************
[WARNING]: Found variable using reserved name: become
[WARNING]: Found variable using reserved name: become_user

TASK [Gathering Facts] ***************************************************************************************************
The authenticity of host 'x.x.x.x (x.x.x.x)' can't be established.
ED25519 key fingerprint is SHA256:zraH7gjZqH2NcVduJrDzW77v2Ty/xxxxxxxxxxxxxxx.
This key is not known by any other names.
The authenticity of host 'x.x.x.x (x.x.x.x)' can't be established.
ED25519 key fingerprint is SHA256:zraH7gjZqH2NcVduJrDzW77v2Ty/xxxxxxxxxxxxxxx.
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Please type 'yes', 'no' or the fingerprint: yes
Please type 'yes', 'no' or the fingerprint: ^C [ERROR]: User interrupted execution

[spantaleev]

1. Does entering yes a 2nd time make it proceed and remember this, so that you don't experience another issue during the current Ansible run?

2. Does having answered with yes to all prompts during the 1st Ansible run suppress all such prompts later on?

I think I've seen this before as well. If Ansible targets multiple hosts at once and various prompts come up (unlocking keys, etc.), you'll be annoyed once for each host and it won't reuse your answers sometimes. If this is it, then this is an Ansible issue and nothing that we (as mere YAML-writing mortals) can probably fix.

[luixxiul]

Does entering yes a 2nd time make it proceed and remember this, so that you don't experience another issue during the current Ansible run?

No, it does not remember choice and keep asking to type "yes".

Does having answered with yes to all prompts during the 1st Ansible run suppress all such prompts later on?

Yes, if the supplementary host is disabled and running the playbook to type "yes" suppresses the prompt to type "yes".