fedora-infrastructure

#9056 PDC/FAS are very unstable
Closed: Fixed by kevin. Opened by ignatenkobrain.

Closed: Fixed
Reopen Issue

Error: A failure occurred while getting a branch in PDC at https://pdc.fedoraproject.org/rest_api/v1/component-branches/?global_component=zgrab2&name=master&type=rpm. The status code was "503". The error was "".

Processing SCM requiests is PITA now due to such timeouts. I've also seen many timeouts from admin.fedoraproject.org/accounts.

I am unable to submit builds to koji due to PDC outage:

Traceback (most recent call last):
  File "/usr/bin/fedpkg", line 11, in <module>
    load_entry_point('fedpkg==1.38', 'console_scripts', 'fedpkg')()                                
  File "/usr/lib/python3.8/site-packages/fedpkg/__main__.py", line 87, in main                     
    sys.exit(client.args.command())                                                                
  File "/usr/lib/python3.8/site-packages/pyrpkg/cli.py", line 1807, in build                                                                                                                               task_id = self._build(sets=sets)
  File "/usr/lib/python3.8/site-packages/fedpkg/cli.py", line 1212, in _build                      
    stream_branches = get_stream_branches(server_url, self.cmd.repo_name)                                                                                                                              
  File "/usr/lib/python3.8/site-packages/fedpkg/utils.py", line 410, in get_stream_branches                                                                                                            
    for item in branches:                                                                          
  File "/usr/lib/python3.8/site-packages/fedpkg/utils.py", line 43, in query_pdc                                                                                                                       
    raise rpkgError(base_error_msg.format(rv.text))                                                
pyrpkg.errors.rpkgError: The following error occurred while trying to get the active release branches in PDC:
--- snip --- 8< ---
      <div id="content">
        <h2>Sorry!  This service is currently unavailable.</h2>
        <p>The service that you are trying to access is currently unavailable.  Please try refreshing this page in a couple of minutes.  If you still see this message, then please follow the steps be
low:</p>
        <ol>
          <li>Check on <a href="http://status.fedoraproject.org/">the status page</a> if there are any known outages for our services.</li>
          <li>Check the <a href="https://pagure.io/fedora-infrastructure/issues">fedora-infrastructure pagure instance</a> for an outage notification.</li>
          <li>Ask around in #fedora-admin on irc.freenode.net.</li>
          <li>If it is accessible, check the <a href="https://docs.pagure.org/infra-docs/sysadmin-guide/sops/outage.html">Outage SOP</a> for more information.</li>
        </ol>
      </div>
--- snip --- 8< ---

Metadata Update from @smooge:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: groomed, medium-gain, medium-trouble

ok. I stood up a pdc-web02 instance... so now if one is down the other should take over and the load should be spread. From logs it seems like there was only a short time this morning where it was throwing the 503s. ;(

Anyhow, I am going to close this, but if you see it happen again, please re-open and include the exact time you saw the issue so we can match it up with logs. ;)

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

medium-gain medium-trouble

None
None
Normal
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.