#12859 Fix a few permissions in ostree repo
Closed: Fixed by jnsamyak. Opened by dustymabe.

  • Describe the issue

The coreos-ostree-importer is throwing me some informational log messages:

2025-08-02 15:26:27,528 WARNING builtins - Directory /mnt/koji/compose/ostree/repo/refs/heads/fedora/42/aarch64/updates does not have rwx+setgid group permissions!
2025-08-02 15:26:27,528 WARNING builtins - Directory /mnt/koji/compose/ostree/repo/refs/heads/fedora/42/x86_64/updates does not have rwx+setgid group permissions!
XXX: Found directories with unexpected permissions/ownership
XXX: For more information see https://pagure.io/releng/issue/8811

Can we get those permissions updated on those directories?

  • When do you need this? (YYYY/MM/DD)

Not urgent.

  • When is this no longer needed or useful? (YYYY/MM/DD)

  • If we cannot complete your request, what is the impact?

Please check https://www.fedorastatus.org/ for any known
outages before filing issues on an outage.


Metadata Update from @jnsamyak:
- Issue tagged with: low-gain, low-trouble, ops

So I tried looking into it:

/mnt/koji/compose/ostree/repo/refs/heads/fedora/41:
total 20
drwxrwsr-x  5 ftpsync ftpsync 4096 Aug 16  2024 .
drwxrwsr-x 24 ftpsync ftpsync 4096 Feb  4 22:03 ..
drwxrwsr-x  4 ftpsync ftpsync 4096 Oct 28  2024 aarch64
drwxrwsr-x  4 ftpsync ftpsync 4096 Oct 28  2024 ppc64le
drwxrwsr-x  4 ftpsync ftpsync 4096 Oct 28  2024 x86_64
/mnt/koji/compose/ostree/repo/refs/heads/fedora/42:
total 16
drwxrwsr-x  4 ftpsync ftpsync 4096 Feb  4 22:06 .
drwxrwsr-x 24 ftpsync ftpsync 4096 Feb  4 22:03 ..
drwxrwsr-x  4 ftpsync ftpsync 4096 Apr 11 11:49 aarch64
drwxrwsr-x  4 ftpsync ftpsync 4096 Apr 11 11:49 x86_64

This looks same for all above, will dig more to see what's happening?

Metadata Update from @jnsamyak:
- Issue assigned to jnsamyak

Looked into the previous ticket - and it helped!

mode of './42/aarch64/updates' changed from 2755 (rwxr-sr-x) to 2775 (rwxrwsr-x)
mode of './42/x86_64/updates' changed from 2755 (rwxr-sr-x) to 2775 (rwxrwsr-x)

This should be fixed now!

Metadata Update from @jnsamyak:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Thanks!

Metadata