{"action":"created","issue":{"url":"https://api.github.com/repos/ManageIQ/manageiq-providers-azure/issues/252","repository_url":"https://api.github.com/repos/ManageIQ/manageiq-providers-azure","labels_url":"https://api.github.com/repos/ManageIQ/manageiq-providers-azure/issues/252/labels{/name}","comments_url":"https://api.github.com/repos/ManageIQ/manageiq-providers-azure/issues/252/comments","events_url":"https://api.github.com/repos/ManageIQ/manageiq-providers-azure/issues/252/events","html_url":"https://github.com/ManageIQ/manageiq-providers-azure/issues/252","id":320935518,"number":252,"title":"Azure Stack flavor names are case sensitive","user":{"login":"bsquizz","id":35474886,"avatar_url":"https://avatars1.githubusercontent.com/u/35474886?v=4","gravatar_id":"","url":"https://api.github.com/users/bsquizz","html_url":"https://github.com/bsquizz","followers_url":"https://api.github.com/users/bsquizz/followers","following_url":"https://api.github.com/users/bsquizz/following{/other_user}","gists_url":"https://api.github.com/users/bsquizz/gists{/gist_id}","starred_url":"https://api.github.com/users/bsquizz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bsquizz/subscriptions","organizations_url":"https://api.github.com/users/bsquizz/orgs","repos_url":"https://api.github.com/users/bsquizz/repos","events_url":"https://api.github.com/users/bsquizz/events{/privacy}","received_events_url":"https://api.github.com/users/bsquizz/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-05-07T19:59:01Z","updated_at":"2018-05-07T20:07:30Z","closed_at":null,"author_association":"NONE","body":"During Azure Stack testing, I tried to deploy a a private image and hit this error:\r\n\r\n```\r\n[----] E, [2018-05-07T12:27:03.581936 #5157:121f114] ERROR -- : Q-task_id([miq_provision_1]) MIQ(ManageIQ::Providers::Azure::CloudManager::Provision#provision_error) [[Azure::Armrest::BadRequestException]: The requested VM size standard_a1 is not available in the current region. The sizes available in the current region are: Basic_A0,Basic_A1,Basic_A2,Basic_A3,Basic_A4,Standard_A0,Standard_A1,Standard_A2,Standard_A3,Standard_A4,Standard_A5,Standard_A6,Standard_A7,Standard_D1,Standard_D2,Standard_D3,Standard_D4,Standard_D11,Standard_D12,Standard_D13,Standard_D14,Standard_D1_v2,Standard_D2_v2,Standard_D3_v2,Standard_D4_v2,Standard_D5_v2,Standard_D11_v2,Standard_D12_v2,Standard_D13_v2,Standard_D14_v2,Standard_DS1,Standard_DS2,Standard_DS3,Standard_DS4,Standard_DS11,Standard_DS12,Standard_DS13,Standard_DS14,Standard_DS1_v2,Standard_DS2_v2,Standard_DS3_v2,Standard_DS4_v2,Standard_DS5_v2,Standard_DS11_v2,Standard_DS12_v2,Standard_DS13_v2,Standard_DS14_v2. Find out more on the available VM sizes in each region at https://aka.ms/azure-regions.] encountered during phase [start_clone_task]\r\n```\r\n\r\nRequested vm size was 'standard_a1', and Standard_A1 is in the list. It appears that the flavor name is case sensitive for the Azure Stack APIs.\r\n\r\nWe could get around this by only storing the uid as `flavor.name.downcase` and keeping the name as-is (see https://github.com/ManageIQ/manageiq-providers-azure/compare/master...bsquizz:flavor_names), however I'm not sure if altering the display name will affect anything existing customers are doing with Azure providers. If that's the case, we may need to store another attribute (i.e. `actual_name`) alongside the downcase'd `name` and have `prepare_for_clone_task` in provision/cloning.rb use the `actual_name` for `vmSize`"},"comment":{"url":"https://api.github.com/repos/ManageIQ/manageiq-providers-azure/issues/comments/387187714","html_url":"https://github.com/ManageIQ/manageiq-providers-azure/issues/252#issuecomment-387187714","issue_url":"https://api.github.com/repos/ManageIQ/manageiq-providers-azure/issues/252","id":387187714,"user":{"login":"djberg96","id":78529,"avatar_url":"https://avatars3.githubusercontent.com/u/78529?v=4","gravatar_id":"","url":"https://api.github.com/users/djberg96","html_url":"https://github.com/djberg96","followers_url":"https://api.github.com/users/djberg96/followers","following_url":"https://api.github.com/users/djberg96/following{/other_user}","gists_url":"https://api.github.com/users/djberg96/gists{/gist_id}","starred_url":"https://api.github.com/users/djberg96/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/djberg96/subscriptions","organizations_url":"https://api.github.com/users/djberg96/orgs","repos_url":"https://api.github.com/users/djberg96/repos","events_url":"https://api.github.com/users/djberg96/events{/privacy}","received_events_url":"https://api.github.com/users/djberg96/received_events","type":"User","site_admin":false},"created_at":"2018-05-07T20:07:30Z","updated_at":"2018-05-07T20:07:30Z","author_association":"COLLABORATOR","body":"Quite silly, I would consider that a bug in the Azure API. It shouldn't care. They're already somewhat inconsistent on the issue, e.g. it ignores case for resource groups.\r\n\r\nLet me think about how we should handle it."}}
{"actor":{"display_login":"djberg96"}}