
There are two nodepool dependency issues affecting our ability to run tests and build container images. One related to IBM cloud package dependency resolution and the other a yappi compilation problem on aarch64. Recent updates to IBM cloud dependencies have triggered pip dependency resolution to go into full scan mode. Ultimately, this appears to end up scanning old packages that don't have the required requirements.txt content and pip dep resolution breaks due to being unable to find transitive dependencies. (This is likely a broken package that should be pulled from pypi). Work around this by setting our lower bounds on these packages to the versions available on April 28, 2025. Additionally, yappi only publishes wheels for x86_64 so when we install yappi in our debian aarch64 containers we must compile it to produce an installable wheel. This fails with: gcc: internal compiler error: Segmentation fault signal terminated program cc1 I suspect that this stopped working when Debian Bookworm 12.11 was released on May 17, 2025 which would've updated many system level packageson Bookworm. To workaround this for now we simply stop installing yappi on aarch64. This will reduce our ability to debug nodepool on that platform, but nodepool in zuul should eventually mitigate the problems with this. Change-Id: I2b753dbe793661ba6f29ce04961062ae97bd66b6
32 lines
885 B
Plaintext
32 lines
885 B
Plaintext
pbr>=1.3
|
|
|
|
PyYAML
|
|
paramiko>=2.0.1
|
|
python-daemon>=2.0.4
|
|
extras
|
|
statsd>=3.0
|
|
PrettyTable>=0.6,<0.8
|
|
# 0.99.0 - 0.102 lead to BadRequestException: Client Error [...] Bad networks format
|
|
# This was due to not properly handling nova api microversions properly. 0.103
|
|
# fixes this.
|
|
# 2.0.0 broke cinder v2 api limits listing.
|
|
openstacksdk>=0.103.0,!=2.0.0
|
|
# Needed for rax api_key use after MFA becomes required
|
|
rackspaceauth
|
|
diskimage-builder>=3.36.0
|
|
voluptuous
|
|
kazoo==2.9.0
|
|
Paste
|
|
WebOb>=1.8.1
|
|
openshift>=0.13.1,<0.14.0
|
|
boto3>=1.34.141
|
|
# TODO: remove grpcio pinning below; 1.71.0rc2 is messing with pip installing opentelemetry-exporter-otlp-proto-grpc
|
|
grpcio==1.69.0
|
|
google-api-python-client
|
|
# botocore 1.23.0 (via boto3 1.20.0) requires urllib 1.26.0 or newer:
|
|
# https://github.com/boto/botocore/issues/2562
|
|
urllib3>=1.26.0
|
|
ibm-vpc>=0.28.0
|
|
ibm-platform-services>=0.64.0
|
|
ibm-cos-sdk>=2.14.0
|