Comment 0 for bug 1986590

at some point in the recent past, the maas cli (not maas-cli which is, confusingly an entirely different tool) has started throwing a traceback:

$ maas --help
Traceback (most recent call last):
  File "/usr/bin/maas", line 11, in <module>
    load_entry_point('maas==3.2.1', 'console_scripts', 'maas')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 490, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2854, in load_entry_point
    return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2445, in load
    return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2451, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/maascli/__init__.py", line 10, in <module>
    from maascli.parser import get_deepest_subparser, prepare_parser
  File "/usr/lib/python3/dist-packages/maascli/parser.py", line 12, in <module>
    from maascli.cli import register_cli_commands
  File "/usr/lib/python3/dist-packages/maascli/cli.py", line 30, in <module>
    from provisioningserver.certificates import check_certificate
ModuleNotFoundError: No module named 'provisioningserver'

I'm unable to use the maas cli tool now.