Here are the requested versions:
"deb": "3.0.0",
"rpm": "3.23.0",
"core": "3.39.2",
"file": "1.15.1",
"ostree": "2.1.3",
"python": "3.10.0",
"ansible": "0.20.2",
"certguard": "1.7.1",
"container": "2.16.2"
pulp-cli could also be updated to whatever is latest.
Bugs that will need backports into Pulpcore 3.39 before Katello consumes it:
opened 08:58PM - 07 Nov 23 UTC
Issue
Triage-Needed
**Version**
Pulpcore 3.39
**Describe the bug**
When syncing file:// reposit… ories, files are disappearing after the sync.
**To Reproduce**
1) Copy these two repositories to the FS:
- https://github.com/Katello/katello/tree/master/test/fixtures/test_repos/file1
- https://github.com/Katello/katello/tree/master/test/fixtures/test_repos/file2
2) Sync one, then the other
3) See that some files disappeared.
- In my case, file2 lost every file except PULP_MANIFEST
**Expected behavior**
No files disappear.
**Additional context**
This also occurred with RPM content type files.
opened 08:16PM - 07 Nov 23 UTC
closed 02:23PM - 08 Nov 23 UTC
Issue
**Version**
3.39
**Describe the bug**
--max-requests-jitter is not recogniz… ed
**To Reproduce**
Run the pulpcore-api entrypoint with --max-requests-jitter
**Expected behavior**
Accepts the argument
**Additional context**
Requested for Katello.
1 Like
Here’s the new gemspec as it exists in the draft Katello upgrade PR:
#pulp3
gem.add_dependency "pulpcore_client", ">= 3.39.0", "< 3.40.0"
gem.add_dependency "pulp_file_client", ">= 1.15.0", "< 1.16.0"
gem.add_dependency "pulp_ansible_client", ">= 0.20.0", "< 0.21.0"
gem.add_dependency "pulp_container_client", ">= 2.16.0", "< 2.17.0"
gem.add_dependency "pulp_deb_client", ">= 3.0.0", "< 3.1.0"
gem.add_dependency "pulp_rpm_client", ">= 3.23.0", "< 3.24.0"
gem.add_dependency "pulp_certguard_client", "< 2.0.0"
gem.add_dependency "pulp_python_client", ">= 3.10.0", "< 3.11.0"
gem.add_dependency "pulp_ostree_client", ">= 2.1.0", "< 2.2.0"
This was just released to 3.39.2.
iballou
November 14, 2023, 9:46pm
4
Odilhao
November 14, 2023, 9:55pm
5
I’m not seeing 3.39.3 in the release logs on github, we have the PR created to build 3.39.2 Update python-pulpcore to 3.39.2 by Odilhao · Pull Request #744 · theforeman/pulpcore-packaging · GitHub , we can release 3.39.3 later this week.
1 Like
iballou
November 15, 2023, 3:04pm
6
Here is the list of related pull requests to allow Katello to use the Pulpcore 3.39 packages once they’re out:
Katello/katello#10791
theforeman/foreman-packaging#9958
theforeman/foreman-packaging#9957
theforeman/foreman-packaging#9989
theforeman:master
← ianballou:bump-pulpcore-3.39
opened 03:02PM - 15 Nov 23 UTC
Related:
https://github.com/Katello/katello/pull/10791
https://github.com/t… heforeman/foreman-packaging/pull/9958
https://github.com/theforeman/foreman-packaging/pull/9957
https://github.com/theforeman/foreman-packaging/pull/9989
theforeman:master
← ianballou:36902
opened 03:17PM - 08 Nov 23 UTC
Assumes that https://github.com/pulp/pulpcore/issues/4679 is in Pulpcore 3.39.
…
Also assumes that https://github.com/pulp/pulpcore/issues/4681 is going to be fixed for Pulpcore 3.39 in time. This doesn't affect the installer but we shouldn't release Katello with that Pulpcore bug.
I had to assume that the entry point will live in `/usr/bin` since, when installed via `pip`, it is installed to `/usr/local/bin`.
I verified these work (minus the jitter for now):
```
ExecStart=/usr/local/bin/pulpcore-api --preload --timeout 90 --workers 5 --max-requests 800 --access-logfile - --access-logformat 'pulp [%({correlation-id}o)s]: %(h)s %(l)s %(u)s %(t)s "%(r)s" %(s)s %(b)s "%(f)s" "%(a)s"'
```
and
```
ExecStart=/usr/local/bin/pulpcore-content --preload --timeout 90 --workers 5 --access-logfile -
```
iballou
November 17, 2023, 6:02pm
7
I created a docs PR to remove the module stream requirement: Remove references to Pulpcore module stream for Pulpcore 3.39 by ianballou · Pull Request #2597 · theforeman/foreman-documentation · GitHub
I’m also removing the module stream requirement from forklift in the forklift PR mentioned above.
Odilhao
November 20, 2023, 2:39pm
8
We finally have the rpms branched for 3.39 Index of /pulpcore/3.39
Please let me or @pcreech know.
pcreech
November 20, 2023, 3:58pm
9
There were some obsoletes that were missing, mainly from the non-python packages providing python extensions.
theforeman:rpm/develop
← pcreech:fix-obsoletes-python-createrepo_c
opened 03:25PM - 20 Nov 23 UTC
quba42
November 20, 2023, 4:02pm
10
@iballou Once the new repo is ready, what do you do to check if the current Katello main branch will run against this Pulp version? Just curious, and now seems like a good chance to find out.
iballou
November 20, 2023, 9:36pm
11
@quba42 the first thing I do is rerecord the VCR tests for the Pulpcore tests – so:
mode=all bundle exec rake test:katello:test:pulpcore
If that is successful, I move on to doing basic tests for all content types.
Then, I test that the Katello server can still talk to smart proxies from two versions back even with the newer Pulp Ruby bindings.
After that, I leave the newest Pulpcore on my development machine so I can test it with everyday work.
ekohl
November 27, 2023, 11:11am
12
Everything was merged. The pipeline is now failing:
@iballou this was the first run with 3.39
export failed with:
2023-11-25T09:51:26 [E|bac|38eff8ef] uninitialized constant PulpOstreeClient::OstreeRepoImport
38eff8ef | Did you mean? PulpOstreeClient::OstreeImportAll (NameError)
38eff8ef | /usr/share/gems/gems/katello-4.11.0.pre.master/app/services/katello/pulp3/repository.rb:482:in `repository_import_content'
38eff8ef | /usr/share/gems/gems/katello-4.11.0.pre.master/app/lib/actions/pulp3/repository/save_artifact.rb:23:in `invoke_external_t…
pcreech
November 28, 2023, 2:38pm
13