Loading...
Loading...
Filesystem Down with Object-Store Access Failure Alert example: EVT-FILESYS-00002: Problem is preventing filesystem from running. Object-Store Profile Cannot Be Configured Command output: sysadmin # storage object-store profile set OAuth is the recommended way of authentication to the object store. Do you want to choose OAuth? (yes|no) [yes]: yes Enter the account name: mystorageaccount Enter the container name: myblob **** Cannot set profile: Server failed to authenticate the request. Please refer to the information in the www-authenticate header. This managed identity does not have the update permission. Log Errors in csm.log HTTP/1.1 401 Server failed to authenticate the request. Signature validation failed. Signature verification failed.
The object-store profile is configured to use OAuth with a user-assigned managed identity. Azure AD OAuth tokens refresh every 24 hours and vary in size based on: VM name length Resource Group name length for VM and Managed Identity Managed Identity name length Token size can exceed DDVE’s supported limit, causing authentication failures.
Permanent Fix: Planned for DDOS >=8.3.1.20 (not released at time of publishing - Expected December 2025) Workaround: Disable OAuth and use HMAC Access Key authentication. Steps: Verify the current authentication type: storage object-store profile show Example output: Authentication Type: OAuth Account name: mystorageaccountname Container name: myblobstoragecontainername Provider: Azure Change the profile to use Access Key: storage object-store profile set
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.