#7295 pdc.stg: component-branches
Closed: Fixed a year ago Opened a year ago by otaylor.

The ACL code for src.fedoraproject.org (perhaps just the new ACL code currently on staging) looks at https://pdc.stg.fedoraproject.org/rest_api/v1/component-branches in order to figure out what release branches are allowed to push to. But it seems like the component branches in staging aren't updated when git is synced is synced prod => stg. So, e.g.:


Doesn't have a f29 branch, even though it's in:


And it's impossible to push to the f29 branch in staging. (Which I need to do to get a runtime building- if fixing this comprehensively is too hard for now - just adding that one branch in staging PDC would let me move forward. Is that something that releng is able to do?)

We have a playbook to sync prod pdc to stage pdc. Would that do it?

We have a playbook to sync prod pdc to stage pdc. Would that do it?

It would be fine from my perspective - I don't know if there's any locally modified data in the PDC that someone else is counting on. What we discussed on irc was for @mohanboddu to just add the one branch I needed in manually as a minimal tweak.

Thanks @mohanboddu! Unfortunately, doesn't fix the underlying problem:

$ git push origin f29
Counting objects: 6, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 745 bytes | 372.00 KiB/s, done.
Total 6 (delta 4), reused 0 (delta 0)
remote: FATAL: W refs/heads/f29 modules/flatpak-runtime otaylor DENIED by refs/heads/f[0-9][0-9]
remote: error: hook declined to update refs/heads/f29
To ssh://pkgs.stg.fedoraproject.org/modules/flatpak-runtime
 ! [remote rejected] f29 -> f29 (hook declined)
error: failed to push some refs to 'ssh://otaylor@pkgs.stg.fedoraproject.org/modules/flatpak-runtime'

Unclear where that f[0-9][0-9] regex is coming from - no matches is fedora-infrastructure-ansible. so that will take some more debugging.

Metadata Update from @bowlofeggs:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: staging

a year ago

Once the branch is created in pdc, the repo permission in gitolite needs to be re-freshed, that's the piece missing here

I ran a regenerate on that repos gitolite...

OK, pushing to the f29 branch works now - thanks!

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

a year ago

Login to comment on this ticket.