-
Notifications
You must be signed in to change notification settings - Fork 138
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
Routine update of dependencies after additional pinning #2917 #2919
Routine update of dependencies after additional pinning #2917 #2919
Conversation
Update Poetry managed dependencies after additional pinning: Includes additional pinning in pyproject.toml. All the following were unpinned previously: - django-oauth-toolkit = "~2.4" (Avoid potential breaking changes). - gevent = "24.2.1" (Avoid AUTH_REQ_SASL_CONT without AUTH_REQ_SASL artifact). - gunicorn = "~23" (was "*") (Pin to major version, precaution) Package operations: 0 installs, 19 updates, 0 removals • Updating cffi (1.17.0 -> 1.17.1) • Updating cryptography (43.0.0 -> 43.0.1) • Updating more-itertools (10.4.0 -> 10.5.0) • Updating zipp (3.20.1 -> 3.20.2) • Updating certifi (2024.7.4 -> 2024.8.30) • Updating charset-normalizer (3.3.2 -> 3.4.0) • Updating idna (3.8 -> 3.10) • Updating importlib-metadata (8.4.0 -> 8.5.0) • Updating jaraco-functools (4.0.2 -> 4.1.0) • Updating setuptools (73.0.1 -> 75.2.0) • Updating simple-websocket (1.0.0 -> 1.1.0) • Updating urllib3 (2.2.2 -> 2.2.3) • Updating django (4.2.15 -> 4.2.16) • Updating greenlet (3.0.3 -> 3.1.1) • Updating keyring (25.3.0 -> 25.4.1) • Updating pytz (2024.1 -> 2024.2) • Updating zope-interface (7.0.2 -> 7.1.0) • Updating huey (2.5.1 -> 2.5.2) • Updating psycopg (3.2.1 -> 3.2.3) Writing lock file N.B. Before pinning gevent the following was observed: ``` connection to server on socket "/run/postgresql/.s.PGSQL.5432" failed: fe_sendauth: invalid authentication request from server: AUTH_REQ_SASL_CONT without AUTH_REQ_SASL ```
TestingAs we are nearing our next stable release, another proof-of-update from last stable (based on non EOL base OS) 'rockstor' rpm 4.6.1-0 was enacted. A host derived from a clean install of the last available stable installer:
This instance was then updated to a current/non-EOL OS base via:
N.B. in this stress-test scenario the 'donor' system maintained a stable subscription & 'rockstor' package install: we have 4.6.1-0 as latest stable available in the Stable repositories for our "Built on openSUSE" Leap 15.4 & 15.5 repos. A LAN local repo host was then added (via zypper and dnf) to emulate a PRODUCTION update to our stable repos to prove:
rockstor.log re migrations etc
Post awaiting the Web-UI reset, with consequent re-login, the resulting successfully instantiated all updates. Note: "Ctrl + Shift + R" post re-login was required to pick-up some newer Web-UI features. This is a recommendation we already have in our Web-UI update page. An indicator of this requirement was no "Uses openSUSE" version specified. I.e. newer 'rockstor' instances after 4.6.1-0 rpm now show for example:
In the top-right of the Web-UI. As the browser can inadvertently maintain older elements of the Rockstor Web-UI, there can be issues over 'rockstor' package updates and in some cases a clearing of the browser cache can be required. |
On the basis of the last comment, detailing the testing done, and given there has been no other community interaction regarding these proposed dependency updates (and new pinnings), I'll merge this proposal ready for our next testing channel rpm release; and to ease what remaining development takes place before that. |
Update Poetry managed dependencies after additional pinning:
Fixes #2917
Includes additional pinning in pyproject.toml.
All the following were unpinned previously:
N.B. Before pinning gevent the following was observed: