error running any Ansible task

[jkrilov]

I get the following error when I try to use any lowlydba Ansible module. In this case instance_info

ParserError:  /root/.ansible/tmp/ansible-tmp-1669653577.4521654-1601096-258718634814176/AnsiballZ_instance_info.ps1:159 
    Line | 
     159 |   {\"module_entry\": \"… 
         |   ~ 
         |   unexpected token ' ', expected 'begin', 'process', 'end', 'clean', or 
         |   'dynamicparam'. \n",
        "module_stdout": "",
        "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error",
        "rc": 1
    }

This is what my task looks like. I've confirmed the values of the variables I'm passing as they work with other non-lowlydba tasks.

- name: Get Instance Info
  lowlydba.sqlserver.instance_info:
    sql_instance: "{{ SQL_HOSTNAME }}"
    sql_username: "{{ SQL_ADMIN_USER }}"
    sql_password: "{{ SQL_ADMIN_PASS }}"
  register: sql_info
  ignore_errors: true

I'm running Ansible on a Ubuntu server with the lowlydba.sqlserver collection, latest powershell, and dbatools installed.

Any help would be appreciated!

[lowlydba]

Which version of Ansible & the collection are you using? Are you running from WSL or on native Linux? And what version of DBATools

[jkrilov]

Initially Ansible 6.5, upgraded to 7.0 no difference. lowlydba.sqlserver version 1.1.0, and DBAtools 1.1.143. Running on Ubuntu 20.04 native linux.

Edit: forgot to mention I'm running Ansible in Check mode if that matters.

[lowlydba]

Thanks - are you able to manually import the DBATools module? I have seen some issues importing on Ubuntu, but most of my/reported issues are using containers, so not sure if that is part of the issue or not.

[jkrilov]

Yeah, I can import it using Import-Module dbatools

[lowlydba]

Are you attempting to get it to run on the localhost? Ansible doesn't natively support pwsh executions. You can see the workarounds we have in place to get the integration testing working locally if you need to mimic that setup.

[jkrilov]

The first thread you linked has the exact error I'm seeing too. I think it may be easiest to just delegate these tasks to a Windows host for now (luckily I already have a workstation with network access to SQL that fits the criteria).

I'll report back if I get that working.

[jkrilov]

Well it works after delegating to a Windows host. But now I have a new problem:

Error restoring database: The parameter XpDirTree cannot be used with a Managed SQL Instance.

DBATools supports SQL MI, but it looks like the Ansible module passes some parameters that aren't supported by default.

[lowlydba]

Not surprised, that is not something I tested against at all! Please open a bug for that and I should be able to get a fix out for you soon.

[jkrilov]

Ok, I'll open a bug.

I imagine you would just need to remove the default value like this right? jkrilov@69d2c30 Or did you want some other switch to toggle defaults for a SQL MI?

I'm sure that won't be the only param that throws an error either.

[jkrilov]

Do you want me to create a PR for that change? I'm not sure how you wanted to handle that. I'm not sure if removing that default would be a breaking change, I guess it could be.