Over the past couple of days, I've seen dist-git deny pushes to branches randomly. Pushing again immediately after works fine.
For example:
$ git push origin --all Enumerating objects: 13, done. Counting objects: 100% (13/13), done. Delta compression using up to 4 threads Compressing objects: 100% (9/9), done. Writing objects: 100% (9/9), 1.60 KiB | 1.60 MiB/s, done. Total 9 (delta 3), reused 0 (delta 0), pack-reused 0 remote: Unspecified ref refs/heads/f34 is blocked remote: Denied push for ref 'refs/heads/f34' for user 'qulogic' remote: Unspecified ref refs/heads/f34 is blocked remote: Denied push for ref 'refs/heads/f34' for user 'qulogic' remote: All changes have been rejected remote: error: hook declined to update refs/heads/f34 remote: Emitting a message to the fedora-messaging message bus. remote: * Publishing information for 6 commits remote: * Publishing information for 2 commits remote: * Publishing information for 2 commits remote: Sending to redis to log activity and send commit notification emails remote: * Publishing information for 6 commits remote: - to fedora-message remote: 2021-09-20 00:09:41,553 [WARNING] pagure.lib.notify: pagure is about to send a message that has no schemas: pagure.git.receive remote: remote: Create a pull-request for f33 remote: https://src.fedoraproject.org/rpms/R-unitizer/diff/rawhide..f33 remote: remote: Sending to redis to log activity and send commit notification emails remote: * Publishing information for 2 commits remote: - to fedora-message remote: 2021-09-20 00:09:41,739 [WARNING] pagure.lib.notify: pagure is about to send a message that has no schemas: pagure.git.receive remote: remote: Create a pull-request for f35 remote: https://src.fedoraproject.org/rpms/R-unitizer/diff/rawhide..f35 remote: remote: Sending to redis to log activity and send commit notification emails remote: * Publishing information for 2 commits remote: - to fedora-message remote: 2021-09-20 00:09:41,827 [WARNING] pagure.lib.notify: pagure is about to send a message that has no schemas: pagure.git.receive To ssh://pkgs.fedoraproject.org/rpms/R-unitizer 819f1b2..6e6e913 f33 -> f33 54b2077..6e6e913 f35 -> f35 54b2077..6e6e913 rawhide -> rawhide ! [remote rejected] f34 -> f34 (hook declined) error: failed to push some refs to 'ssh://pkgs.fedoraproject.org/rpms/R-unitizer'
and then repeating the same works:
$ git push origin --all Total 0 (delta 0), reused 0 (delta 0), pack-reused 0 remote: Emitting a message to the fedora-messaging message bus. remote: * Publishing information for 5 commits remote: Sending to redis to log activity and send commit notification emails remote: * Publishing information for 5 commits remote: - to fedora-message remote: 2021-09-20 00:09:54,097 [WARNING] pagure.lib.notify: pagure is about to send a message that has no schemas: pagure.git.receive remote: remote: Create a pull-request for f34 remote: https://src.fedoraproject.org/rpms/R-unitizer/diff/rawhide..f34 remote: To ssh://pkgs.fedoraproject.org/rpms/R-unitizer 0b78824..6e6e913 f34 -> f34
Metadata Update from @mobrien: - Issue tagged with: low-gain, medium-trouble, ops
Metadata Update from @mobrien: - Issue priority set to: Waiting on Assignee (was: Needs Review)
@pingou any ideas here?
remote: Unspecified ref refs/heads/f34 is blocked remote: Denied push for ref 'refs/heads/f34' for user 'qulogic' remote: Unspecified ref refs/heads/f34 is blocked remote: Denied push for ref 'refs/heads/f34' for user 'qulogic' remote: All changes have been rejected remote: error: hook declined to update refs/heads/f34
This is the odd part, pagure-dist-git should be able to tell us what triggers these lines and thus what could be the cause. It is definitely weird though
I think this might be a duplicate of #10236 ?
I think this was 10236 which seems to have cleared up.
So, please re-open if you see this happening again?
Metadata Update from @kevin: - Issue close_status updated to: Insufficient data - Issue status updated to: Closed (was: Open)
Issue status updated to: Open (was: Closed)
Metadata Update from @jbley: - Issue close_status updated to: Insufficient data - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.