Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Try three times to get the CRL. #354

Merged
merged 1 commit into from Oct 6, 2015
Merged

Try three times to get the CRL. #354

merged 1 commit into from Oct 6, 2015

Conversation

ralphbean
Copy link
Contributor

I've gotten reports from multiple people in recent weeks that their fedmsg
scripts fail and exit when something happens and they are unable to pull down
the CRL. We're not sure why that's failing yet. It may be a network blip, or
it may be a proxy issue. In the meantime, we can make fedmsg try a little
harder to get that file before it blows up on the user.

I've gotten reports from multiple people in recent weeks that their fedmsg
scripts fail and exit when *something happens* and they are unable to pull down
the CRL.  We're not sure why that's failing yet.  It may be a network blip, or
it may be a proxy issue.  In the meantime, we can make fedmsg try a little
harder to get that file before it blows up on the user.
@pypingou
Copy link
Member

pypingou commented Oct 6, 2015

👍 for me

@ralphbean
Copy link
Contributor Author

ralphbean added a commit that referenced this pull request Oct 6, 2015
@ralphbean ralphbean merged commit fb2979b into develop Oct 6, 2015
@ralphbean ralphbean deleted the feature/pesky-crl branch October 6, 2015 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants