Fix single security group in provisioning

[alexander-demicev]

This PR fixes issue with selecting security groups in provisioning. Security groups are not required to perform provisioning and it is not possible to leave field empty when there was only one security group in list. Requires restarting memcached and running bin/update.

ManageIQ/manageiq-providers-openstack#178

[alexander-demicev]

ping @aufi @skateman @agrare

[skateman]

Note for testing: you need a bin/update

[agrare]

@AlexanderZagaynov can you confirm for Amazon and @aufi for OpenStack?

[AlexanderZagaynov]

It's impossible to go without security group in AWS: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html#default-security-group

[alexander-demicev]

@AlexanderZagaynov @agrare Ok, I will remove it then, but there is still :required: false in yaml.

[miq-bot]

Checked commit alexander-demicev@500726e with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0
0 files checked, 0 offenses detected
Everything looks fine. 🏆

[skateman]

@alexander-demichev I think you should set the required field too then, maybe in a separate PR...ask the others' opinion 😉

[agrare]

Yeah I agree @skateman ... @AlexanderZagaynov if we should be setting requred: true for amazon can you post a PR to do that?

[aufi]

Tested, works for me 👍

OpenStack doesn't require a Security Group for provisioning Instance - https://developer.openstack.org/api-ref/compute/#create-server

[agrare]

Thanks @alexander-demichev !