Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failure to push to vsphere #248

Closed
dajohnso opened this issue Feb 14, 2013 · 6 comments
Closed

failure to push to vsphere #248

dajohnso opened this issue Feb 14, 2013 · 6 comments

Comments

@dajohnso
Copy link

Built a target image for vsphere but when I try to push, I get the following error.

2013-02-14 11:16:44,835 DEBUG imgfac.PersistentImage.ProviderImage thread(7ce6859e) Message: Executing metadata in class (<class 'imgfac.ProviderImage.ProviderImage'>) my metadata is (('target_image_id', 'provider', 'identifier_on_provider', 'provider_account_identifier', 'parameters'))
2013-02-14 11:16:44,836 DEBUG imgfac.PersistentImage.ProviderImage thread(7ce6859e) Message: Executing metadata in class (<class 'imgfac.ProviderImage.ProviderImage'>) my metadata is (('identifier', 'data', 'template', 'icicle', 'status_detail', 'status', 'percent_complete', 'parameters'))
2013-02-14 11:16:44,837 DEBUG imgfac.FilePersistentImageManager.FilePersistentImageManager thread(7ce6859e) Message: Saved metadata for image (d6721914-553b-4cb2-ae7e-e5111c8266c3): {'status': 'FAILED', 'identifier': 'd6721914-553b-4cb2-ae7e-e5111c8266c3', 'parameters': None, 'icicle': None, 'data': '/var/lib/imagefactory/storage/d6721914-553b-4cb2-ae7e-e5111c8266c3.body', 'identifier_on_provider': None, 'status_detail': {'error': None, 'activity': 'Initializing image prior to Cloud/OS customization'}, 'provider_account_identifier': None, 'template': u'<template>\r\n                    <name>RHEL6.3</name>\r\n                    <os>\r\n                      <name>RHEL-6</name>\r\n                      <version>3</version>\r\n                      <arch>x86_64</arch>\r\n                      <install type="url">\r\n                          <url>http://download.devel.redhat.com/released/RHEL-6/6.3/Server/x86_64/os/</url>\r\n                      </install>\r\n                      <rootpw>redhat</rootpw>\r\n                    </os>\r\n                    <description>RHEL63 x86_64 </description>\r\n                  </template>\r\n                  ', 'provider': '{"api-url":"https://10.16.120.33/sdk","datastore":"iscsi_storage","network_name":"VM Network"}', 'target_image_id': 'e8ffee78-02d3-4416-bd66-82004d1380ea', 'percent_complete': 0, 'type': 'ProviderImage'}
2013-02-14 11:16:44,837 ERROR imgfac.Builder.Builder thread(7ce6859e) Message: Exception encountered in _push_image_to_provider thread
2013-02-14 11:16:44,837 ERROR imgfac.Builder.Builder thread(7ce6859e) Message: 'NoneType' object has no attribute 'push_image_to_provider'
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/imgfac/Builder.py", line 347, in _push_image_to_provider
    self.cloud_plugin.push_image_to_provider(self, provider, credentials, target, image_id, parameters)
AttributeError: 'NoneType' object has no attribute 'push_image_to_provider'
2013-02-14 11:16:45,011 DEBUG imgfac.CallbackWorker.CallbackWorker thread(Thread-8) Message: Entering blocking non-empty queue call
2013-02-14 11:16:45,011 DEBUG imgfac.CallbackWorker.CallbackWorker thread(Thread-8) Message: Leaving blocking non-empty queue call
2013-02-14 11:16:45,011 DEBUG imgfac.CallbackWorker.CallbackWorker thread(Thread-8) Message: Updated image is: ({'provider_image': {'status': 'FAILED', '_type': 'ProviderImage', 'parameters': None, 'identifier_on_provider': None, 'icicle': None, 'status_detail': {'error': None, 'activity': 'Initializing image prior to Cloud/OS customization'}, 'provider_account_identifier': None, 'template': u'<template>\r\n                    <name>RHEL6.3</name>\r\n                    <os>\r\n                      <name>RHEL-6</name>\r\n                      <version>3</version>\r\n                      <arch>x86_64</arch>\r\n                      <install type="url">\r\n                          <url>http://download.devel.redhat.com/released/RHEL-6/6.3/Server/x86_64/os/</url>\r\n                      </install>\r\n                      <rootpw>redhat</rootpw>\r\n                    </os>\r\n                    <description>RHEL63 x86_64 </description>\r\n                  </template>\r\n                  ', 'provider': '{"api-url":"https://10.16.120.33/sdk","datastore":"iscsi_storage","network_name":"VM Network"}', 'percent_complete': 0, 'id': 'd6721914-553b-4cb2-ae7e-e5111c8266c3'}})
2013-02-14 11:16:45,011 DEBUG imgfac.CallbackWorker.CallbackWorker thread(Thread-8) Message: PUTing update to URL (http://cloud-qe-5.idm.lab.bos.redhat.com:3000/tim/provider_images/4)
@imcleod
Copy link
Contributor

imcleod commented Feb 15, 2013

This normally indicates that the plugin for the specified target could not be found. However, I believe we recently determined that this particular error is a result of an upstream change in python-psphere that breaks compatibility and actually prevents the vSphere plugin from importing completely.

We can either spend some time determining what has changed in psphere or recommend a downgrade.

@martinpovolny
Copy link

Hallo gentleman!

Is there any progress on this issue?
Can you e.g. recommend a working version of the library involved (the python-psphere)?

thanks!

@dajohnso
Copy link
Author

dajohnso commented Mar 4, 2013

In an attempt to find a workaround, I tried using this src rpm[1] which we have been using forever. Incidentally, it is the same version to the one in f17 repos that we are seeing the failure. Unfortunately it too fails which seems to indicate that the theory of a recent python-psphere update being the cause of this failure is incorrect.

[1] wget http://repos.fedorapeople.org/repos/aeolus/imagefactory/testing/latest_bindings/python-psphere-0.1.4-2.fc14.src.rpm

@ghost ghost assigned steveloranz Mar 6, 2013
@martinpovolny
Copy link

I wonder if the recent commit with a fix to vsphere code could solve this issue?

@imcleod
Copy link
Contributor

imcleod commented Mar 26, 2013

This remains an issue. We are not compatible with the latest psphere in Feodra.

Users who need vsphere to work with the upstream code can downgrade to this psphere:

http://repos.fedorapeople.org/repos/aeolus/imagefactory/testing/repos/fedora/17/source/python-psphere-0.5.1_44_gde2b93f-1.fc17.src.rpm

We'll leave this issue open until we are compatible with the newer psphere.

@dkliban
Copy link
Member

dkliban commented Apr 5, 2013

The problem lies in the fact that python-pshere in F17 and F18 repositories is at 0.1.4. Since this plugin was written, it has required manually installing a newer version of python-psphere. Closing this issue and opening another one for packaging a newer version of python-psphere.

@dkliban dkliban closed this as completed Apr 5, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants