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
Comments
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. |
Hallo gentleman! Is there any progress on this issue? thanks! |
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. |
I wonder if the recent commit with a fix to vsphere code could solve this issue? |
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: We'll leave this issue open until we are compatible with the newer psphere. |
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. |
Built a target image for vsphere but when I try to push, I get the following error.
The text was updated successfully, but these errors were encountered: