Grizzly glance command fails on Ubuntu Precise with warlock error

Bug #1131327 reported by Sandeep Raman
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
python-glanceclient (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

OS: Ubuntu Precise 12.04
Glance version: Grizzly 2

root@controller:~# dpkg --print-avail glance
Package: glance
Priority: extra
Section: python
Installed-Size: 45
Maintainer: Ubuntu OpenStack <email address hidden>
Architecture: all
Version: 2013.1.a120.g927088b+git201302201601~precise-0ubuntu1
Depends: glance-api (= 2013.1.a120.g927088b+git201302201601~precise-0ubuntu1), glance-registry (= 2013.1.a120.g927088b+git201302201601~precise-0ubuntu1)
Suggests: python-ceph
Size: 22216

Problem Description:
After successful install and config of glance, glance index errors as below.

root@controller:~# glance index
Traceback (most recent call last):
  File "/usr/bin/glance", line 5, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2711, in <module>
    parse_requirements(__requires__), Environment()
  File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 584, in resolve
    raise DistributionNotFound(req)
pkg_resources.DistributionNotFound: warlock>=0.7.0,<2
root@controller:~#

The glance-api and glance-registry service is crashing as well. The upstart log has the following entry -
2013-02-21 22:30:03.072 2142 CRITICAL glance [-] duplicate option: log-format

The workaround mentioned on the other bugs filed for jsonschema error, 1100356, 1098688, 1101158 did not help.
Added the below in the following files -
root@controller:/usr/share/doc/python-warlock# vi requirements.txt
root@controller:/usr/share/pyshared/warlock-0.1.0.egg-info# vi requires.txt

jsonschema>=0.2
warlock>=0.1.0

Is there any other file, location where the value needs to be changed?

Revision history for this message
Dennis Miyoshi (dennis-miyoshi) wrote :

I do not see the jsonschema error anymore. There is a Problem with the following file though:
/usr/share/pyshared/python_glanceclient-0.7.0.21.ged644d7.egg-info/requires.txt

In this file it specifies warlock>=0.7.0,<2

On my Ubuntu Precise load, warlock is Version 0.1.0 and I have to Change that line to the following to get this all to work:

warlock>=0.1.0,<2

I believe that the latest python-warlock is 0.3.1 but Ubuntu Precise is still using 0.1.0.

Brian Waldon (bcwaldon)
no longer affects: glance
Revision history for this message
Dennis Miyoshi (dennis-miyoshi) wrote :

I'm sure that this is packaging on the Ubuntu side. We'll ask them about this. Thanks.

Revision history for this message
Sandeep Raman (sandeep-raman) wrote :

Modifying as mentioned above did not help. The glance-api and glance-registry service continue to crash and error as before.

Revision history for this message
Sandeep Raman (sandeep-raman) wrote :

Upgraded glance. Modified the following files, made no difference yet.

/usr/lib/python2.7/dist-packages/warlock-0.1.0.egg-info/requires.txt
/usr/lib/python2.7/dist-packages/glance-2013.1.a127.gce8dadf.egg-info/requires.txt
/usr/lib/python2.7/dist-packages/python_glanceclient-0.8.0.2.g6c7fb0e.egg-info/requires.txt
/usr/share/pyshared/warlock-0.1.0.egg-info/requires.txt
/usr/share/pyshared/glance-2013.1.a127.gce8dadf.egg-info/requires.txt
/usr/share/pyshared/python_glanceclient-0.8.0.2.g6c7fb0e.egg-info/requires.txt

Revision history for this message
Sandeep Raman (sandeep-raman) wrote :

I rebuilt the setup and edited the file /usr/lib/python2.7/dist-packages/python_glanceclient-0.8.0.2.g6c7fb0e.egg-info/requires.txt to read warlock>=0.1.0,<2. Services restarted, now glance works.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in python-glanceclient (Ubuntu):
status: New → Confirmed
Chuck Short (zulcss)
Changed in python-glanceclient (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.