I've got a CloudBoost appliance running 2.2.3 in Azure.

I'm unable to assign a cloud profile, as the validation of the profile fails (and trying to reploy gives a generic jclouds error).

Looking at in the /var/log/jclouds.log I see the following error:

2018-04-11T18:31:09.902+0000 [main] WARN  blobstore.cli.BlobstoreCli - Failed in command: blobstore.cli.commands.ContainerCreate@19ae6bb, request: HEAD https://xxxxx.blob.core.windows.net/mag-test-1523471468-jokwif?restype=container HTTP/1.1 failed with response: HTTP/1.1 403 Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.

Any suggestions would be appreciated.  The key itself works fine, and I've tried re-generating new ones as well.

One suggestion was the time could be out, but the clock is synced via NTP:

admin@mag-fs> ntp timedrift

Enabled NTP servers are : 0.europe.pool.ntp.org, 1.europe.pool.ntp.org

remote           refid      st t when poll reach   delay   offset  jitter

==============================================================================

*time.sunrise.ne 10.17.10.20      2 u   35   64  377   17.200   -2.701   0.355

+mica.ad-notam.n 124.216.164.14   2 u   27   64  377   18.060   -1.700   0.286

Thanks,

Adam