Closed nrcxcia closed 7 years ago
This problem does NOT present itself when supplying:
storage_service_name (Optional according to docs)
Not sure how that would affect the image.
+1 This also bit me, costing me almost a whole day of work.
No matter what name you use, terraform will fail on azure claiming the name is invalid.
As soon as I added storage_service_name
the problem went away.
At the very least, this should be in the documentation.
Guys, something related, I was trying to deploy CoreOS with specific version, I find it by azure-cli something like this: 2b171e93f07c4903bcad35bda10acf22__CoreOS-Alpha-870.3.0
If I put this in tf I got above error msg. But put in "CoreOS Alpha" does work, so how do we specify the version then? Apparently in above msg we got tons of CoreOS Alpha there which all look the same. :)
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
When using the azure provider to setup an instance, no matter what image label I provide it can not find it. Even when I supply an image label that it says is available in the error output it then proceeds to return a different set of images that it says are "available". Here is my code:
Here is the error that is returned: