Stickiness type 'lb_cookie' is not supported for target groups with the TCP protocol(unable to disable stickiness not supported in NLB)

[ghost]

SUMMARY

We are using Ansible 2.5 to deploy AWS resources in our environment. From March 02, 2019 our deployment is failing with the below error.

ERROR:

TASK [immutable_server : target group for analytics-tst-plebos loadbalancer] ***
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: InvalidConfigurationRequestException:
An error occurred (InvalidConfigurationRequest) when calling the ModifyTargetGroupAttributes operation:
Stickiness type 'lb_cookie' is not supported for target groups with the TCP protocol
17:21:08 fatal: [localhost]: FAILED! => {"changed": false, "error": {"code": "InvalidConfigurationRequest", "message": "Stickiness type 'lb_cookie'
is not supported for target groups with the TCP protocol", "type": "Sender"}, "msg": "An error occurred (InvalidConfigurationRequest)
when calling the ModifyTargetGroupAttributes operation: Stickiness type 'lb_cookie' is not supported for target groups with the TCP protocol",
"response_metadata": {"http_headers": {"connection": "close", "content-length": "359", "content-type": "text/xml", "date": "Tue, 03 Mar 2020 11:51:08 GMT",
"x-amzn-requestid": "23b0ca87-e0fb-4b84-b93b-ae5b1363df53"}, "http_status_code": 400, "request_id": "23b0ca87-e0fb-4b84-b93b-ae5b1363df53", "retry_attempts": 0}}

ISSUE TYPE

• Bug Report - Unable to disable stickiness not supported in NLB

COMPONENT NAME

• name: "target group for {{ server_name }} loadbalancer"
  elb_target_group:
  state: present
  name: "{{ server_name }}-elb"
  protocol: tcp
  port: 80
  target_type: instance
  deregistration_delay_timeout: 35
  modify_targets: False
  vpc_id: "{{ vpc_out.vpcs.0.id }}"
  health_check_protocol: "{{ load_balancer_ping_protocol | default('http') }}"
  health_check_port: "{{ load_balancer_ping_port | default('80') }}"
  health_check_path: "{{ load_balancer_ping_path | default('/elb/ping')}}"
  health_check_interval: 30
  unhealthy_threshold_count: 2
  healthy_threshold_count: 2
  stickiness_enabled: False
  tags: "{{ aws.tags_as_dict }}"
  register: target_group_out

ANSIBLE VERSION

Ansible version = 2.5.0

CONFIGURATION

- name: "target group for {{ server_name }} loadbalancer"
  elb_target_group:
    state: present
    name: "{{ server_name }}-elb"
    protocol: tcp
    port: 80
    target_type: instance
    deregistration_delay_timeout: 35
    modify_targets: False
    vpc_id: "{{ vpc_out.vpcs.0.id }}"
    health_check_protocol: "{{ load_balancer_ping_protocol | default('http') }}"
    health_check_port: "{{ load_balancer_ping_port | default('80') }}"
    health_check_path: "{{ load_balancer_ping_path | default('/elb/ping')}}"
    health_check_interval: 30
    unhealthy_threshold_count: 2
    healthy_threshold_count: 2
    stickiness_enabled: False
    tags: "{{ aws.tags_as_dict }}"
  register: target_group_out

OS / ENVIRONMENT

Ubuntu 18.04 LTS / AWS environment

STEPS TO REPRODUCE

Kindly use the below playbook to deploy loadbalancer using Ansible on AWS cloud.

- name: "target group for {{ server_name }} loadbalancer"
  elb_target_group:
    state: present
    name: "{{ server_name }}-elb"
    protocol: tcp
    port: 80
    target_type: instance
    deregistration_delay_timeout: 35
    modify_targets: False
    vpc_id: "{{ vpc_out.vpcs.0.id }}"
    health_check_protocol: "{{ load_balancer_ping_protocol | default('http') }}"
    health_check_port: "{{ load_balancer_ping_port | default('80') }}"
    health_check_path: "{{ load_balancer_ping_path | default('/elb/ping')}}"
    health_check_interval: 30
    unhealthy_threshold_count: 2
    healthy_threshold_count: 2
    stickiness_enabled: False
    tags: "{{ aws.tags_as_dict }}"
  register: target_group_out

EXPECTED RESULTS

An AWS Network loadbalancer will be created.

ACTUAL RESULTS

The deployment fails with below error.

 TASK [immutable_server : target group for analytics-tst-plebos loadbalancer] ***
17:21:08 An exception occurred during task execution. To see the full traceback, use -vvv. The error was: InvalidConfigurationRequestException:
An error occurred (InvalidConfigurationRequest) when calling the ModifyTargetGroupAttributes operation: 
Stickiness type 'lb_cookie' is not supported for target groups with the TCP protocol
17:21:08 fatal: [localhost]: FAILED! => {"changed": false, "error": {"code": "InvalidConfigurationRequest", "message": "Stickiness type 'lb_cookie'
is not supported for target groups with the TCP protocol", "type": "Sender"}, "msg": "An error occurred (InvalidConfigurationRequest) 
when calling the ModifyTargetGroupAttributes operation: Stickiness type 'lb_cookie' is not supported for target groups with the TCP protocol", 
"response_metadata": {"http_headers": {"connection": "close", "content-length": "359", "content-type": "text/xml", "date": "Tue, 03 Mar 2020 11:51:08 GMT", 
"x-amzn-requestid": "23b0ca87-e0fb-4b84-b93b-ae5b1363df53"}, "http_status_code": 400, "request_id": "23b0ca87-e0fb-4b84-b93b-ae5b1363df53", "retry_attempts": 0}}

References

I can see a similar issue occurred for terraform users as well.

hashicorp/terraform-provider-aws#10494

[ansibot]

Files identified in the description:

• lib/ansible/modules/cloud/amazon/elb_target_group.py
• lib/ansible/modules/cloud/openstack/os_loadbalancer.py
• lib/ansible/modules/system/ping.py

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

[ansibot]

cc @Shrews @cloudnull @dagnello @emonty @gtema @jillr @juliakreger @lingxiankong @mnaser @odyssey4me @rcarrillocruz @s-hertel @tremble @wimnat
click here for bot help

[ansibot]

@srikark16, just so you are aware we have a dedicated Working Group for aws.
You can find other people interested in this in #ansible-aws on Freenode IRC
For more information about communities, meetings and agendas see https://github.com/ansible/community

click here for bot help

[mkrizek]

!component -lib/ansible/modules/system/ping.py

[ansibot]

Files identified in the description:

• lib/ansible/modules/cloud/amazon/elb_target_group.py
• lib/ansible/modules/cloud/openstack/os_loadbalancer.py

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

[Sodki]

The same is happening to me with Ansible 2.9.

[Sodki]

I tried putting a random value for stickiness_type and got the following error:

Couldn't delete target group: An error occurred (ValidationError) when calling the ModifyTargetGroupAttributes operation: 'Stickiness type' must be one of [lb_cookie, source_ip]

So it seems that lb_cookie is not the only valid option, unlike what the documentation says. Using the following workaround worked for me:

stickiness_type: source_ip

[ghost]

Thank you Henrique Rodrigues!!!
The work around you have provided worked for me.

Regards,
Srikar

[thomaszooman]

setting stickiness_enabled: no not working also.

[antoineserrano]

Adding both stickiness_enable: no and stickiness_type: source_ip did the trick for us, using Ansible 2.9.6.