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

fix: retry on alreadyReplaced error #2475

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ldez
Copy link
Member

@ldez ldez commented Mar 9, 2025

@ldez ldez added bug area/ari ACME Renewal Information Extension labels Mar 9, 2025
@ldez ldez added this to the unreleased milestone Mar 9, 2025
@ldez ldez requested a review from dmke March 9, 2025 15:43
@ldez
Copy link
Member Author

ldez commented Mar 9, 2025

I have a problem: the RFC is talking about alreadyReplaced type

But Boulder has no reference of that: alreadyReplaced

letsencrypt/boulder#7385

And Pebble has also no reference: Conflict

Also, the type inside the issue is urn:ietf:params:acme:error:conflict and not urn:ietf:params:acme:error:alreadyReplaced.

So I don't know if I should follow the RFC.

@dmke WDYT?

@ldez
Copy link
Member Author

ldez commented Mar 9, 2025

Maybe @beautifulentropy could help us in this context?

@dmke
Copy link
Member

dmke commented Mar 9, 2025

Hm. I need to think about that a bit.

My gut feeling says go with the standard (even though it's still a draft).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ari ACME Renewal Information Extension bug
Development

Successfully merging this pull request may close these issues.

cannot indicate an order replaces certificate with serial <serial>, which already has a replacement order
2 participants