Skip to content

fix: pin constraints to sapcc/requirements stable/2025.2-m3#134

Open
notque wants to merge 1 commit into
masterfrom
fix/update-upper-constraints-url
Open

fix: pin constraints to sapcc/requirements stable/2025.2-m3#134
notque wants to merge 1 commit into
masterfrom
fix/update-upper-constraints-url

Conversation

@notque
Copy link
Copy Markdown
Contributor

@notque notque commented May 14, 2026

Summary

  • Pin upper-constraints to sapcc/requirements/stable/2025.2-m3 instead of upstream openstack/requirements master, which pins unreleased packages (e.g. keystoneauth1===5.14.0) and causes install failures
  • Rename env var from UPPER_CONSTRAINTS_FILE to TOX_CONSTRAINTS_FILE to match the convention used by all other SAP CC OpenStack services

Context

The previous default URL (git.openstack.org) was decommissioned in 2019 and redirects via 302. The opendev.org master branch pins packages that haven't been released to PyPI yet. Using sapcc/requirements stable releases (the same constraints consumed by nova, neutron, keystone, ironic, glance, etc.) ensures reproducible installs.

Test plan

  • tox -e py3 — 76 tests pass
  • tox -e pep8 — flake8 + bandit clean

Switch from upstream openstack/requirements master (which pins
unreleased packages) to sapcc/requirements stable/2025.2-m3.
This aligns with the constraint branch used by other SAP CC
OpenStack services (ironic, glance, keystone, etc.).

Also rename the env var from UPPER_CONSTRAINTS_FILE to
TOX_CONSTRAINTS_FILE, matching the convention used across
all SAP CC service repos.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant