Pavel Raiskup

``` 14:40:50 ~$ podman --version podman version 4.3.1 14:40:53 ~$ rpm -q podman podman-4.3.1-1.fc37.x86_64 ```

Also note that I'm not quite sure I'm using [the right image](https://github.com/pulp/pulpproject.org/pull/449).

Looks promising, thanks! ``` [root@21e381ccf81f /]# ls -la /etc/pulp/ total 12 drwx------. 3 root root 80 Jan 10 09:19 . drwxr-xr-x. 72 root root 4096 Dec 23 01:32 .. drwxr-xr-x....

Indeed, I temporarily switched umask from 0077 to 0022, and recreated from scratch. That helped. Could the permissions be fixed automatically? I can see some tasks like: fix-attrs: warning: fix-attrs...

Also: ``` [2023-01-10 09:42:18 +0000] [12692] [ERROR] Exception in gunicorn worker Traceback (most recent call last): File "/usr/local/lib64/python3.8/site-packages/aiohttp/worker.py", line 57, in run self.loop.run_until_complete(self._task) File "/usr/lib64/python3.8/asyncio/base_events.py", line 616, in run_until_complete return...

> So, my opinion is that maybe sometimes it takes more time to initialize the entire pulp, hence the errors. Could you give it more time please ? Ok, thanks...

> it was interesting because few libs and python3-something packages were in newer versions from that ovirt repo that i had If the external repo is hosted in Fedora Copr,...

@ggainey wrote: > My thought on upload is is to assume the user knows what they're doing [snip]. So "incoming" always wins. The one being-replaced is still in the Pulp...

Hello folks, thank you for the update here. > So, a quick summary of some of the more tricky requirements / problems here: > > * The simplest approach would...

Sounds good, just ad 1., note we have ~122000 keys ATM, so the DB needs to be fairly optimal. Is there some queue of pending tasks of this kind? So...