Skip to content

Conversation

bavshin-f5
Copy link
Member

Some failures can be addressed by a configuration change, so we need to reschedule updates for the inherited failed orders after reload.

Some failures can be addressed by a configuration change, so we need to
reschedule updates for the inherited failed orders after reload.
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR addresses a bug where failed certificate orders maintain their next update time after a reload, preventing proper rescheduling. The fix ensures that pending certificates get their next update time reset to the default value during cloning operations.

  • Reset next update time for pending certificates to allow immediate rescheduling
  • Maintain existing next update time for ready certificates
  • Refactor state assignment to handle both state and next update time together

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@bavshin-f5 bavshin-f5 merged commit ce4a2f6 into nginx:main Oct 7, 2025
15 checks passed
@bavshin-f5 bavshin-f5 deleted the reset-next-on-reload branch October 7, 2025 00:58
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.

3 participants