__virtual__ returned False is cryptic

[ksalman]

The error is cryptic while it just needed python3-mysqldb package. So apt-get install -y python3-mysqldb fixed it.

Setup

vlab local user:
  mysql_user.present:
    - name: user
    - host: localhost
    - allow_passwordless: True
    - require:
      - pkg: mysql-server

Steps to Reproduce Issue

(Include debug logs if possible and relevant.)
Tried to create user with the example pasted above and got this error

<snip>
[DEBUG   ] Could not LazyLoad mysql_user.present: 'mysql_user' __virtual__ returned False
[INFO    ] Running state [vlab] at time 08:06:37.711519
[DEBUG   ] LazyLoaded mysql_user.present
[ERROR   ] State 'mysql_user.present' was not found in SLS 'roles.vlab.database'
Reason: 'mysql_user' __virtual__ returned False
<snip>
----------
          ID: vlab local user
    Function: mysql_user.present
        Name: user
      Result: False
     Comment: State 'mysql_user.present' was not found in SLS 'roles.vlab.database'
              Reason: 'mysql_user' __virtual__ returned False
     Changes:

Versions Report

salt-minion --versions
Salt Version:
Salt: 2019.2.0

Dependency Versions:
cffi: Not Installed
cherrypy: Not Installed
dateutil: 2.4.2
docker-py: Not Installed
gitdb: Not Installed
gitpython: Not Installed
ioflo: Not Installed
Jinja2: 2.8
libgit2: Not Installed
libnacl: Not Installed
M2Crypto: Not Installed
Mako: Not Installed
msgpack-pure: Not Installed
msgpack-python: 0.4.6
mysql-python: 1.3.7
pycparser: Not Installed
pycrypto: 2.6.1
pycryptodome: Not Installed
pygit2: Not Installed
Python: 3.5.2 (default, Nov 12 2018, 13:43:14)
python-gnupg: 0.3.8
PyYAML: 3.11
PyZMQ: 15.2.0
RAET: Not Installed
smmap: Not Installed
timelib: Not Installed
Tornado: 4.2.1
ZMQ: 4.1.4

System Versions:
dist: Ubuntu 16.04 xenial
locale: UTF-8
machine: x86_64
release: 4.4.0-21-generic
system: Linux
version: Ubuntu 16.04 xenial

[lsh-0]

just encountered this, thank you for opening a ticket with a solution! from the error message I assumed we had written some arcane custom code somewhere and forgotten about it.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

[ksalman]

Please reopen.

…

On Sat, Jan 11, 2020, at 23:12, stale[bot] wrote: This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#54702?email_source=notifications&email_token=AAJVZB54LVU7QXFLAQ4ZA53Q5K7F3A5CNFSM4IYYLQZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIWTS3Y#issuecomment-573389167>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJVZB4B2VJBCJJUZOLHQNDQ5K7F3ANCNFSM4IYYLQZQ>.

[stale]

Thank you for updating this issue. It is no longer marked as stale.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

[ksalman]

Please reopen

…

On Tue, Feb 11, 2020, at 07:31, stale[bot] wrote: This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#54702?email_source=notifications&email_token=AAJVZB3NXOAXVSBGIAAHTL3RCLAENA5CNFSM4IYYLQZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELM3JNI#issuecomment-584692917>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJVZB3QGHTVFKXSOGWGE33RCLAENANCNFSM4IYYLQZQ>.

[stale]

Thank you for updating this issue. It is no longer marked as stale.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

[RolandRosenfeld]

Please reopen and fix the issue...

[stale]

Thank you for updating this issue. It is no longer marked as stale.

[sagetherage]

closing as fixed in PR #56395 will be released in Sodium

[sc-kanga]

Please reopen and fix the issue...

If you're still having issues with this, post installation of python3-mysqldb, it's likely you've made the same mistake I did and haven't updated your map.jinja or whatever else it is you've used to jinja map. As soon as I did that, everything worked (though i now have an equally odd error on CentOS)