VeeamHub / veeam-ansible

Sample code for deploying and configuring various Veeam solutions using Ansible.
GNU Lesser General Public License v3.0
47 stars 19 forks source link

ONE install: Error when using domain user USERNAME@DOMAIN #71

Open carceneaux opened 3 months ago

carceneaux commented 3 months ago

Describe the bug

Defining one_username with a domain user in the following format - USERNAME@DOMAIN - results in an error during installation.

As is, domain user must be entered in the following format: DOMAIN\USERNAME

Expected behavior

Both username formats must be accepted. Alternatively, a playbook validation check could confirm and report the incorrect configuration early on when running the playbook.

MichaelCade commented 3 months ago

I experienced this with the following error

fatal: [192.168.169.186]: FAILED! => {"changed": false, "msg": "unexpected rc from 'C:\\Windows\\System32\\msiexec.exe /i E:\\Reporter\\VeeamONE.Reporter.WebUI.x64.msi /L*V C:\\Users\\Administrator\\AppData\\Local\\Temp\\ansible-moduletmp-133669981933208933-4812-1137387457\\msiexec.log /qn /norestart /L*v \"C:\\install\\logs\\VeeamONE.Reporter.WebUI.x64.log\" ACCEPT_THIRDPARTY_LICENSES=1 ACCEPT_EULA=1 ACCEPT_LICENSING_POLICY=1 ACCEPT_REQUIRED_SOFTWARE=1 VO_REPORTER_WEB_SERVER_NAME=\"localhost\" VO_REPORTER_WEB_CONNECTION_ACCOUNT_NAME=\"svc_one\" VO_REPORTER_WEB_CONNECTION_ACCOUNT_PASSWORD=\"PASSWORD_HERE\"': see rc, stdout, and stderr for more details", "rc": 1603, "reboot_required": false, "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []}

My playbook defined as one_username: "svc_one"

I added the following to my playbook for the ansible_env to gather the local computer name

    - name: Gather environment facts
      ansible.builtin.setup:
        gather_subset:
          - "env"

This fixed the error and Veeam One was installed using local

MichaelCade commented 3 months ago

I will also add that with the playbook and example I used I did have

gather_facts: false

If this was set to true this would have not been an issue

carceneaux commented 3 months ago

Thx for reporting @MichaelCade! I've created #72 to address the behavior you encountered.