No module named vmtype error.

User 851 | 1/28/2015, 11:17:26 PM

After upgrading to version 1.2.1 I am getting a "ImportError: No module named vtype" when trying to load graphlab. To add to the mystery I have a cluster of 28 identical machines. All of them upgraded with no errors. The error is occurring on only 8 of the machines. Downgrading to 1.2.0 did not fix the problem either.

<blockquote class="Quote"> In [1]: import graphlab as gl


ImportError Traceback (most recent call last) <ipython-input-1-4a710214f762> in <module>() ----> 1 import graphlab as gl

/opt/anaconda/lib/python2.7/site-packages/graphlab/init.py in <module>() 5 """ 6 ----> 7 import graphlab.connect.aws as aws 8 9 import graphlab.deploy

/opt/anaconda/lib/python2.7/site-packages/graphlab/connect/aws/init.py in <module>() 7 8 """ ----> 9 from ec2 import getcredentials, launchEC2, listinstances, setcredentials, status, terminateEC2

/opt/anaconda/lib/python2.7/site-packages/graphlab/connect/aws/_ec2.py in <module>() 11 import urllib2 12 ---> 13 import boto.ec2 14 from boto.exception import EC2ResponseError 15

/opt/anaconda/lib/python2.7/site-packages/boto/ec2/init.py in <module>() 24 service from AWS. 25 """ ---> 26 from boto.ec2.connection import EC2Connection 27 from boto.regioninfo import RegionInfo, getregions, loadregions 28

/opt/anaconda/lib/python2.7/site-packages/boto/ec2/connection.py in <module>() 59 from boto.ec2.placementgroup import PlacementGroup 60 from boto.ec2.tag import Tag ---> 61 from boto.ec2.vmtype import VmType 62 from boto.ec2.instancestatus import InstanceStatusSet 63 from boto.ec2.volumestatus import VolumeStatusSet

ImportError: No module named vmtype </blockquote>

Comments

User 851 | 1/29/2015, 12:12:04 AM

Turns out it was a simple boto version mismatch. not all of them were updated.

Fix was to do a <code class="CodeInline">pip install --upgrade boto</code> and all is well