Event Hubs on Azure Stack Hub 1.2012.1.0 release notes

These release notes describe improvements and fixes in Event Hubs on Azure Stack Hub version 1.2012.1.0, and any known issues.

Important

Before deploying or updating the Event Hubs resource provider (RP), you may need to update Azure Stack Hub to a supported version (or deploy the latest Azure Stack Development Kit). Be sure to read the RP release notes first, to learn about new functionality, fixes, and any known issues that could affect your deployment.

Supported Azure Stack Hub version(s) Event Hubs RP release
2102 and higher 1.2102.0.0 Install | Update | Release notes
2008 and higher 1.2012.2.0 Install | Update | Release notes
2008 and higher 1.2012.1.0 Install | Update | Release notes
2005, 2008 1.2012.0.0 Install | Update

If you've installed a preview version not listed above, upgrading to one of the versions above is also recommended.

Warning

Failure to rotate secrets on a regular basis can result in your data plane clusters entering an unhealthy state, and possibly redeployment of the Event Hubs on Azure Stack Hub resource provider. As such, it is critical that you proactively rotate the secrets used by Event Hubs on Azure Stack Hub. Secrets should be rotated after completing an install/update to a new release, and on a regular basis, ideally every 6 months. Proactive rotation is required as secret expiration does not trigger administrative alerts.

Updates in this release

This release includes the following updates:

  • For Azure portal SDK developers, portal version 5.0.303.7361 is now supported.
  • Internal logging improvements for Event Hubs clusters.

Issues fixed in this release

This release includes the following fixes:

  • A fix to the upgrade order for Event Hubs clusters, to address an upgrade issue.
  • The cluster health and backup health check for Event Hubs clusters were not running when clusters were in "Upgrading" or "Upgrade Failed" state. The issue has been fixed in this release.
  • Fixed a bug causing usage records to contain the wrong quantity. Instead of cores, we were emitting capacity units (CU). Previously, a 1CU cluster would show 1 core in hourly usage. Users will now see the correct quantity of 10 cores for a 1 CU cluster in their hourly usage.

Known issues

Secret expiration doesn't trigger an alert

  • Applicable: This issue applies to all supported releases of Event Hubs on Azure Stack Hub.
  • Cause: Administrative alerts aren't currently integrated.
  • Remediation: Complete the process in How to rotate secrets for Event Hubs on Azure Stack Hubs regularly, ideally every six months.

Data plane clusters are in an unhealthy state with all nodes in warning state

  • Applicable: This issue applies to all supported releases of Event Hubs on Azure Stack Hub.
  • Cause: Internal infrastructure secrets may be nearing expiration.
  • Remediation: Update to the latest Event Hubs on Azure Stack Hub release, then complete the process in How to rotate secrets for Event Hubs on Azure Stack Hubs.

Data plane clusters' health isn't getting updated in admin portal or scale-out of clusters results in access denied

  • Applicable: This issue applies to all supported releases of Event Hubs on Azure Stack Hub.
  • Cause: Internal components haven't refreshed their cache with new secrets, after secret rotation is completed.
  • Remediation: Open a support request to receive assistance.

Azure Stack Hub backup fails

  • Applicable: This issue applies to all supported releases of Event Hubs on Azure Stack Hub.
  • Cause: Internal infrastructure secrets may have expired.
  • Remediation: Open a support request to receive assistance.

Next steps