Samir Jha

I have the commit with local test fixes but we need to run the CI once to make sure the same tests fail on the CI with PF5.. https://github.com/sjha4/katello/commit/08aae79ee52203fd3bdd2dad70b6a1e4ae09d7f8

Not sure if you included this https://github.com/sjha4/katello/commit/08aae79ee52203fd3bdd2dad70b6a1e4ae09d7f8 into the PR for the test errors?

Able to reproduce the issue, this was what katello sent pulp with complete sync: ``` 14:13:18 rails.1 | 2024-10-18T14:13:18 [D|kat|72c80f12] Calling API: RepositoriesRpmApi.sync ... 14:13:18 rails.1 | 2024-10-18T14:13:18 [D|kat|72c80f12] HTTP...

On this branch, katello correctly sends optimize:false to pulp. ``` 14:23:32 rails.1 | 2024-10-18T14:23:32 [D|kat|756893c0] HTTP request body param ~BEGIN~ 14:23:32 rails.1 | 756893c0 | {"remote":"/pulp/api/v3/remotes/rpm/rpm/01929fe5-3f01-7f0e-93c3-75176f040d6d/", "sync_policy":"mirror_complete", "optimize":false} 14:23:32 rails.1...

Although, Isee ansible sync API getting called with optimized: true..Looking into the difference there.. What I see is a missing override in ansible service in katello. We want to add...

Looking at the changes, I remember some discussions around the refactoring in the PR. I haven't had a chance to look at this closely but a lot of it is...

Everything looks good here..Was able to go through the general CV workflows with container push repos. One note above which is because after deleting the product, I was left with...

Will retrace the steps but I think it wa the library push repo without any CVs that I tried deleting first and it left the library repo in pulp.

So I tried reproducing and it happens only when the repo push actually fails. For ex: I tried a push with a v1 manifest podman pull quay.io/aptible/hello-world . That created...

I think there is a workflow that leads to an orphaned pulp repo. If you push a container repo, publish it in a CV version and then delete the repository...