You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Azure is used as the cloud provider for backup storage, the account name is used to construct the endpoint URL. For example, if the account name were foo, the TLD for the endpoint URL would be foo.blob.core.windows.net. If the account name were not provided, then Scylla Manager wouldn't be able to construct the endpoint URL. Therefore, the account parameter is pretty much mandatory.
However, if the account parameter is not set, the SM agent does not fail gracefully with a clear error message. Instead, it tries to connect to an invalid endpoint, such as https://.blob.core.windows.net.
Steps to reproduce
On each node, ensure that the agent configuration file (/etc/scylla-manager-agent/scylla-manager-agent.yaml) does not have the account parameter configured for the Azure provider.
Execute a backup command using an Azure bucket, like the following:
The agent should provide a clear error message that the account name has not been configured, so the endpoint URL can't be constructed. For example, something like this:
The Azure account parameter is empty or not set, so the endpoint URL can't be constructed. Set it in /etc/scylla-manager-agent/scylla-manager-agent.yaml and restart the agent.
Actual results
Instead of failing with a clear error message, the backup says that the location is inaccessible:
$ sctool backup --cluster prod-cluster --cron '35 5 * * *' --name 'daily' --location azure:prodbucket --retention 10 --dry-run
NOTICE: this may take a while, we are performing disk size calculations on the nodes
Error: get backup target: location is not accessible
10.175.0.4: giving up after 2 attempts: after 30s: context deadline exceeded
Trace ID: 2_bjbc54Rm6BBvzDIWvV9w (grep in scylla-manager logs)
And the systemd journal on the agent shows a long stack trace with the reason for the failure hidden in it:
Description
When Azure is used as the cloud provider for backup storage, the account name is used to construct the endpoint URL. For example, if the account name were
foo
, the TLD for the endpoint URL would befoo.blob.core.windows.net
. If the account name were not provided, then Scylla Manager wouldn't be able to construct the endpoint URL. Therefore, theaccount
parameter is pretty much mandatory.However, if the
account
parameter is not set, the SM agent does not fail gracefully with a clear error message. Instead, it tries to connect to an invalid endpoint, such ashttps://.blob.core.windows.net
.Steps to reproduce
On each node, ensure that the agent configuration file (
/etc/scylla-manager-agent/scylla-manager-agent.yaml
) does not have theaccount
parameter configured for the Azure provider.Execute a backup command using an Azure bucket, like the following:
The backup should fail.
The reason for the failure is hidden within, but it isn't very clear. See below for details.
account
parameter is configured:This time, the backup should succeed.
Expected results
The agent should provide a clear error message that the account name has not been configured, so the endpoint URL can't be constructed. For example, something like this:
Actual results
Instead of failing with a clear error message, the backup says that the location is inaccessible:
And the systemd journal on the agent shows a long stack trace with the reason for the failure hidden in it:
The text was updated successfully, but these errors were encountered: