Skip to content

docs: add WAN Assurance Plugin 3.102 release notes#1040

Open
agrawalkaushik wants to merge 1 commit into
masterfrom
kagrawal/wan-assurance-3.102.0
Open

docs: add WAN Assurance Plugin 3.102 release notes#1040
agrawalkaushik wants to merge 1 commit into
masterfrom
kagrawal/wan-assurance-3.102.0

Conversation

@agrawalkaushik

Copy link
Copy Markdown
Contributor

No description provided.

Add release notes for version 3.102.0 covering fix for mist-agent restart loop on conductor-managed deployments (WAN-4866). Register new doc in sidebars.js.
@@ -0,0 +1,208 @@
---

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@MichaelBaj in case you're wondering - this is largely based on the other prompt we created but there are some differences in how to gather the release notes data for plugins. hence the new prompt

---
## Release 3.102.0

**Release Date:** June 5, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

need to update this - not sure where it got this from.

@MichaelBaj MichaelBaj left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Please use the correct date.


### Resolved Issues

- **WAN-4866 mist-agent enters restart loop after upgrade on conductor-managed deployments without Mist org**

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

  • WAN-4866 mist-agent enters restart loop after upgrade on conductor-managed deployments without Mist org


- **WAN-4866 mist-agent enters restart loop after upgrade on conductor-managed deployments without Mist org**

_**Resolution**_ On conductor-managed or air-gapped deployments without a Mist organization configured, the mist-agent service could enter a continuous restart loop after an SSR upgrade, generating excessive log entries and alarms. The upgrade process now preserves the pre-upgrade state of the mist-agent service, preventing unnecessary restarts.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Resolution On conductor-managed or air-gap deployments that do not have a Mist organization configured, the mist-agent service could enter a continuous restart loop after an SSR upgrade, generating excessive log entries and alarms. The upgrade process now preserves the pre-upgrade state of the mist-agent service, preventing unnecessary restarts.

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