Uploaded image for project: 'repository.jboss.org/nexus'
  1. repository.jboss.org/nexus
  2. NEXUS-229

Authentication Problem in Fusesource Quickstarts Deployment

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • Q2FY20
    • None
    • None
    • None
    • MWES 2019-06-25

      Transcript from Google Chat:

      Torsten Mielke:
      Hello David, Jon Anstey suggested to reach out to you. I have problems getting a dev build for Fuse 6.3 to succeed. Not sure you can access https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/perfectus-6.3.0/. All the builds since yesterday fail with the same error:
      "Failed to transfer file: https://repository.jboss.org/nexus/content/repositories/fs-tmp630/org/switchyard/quickstarts/switchyard-bean-service/2.1.0.redhat-630399/switchyard-bean-service-2.1.0.redhat-630399.jar. Return code is: 401, ReasonPhrase: Unauthorized."
      I checked that the three repositories
      https://origin-repository.jboss.org/nexus/content/repositories/fs-tmp630/
      https://proxy01-repository.jboss.org/nexus/content/repositories/fs-tmp630/
      https://proxy02-repository.jboss.org/nexus/content/repositories/fs-tmp630/
      are all up and runinng and don't know what else I can do to resolve the problem. Any idea on your side?
      And apologies for pinging you directly. In case you are not the right contact to ask on this kind of problem, can you recommend someone else?
      Also according to http://grafana.pnc.dynamic.host.centralci.eng.rdu2.redhat.com:3000/d/fa8Ubvumz/status?refresh=1m&orgId=1&from=now-7d&to=now all systems are up and running during the time of the builds

      David Hladky:
      Hi, no apology necessary.
      401 error means error in user credentials (missing or incorrect)

      Torsten Mielke:
      Yes but it is an intermittent error.
      Other uploads to the same site succeed

      David Hladky:
      Can you check you Maven settings, that you have the right repository identifier and the right credentials there?

      Torsten Mielke:
      Search for "Uploading" on https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/perfectus-6.3.0/776/consoleFull

      David Hladky:
      I would expect this particular build is using the old credentials
      And therefore it is unable to authenticate

      Torsten Mielke:
      No, it should not as we have seen this error many times and typically it goes away after some retries a few days later without changing any credentials on our side.

      David Hladky:
      I see.
      Thank you.

      Torsten Mielke:
      I checked with Jon Anstey on this error before and he said that he typically checks that all the three repos (listed above) are functional as we seem to get load balanced across them and sometimes one is down.

      David Hladky:
      The log then makes investigation of this particular problem possible.

      Torsten Mielke:
      But they all seem to be up.

      David Hladky:
      I will check if there was some outage on Keycloak.

      Torsten Mielke:
      Thanks.
      We see this error very regularly when building.

      David Hladky:
      If there was, it would behave exactly this way - Nexus would be functional for anonymous operations, but it would not authorize anyone

      David Hladky:
      https://issues.jboss.org/projects/NEXUS/issues/NEXUS-163?filter=allopenissues
      This is the right place for reporting similar problems

      Torsten Mielke:
      Thx, should I kick off a new build or wait until you got a chance to check?

      David Hladky:
      No. I will check the logs first if there is some clue about what was going on.

      Torsten Mielke:
      Many thanks. Whats interesting to note is that the build seems to always fail on the same artifact
      Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: https://repository.jboss.org/nexus/content/repositories/fs-tmp630/org/switchyard/quickstarts/switchyard-bean-service/2.1.0.redhat-630399/switchyard-bean-service-2.1.0.redhat-630399.jar.
      This is fairly consistent.
      while it seems to succeed on others before
      Previous builds on the same day had the same problem.

      David Hladky:
      This is a very good clue
      Just to be sure: does this particular file ever uploads?

      Torsten Mielke:
      Yes, it does eventually
      At some stage (a number of retries) the build succeeds
      Last time it took me 3-4 days of trying

              dhladky@redhat.com David Hladky
              rhn-support-tmielke Torsten Mielke
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: