Improvements to Pelican Plugin Error Messages

[jhiemstrawisc]

Pelican Service:

• Plugin

Is your feature request related to a problem? Please describe.
A user recently gave us a list of errors they were getting from the pelican plugin in the OSPool. In particular, the error appeared to be related to a network issue at the site:

Problem initializing the Pelican Client configuration:
Failure when doing federation metadata lookup to https://osg-htc.org/.well-known/pelican-
configuration: Get "https://osg-htc.org/.well-known/pelican-configuration": context deadline
exceeded (Client.Timeout exceeded while awaiting headers) (5s since start)

It would be tremendously useful if this type of error message from the plugin included the site name/hostname so that we could track potentially buggy sites and direct users away from them.

Describe the solution you'd like
Plugin error messages include information about the site that generated the error.

From talking with Rachel, there are a few more action items for this issue that should be tagged on:

• Having all errors start with PELICAN CLIENT ERROR: so RCF's can notice this easier and know it is an issue with the plugin
• Clear separators within the errors for PELICAN CLIENT ERROR, SITENAME, and HOSTNAME. All caps is good enough to really help the facilitators.