#69 RFE: Imrpove the error message when centpkg tries to authenticate to kojihub.stream.centos.org (and fails)
Opened 2 years ago by churchyard. Modified a year ago

A teammate was confused by this output:

$ centpkg build
NO SCRATCH BUILD
Only scratch builds are allowed without internal configurations
Exiting
(gssapi auth failed: requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: https://kojihub.stream.centos.org/kojihub/ssllogin)
Use following documentation to debug kerberos/gssapi auth issues. https://docs.pagure.org/koji/kerberos_gssapi_debug/
Kerberos authentication fails: unable to obtain a session (gssapi auth failed: requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: https://kojihub.stream.centos.org/kojihub/ssllogin)
Use following documentation to debug kerberos/gssapi auth issues. https://docs.pagure.org/koji/kerberos_gssapi_debug/
Could not execute build: Could not login to https://kojihub.stream.centos.org/kojihub

They debugged their Kerberos config, which was a red flag. Insatlling rhel-packager helped.

Could the output perhaps be something like this instead:

$ centpkg build
NO SCRATCH BUILD
Only scratch builds are allowed without internal (Red Hat) configuration.
Hint: Install the rhel-packager package from https://copr.fedorainfracloud.org/coprs/james/centpkg if you want to build the package via internal (Red Hat) configuration.
Exiting
(Absolutely no Kerberos-related error here)

off-topic question: How do I actually authenticate to kojihub.stream.centos.org directly without internal (Red Hat) configuration to perform a sctrathcbuild?

+1 for this proposal, I've seen many folks spending too much time debugging this error.

Metadata Update from @tdawson:
- Issue assigned to tdawson

2 years ago

off-topic question: How do I actually authenticate to kojihub.stream.centos.org directly without internal (Red Hat) configuration to perform a sctrathcbuild?

If I have my normal Red Hat kerberos authentication, and do not have any of the internal configs provided by rhel-packager, I am able to submit scratch builds.
It's possible that I have different privileges than others, but I think that is all you need.

Adddressed in this pull request - https://git.centos.org/centos/centpkg/pull-request/70
If there is no internal configuration it now says this.

NO INTERNAL CONFIGURATION
Only scratch builds are allowed without internal configurations
Hint: Install the rhel-packager package from https://download.devel.redhat.com/rel-eng/RCMTOOLS/latest-RCMTOOLS-2-RHEL-9/compose/BaseOS/x86_64/os/Packages/ if you want to build the package via internal (Red Hat) configuration.
Exiting

How does that sound?

I've never encountered the https://download.devel.redhat.com/rel-eng/RCMTOOLS/latest-RCMTOOLS-2-RHEL-9/compose/BaseOS/x86_64/os/Packages/ link but it appears that I can install the package from there just fine even on Fedora. If that is the proper place to grab the package, please update internal documentation (RHEl Development Guide) as well.


Other than that, sounds great.

I've never encountered the https://download.devel.redhat.com/rel-eng/RCMTOOLS/latest-RCMTOOLS-2-RHEL-9/compose/BaseOS/x86_64/os/Packages/ link but it appears that I can install the package from there just fine even on Fedora. If that is the proper place to grab the package, please update internal documentation (RHEl Development Guide) as well.

Yes, that is where rhel-packager is officially being released now.
Since the rpm is simply putting two config files in place, it really doesn't matter if it was built for RHEL or Fedora. I chose the RHEL-9 link, because sometimes RCMTOOLS get's a little behind on the Fedora branches.
Good point about updating the RHEL Development guide. Doing that right now.

Metadata Update from @tdawson:
- Issue tagged with: Feature Request

a year ago

Log in to comment on this ticket.

Metadata