I am trying to install devstack on Ubuntu 18.04, using the guide in https://docs.openstack.org/devstack/latest/.
Installation fails with the error,
ERROR: Cannot install cinder because these package versions have conflicting dependencies.
The conflict is caused by:
oslo-vmware 3.9.1 depends on suds-jurko>=0.6
The user requested (constraint) suds-jurko===0.6
To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/user_guide/#fixing-conflicting-dependencies
I have 2 python versions on the machine
stack#stack:~/devstack$ which python
/usr/bin/python
stack#stack:~/devstack$ which python3
/usr/bin/python3
Am I missing something here?
Best Regards,
J
Just install setuptools 57.5.0
vim /opt/stack/requirements/upper-constraints.txt
like this:
#setuptools===58.2.0
setuptools===57.5.0
It works for me.
The issue is that suds-jurko is incompatible with the setuptools 58.0. You would need to downgrade to setuptools 57.5.0, e.g. pip install setuptools==57.5.0, but it's possible that devstack will upgrade it again.
The real solution is a set of upstream patches that are already in the works to fix this, but isn't merged yet (as of this post).
https://review.opendev.org/c/openstack/oslo.vmware/+/813377
Related
I'm trying to install azureml-sdk in a Mac M1 with Python 3.9.15 and facing the following problems:
When I pip install azureml-sdk, it installs an old version (azureml==1.0.23)
If I run:
from azureml.core import Workspace
ws = Workspace.from_config()
I get the following error:
AttributeError: 'BasicTokenAuthentication' object has no attribute 'get_token'
And if I try to install the latest azureml-sdk version with
pip install azureml-sdk==1.48.0
I get the following error:
ERROR: Cannot install azureml-dataset-runtime because these package versions have conflicting dependencies.
The conflict is caused by:
azureml-dataprep 4.8.3 depends on azureml-dataprep-native<39.0.0 and >=38.0.0
azureml-dataprep 4.8.2 depends on azureml-dataprep-native<39.0.0 and >=38.0.0
azureml-dataprep 4.8.1 depends on azureml-dataprep-native<39.0.0 and >=38.0.0
azureml-dataprep 4.8.0 depends on azureml-dataprep-native<39.0.0 and >=38.0.0
To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
Any ideas? Thanks in advance
Regarding the first error you cited, this error is typically experienced when the provided login credentials for the Azure Machine Learning workspace are incorrect.
Verify the access rights for the workspace on the service principal you are using for authentication.
Make sure the configuration file you use for authentication is formatted correctly and has all the necessary elements.
Use the newly created service principal and configuration file to authenticate.
The second error is because these package versions have conflicting dependencies, typically experienced when there is a conflict between the dependencies of the installed packages.
You might attempt the following solutions to troubleshoot this problem:
Try downgrading or upgrading the conflicting packages' versions until you find one that works with the Azure Machine Learning SDK.
To avoid installing the dependencies, try installing the Azure Machine Learning SDK using the —no-deps parameter.
If the issue still exists, you can try deleting and then reinstalling every package linked to Azure Machine Learning.
Getting this error in my Jupyter Notebook
What would be the best way to fix this utilizing conda instead of pip
I've attempted conda upgrade --all and that didnt seem to work
The scipy.sparse.*_array functions were introduced with v1.8. The networkx package started requiring scipy >=1.8 with v2.7. So, either upgrade SciPy
conda install 'scipy>=1.8'
or downgrade NetworkX:
conda install 'networkx<2.7'
Part of the issue here is that, at the recommendation of a networkx developer, Conda Forge stopped explicitly requiring scipy as a dependency of networkx, and therefore there is no longer any constraint. I opened an issue on the feedstock to revisit coinstallation constraints (run_constrained specifications).
As mentioned in this Github comment, I was trying to calculate the page rank (networkx.pagerank) of a graph on Google Colab when I encountered the same error. After executing the following code, the issue was resolved for me:
!pip install --upgrade scipy networkx
A Side Note: pip install refers to installing packages and leave the package as-is if it is already installed. But the --upgrade flag instructs pip to uninstall anything which is being upgraded/replaced. For more info on this, refer this official doc.
I encountered similar error
I could solve it by installing these versions of newtorkx and scipy:
!pip install 'networkx<2.7'
!pip install 'scipy>=1.8'
I am trying to install Openstack using DevStack. After correctly creating the user stack and running ./stack.sh, the script starts to install the required dependencies until it hits Obtaining file:///opt/stack/cinder. Then I obtain the following errors:
Exception:
ContextualVersionConflict: (grpcio 1.21.1 (/usr/local/lib/python2.7/dist-packages), Requirement.parse('grpcio<1.16.0,>=1.0.0'), set(['tooz']))
I understand that there is a conflict in grpcio, but I don't know how to solve it. I already unsuccessfully tried to install a specific version between 1.0.0 and 1.16.0.
The Devstack version I am using is the latest from the git master.
I think I solved the problem myself.
I had the tooz package installed with version 1.62 which was causing the issue.
After removing that package the installation completed.
I am seeing the below error when deploying devstack (openstack) on ubuntu:
E: Unable to locate package libvirt-clients
E: Unable to locate package libvirt-daemon-system
Any clues pls ?
I have this problem too and i use ubuntu trusty
according to this commit:
https://github.com/openstack-dev/devstack/commit/03fbc0d71bf4ee85820999ef1324dc319ef9d926?diff=split
they changed the repo packages 5 days ago and just for ubuntu xenial its the same as before : "install_package libvirt-bin libvirt-dev"
but other distros: "install_package libvirt-clients libvirt-daemon-system libvirt-dev"
I think we could better edit the file manually until better changes take place.
You're probably trying to install Devstack it on an unsupported version of Linux. Try Ubuntu 16.0.4 (worked for my today without a single problem) or the one that the installation guide says is supported.
Try sudo apt install qemu qemu-kvm virt-manager for more information check this out on github.
I am facing a problem while installing openstack through devstack script on my Ubuntu 15 lts.
It says:
sorry, but this version only supports 100 named groups" AssertionError: sorry, but this version only supports 100 named groups ---------------------------------------- Rolling back uninstall of cryptography
Hi this is due to a pycparser 2.14 package update on pypi today. More details can be found in [1] and [2].
[1] http://lists.openstack.org/pipermail/openstack-dev/2016-October/104909.html
[2] https://github.com/eliben/pycparser/issues/147
Workaround to fix it is to change "pycparser===2.14"in /opt/stack/requirements/upper-constraints.txt to "pycparser===2.13"
Using pip to change the version will not work, because DevStack will uninstall 2.13 version and update it to 2.14, as required in the above file.
========================================================================
Update on 10/4(JST):
according to the update in [2], this bug has been resolved. :)
It's an issue with pythons pycparser lib, install the previous version by setting pycparser==2.13 in your requirements.txt file or via pip.
I have same problem and I resolve this issue after removing 'pycparser' package, using below command:
pip uninstall pycparser
The source package of pycparser doesn't have this problem, only the wheel seems to fail.
Using the --no-binary in your installation command or requirements file should make it work too.
I added --no-binary pycparser in the end of my requirements file and it did the job.
Just adding this so that it may help someone...
Our Devstack also failed because of this pycparser bug. We have just downgraded pycparser to 2.13 in requirement.txt/upper_requirement.txt and disabled 'tempest' service(This service will install cryptography and pycparser) in local.conf. After this, our Devstack installation was successful.
NOTE: comment the line 'RECLONE=yes' in local.conf file.
Thanks