Uanable to create ELB security group in AWS when using IPV4 and IPV6 CIDR in LoadBalancerSourceRanges

[aaronmell]

**BUG REPORT ** (choose one):

Kubernetes version (use kubectl version):
1.10

Environment:
AWS

What happened:
Attempted to add an IPV6 and IPV4 address as a loadBalancerSourceRanges. Received the following error messages

Error creating load balancer (will retry): failed to ensure load balancer for service infrastructure/ingress-nginx-nginx-ingress-controller: error authorizing security group ingress: "InvalidParameterValue: CIDR block IPV6_CIDR is malformed\n

IPV6_CIDR in loadBalancerSourceRanges has incorrect IP version

What you expected to happen:
The load balancer to be created with the security rule that allows an iPV6 and IPV4 address inbound

How to reproduce it (as minimally and precisely as possible):
add a IPV6 address and an IPV4 address as a loadBalancerSourceRanges on an ingress controller setup for AWS ELB

Anything else we need to know:

[aaronmell]

@kubernetes/sig-aws-bugs

[k8s-ci-robot]

@aaronmell: Reiterating the mentions to trigger a notification:
@kubernetes/sig-aws-bugs

In response to this:

@kubernetes/sig-aws-bugs

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dusansusic]

I have this issue, too.