Comment 0 for bug 1352273

Hi,

We're upgrading our MAAS infrastructure from precise+MAAS 1.4 to trusty+MAAS 1.5. During a do-release-upgrade, we're seeing the following traceback when setting up maas-region-controller:

 in load_app
    models = import_module('%s.models' % app_name)
  File "/usr/lib/python2.7/dist-packages/django/utils/importlib.py", line 40, in import_module
    __import__(name)
  File "/usr/lib/python2.7/dist-packages/maasserver/models/__init__.py", line 44, in <module>
    from maasserver.models.bootimage import BootImage
  File "/usr/lib/python2.7/dist-packages/maasserver/models/bootimage.py", line 26, in <module>
    from maasserver.models.nodegroup import NodeGroup
  File "/usr/lib/python2.7/dist-packages/maasserver/models/nodegroup.py", line 35, in <module>
    from maasserver.refresh_worker import refresh_worker
  File "/usr/lib/python2.7/dist-packages/maasserver/refresh_worker.py", line 21, in <module>
    from provisioningserver.tasks import refresh_secrets
  File "/usr/lib/python2.7/dist-packages/provisioningserver/tasks.py", line 49, in <module>
    from provisioningserver.custom_hardware.virsh import probe_virsh_and_enlist
  File "/usr/lib/python2.7/dist-packages/provisioningserver/custom_hardware/virsh.py", line 18, in <module>
    import pexpect
ImportError: No module named pexpect

The python-pexpect package isn't installed because we have "APT::Install-Recommends" set to "false".

iF maas-region-controller 1.5.2+bzr2282-0ubuntu0.2 all MAAS server complete region controller
ii maas-region-controller-min 1.5.2+bzr2282-0ubuntu0.2 all MAAS Server minimum region controller

Regards,

Haw