Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix ecs_cluster integration test #1145

Merged
merged 21 commits into from
May 23, 2022
Merged

fix ecs_cluster integration test #1145

merged 21 commits into from
May 23, 2022

Conversation

markuman
Copy link
Member

@markuman markuman commented May 11, 2022

SUMMARY
  • ecs_cluster: make ecs_cluster integration test work again - as it is
    • bugs I've hit and must be fixed to complete this challenge
      • ecs_taskdefinition: fix change detection of changing launch_type parameter
      • ecs_service:
        • compare of task_definition never works and results always in a changed task
        • change detect of health_check_grace_period_seconds was never implemented, but tested and failing, after the task_definition is compared correctly

ref: #1142

ISSUE TYPE
  • Bugfix Pull Request
COMPONENT NAME

ecs_taskdefinition
ecs_service

ADDITIONAL INFORMATION

basically the existing test tasks are not changed. just sorted and removed what was marked as fixme because it's simple not possible (changing network settings of a created service).

@ansibullbot
Copy link

@ansibullbot ansibullbot added bug This issue/PR relates to a bug community_review integration tests/integration module module needs_triage plugins plugin (any type) tests tests labels May 11, 2022
@softwarefactory-project-zuul
Copy link
Contributor

Build failed.

ansible-galaxy-importer FAILURE in 4m 03s (non-voting)
✔️ build-ansible-collection SUCCESS in 4m 55s
ansible-test-sanity-docker-devel FAILURE in 10m 41s (non-voting)
ansible-test-sanity-docker-milestone FAILURE in 11m 58s
ansible-test-sanity-docker-stable-2.9 FAILURE in 11m 10s
ansible-test-sanity-docker-stable-2.11 FAILURE in 10m 51s
ansible-test-sanity-docker-stable-2.12 FAILURE in 9m 49s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 6m 09s
✔️ ansible-test-splitter SUCCESS in 2m 47s
integration-community.aws-1 FAILURE in 6m 33s
⚠️ integration-community.aws-2 SKIPPED
⚠️ integration-community.aws-3 SKIPPED
⚠️ integration-community.aws-4 SKIPPED
⚠️ integration-community.aws-5 SKIPPED
⚠️ integration-community.aws-6 SKIPPED
⚠️ integration-community.aws-7 SKIPPED
⚠️ integration-community.aws-8 SKIPPED
⚠️ integration-community.aws-9 SKIPPED
⚠️ integration-community.aws-10 SKIPPED
⚠️ integration-community.aws-11 SKIPPED
⚠️ integration-community.aws-12 SKIPPED
⚠️ integration-community.aws-13 SKIPPED

@softwarefactory-project-zuul
Copy link
Contributor

Build failed.

ansible-galaxy-importer FAILURE in 4m 09s (non-voting)
✔️ build-ansible-collection SUCCESS in 5m 23s
ansible-test-sanity-docker-devel FAILURE in 9m 48s (non-voting)
ansible-test-sanity-docker-milestone FAILURE in 11m 11s
ansible-test-sanity-docker-stable-2.9 FAILURE in 12m 11s
ansible-test-sanity-docker-stable-2.11 FAILURE in 10m 43s
ansible-test-sanity-docker-stable-2.12 FAILURE in 10m 33s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 5m 58s
✔️ ansible-test-splitter SUCCESS in 2m 57s
integration-community.aws-1 FAILURE in 6m 37s
⚠️ integration-community.aws-2 SKIPPED
⚠️ integration-community.aws-3 SKIPPED
⚠️ integration-community.aws-4 SKIPPED
⚠️ integration-community.aws-5 SKIPPED
⚠️ integration-community.aws-6 SKIPPED
⚠️ integration-community.aws-7 SKIPPED
⚠️ integration-community.aws-8 SKIPPED
⚠️ integration-community.aws-9 SKIPPED
⚠️ integration-community.aws-10 SKIPPED
⚠️ integration-community.aws-11 SKIPPED
⚠️ integration-community.aws-12 SKIPPED
⚠️ integration-community.aws-13 SKIPPED

@markuman
Copy link
Member Author

AccessDeniedException

It looks like the permissions were also not sufficient

@markuman
Copy link
Member Author

AccessDeniedException

It looks like the permissions were also not sufficient

User: arn:aws:sts::966509639900:assumed-role/ansible-core-ci-test-prod/prod=remote=zuul-cloud is not authorized to perform: ecs:DescribeClusters on resource: arn:aws:ecs:us-east-1:966509639900:cluster/ansible-test-98751679-node-0002534772 because no identity-based policy allows the ecs:DescribeClusters action",

hmm https://github.com/mattclay/aws-terminator/blob/25185a54a75c4bf6edda67ad5ee55a3fd5391b0c/hacking/aws_config/test_policies/container-policy.yaml#L12-L18

Is there something wrong with - ecs:Describe*?
cc @alinabuzachis @jillr

@softwarefactory-project-zuul
Copy link
Contributor

Build failed.

ansible-galaxy-importer FAILURE in 4m 36s (non-voting)
✔️ build-ansible-collection SUCCESS in 5m 53s
✔️ ansible-test-sanity-docker-devel SUCCESS in 11m 02s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 11m 53s
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 12m 50s
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 10m 17s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 10m 17s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 6m 02s
✔️ ansible-test-splitter SUCCESS in 3m 57s
integration-community.aws-1 FAILURE in 7m 50s
⚠️ integration-community.aws-2 SKIPPED
⚠️ integration-community.aws-3 SKIPPED
⚠️ integration-community.aws-4 SKIPPED
⚠️ integration-community.aws-5 SKIPPED
⚠️ integration-community.aws-6 SKIPPED
⚠️ integration-community.aws-7 SKIPPED
⚠️ integration-community.aws-8 SKIPPED
⚠️ integration-community.aws-9 SKIPPED
⚠️ integration-community.aws-10 SKIPPED
⚠️ integration-community.aws-11 SKIPPED
⚠️ integration-community.aws-12 SKIPPED
⚠️ integration-community.aws-13 SKIPPED

@gravesm
Copy link
Member

gravesm commented May 11, 2022

@markuman As far as I am aware, the only policies that are applied are the ones in https://github.com/mattclay/aws-terminator/tree/master/aws/policy.

@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded.

ansible-galaxy-importer FAILURE in 5m 30s (non-voting)
✔️ build-ansible-collection SUCCESS in 5m 49s
✔️ ansible-test-sanity-docker-devel SUCCESS in 9m 37s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 10m 03s
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 11m 39s
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 10m 39s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 9m 51s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 7m 16s
✔️ ansible-test-splitter SUCCESS in 3m 58s
✔️ integration-community.aws-1 SUCCESS in 5m 36s
⚠️ integration-community.aws-2 SKIPPED
⚠️ integration-community.aws-3 SKIPPED
⚠️ integration-community.aws-4 SKIPPED
⚠️ integration-community.aws-5 SKIPPED
⚠️ integration-community.aws-6 SKIPPED
⚠️ integration-community.aws-7 SKIPPED
⚠️ integration-community.aws-8 SKIPPED
⚠️ integration-community.aws-9 SKIPPED
⚠️ integration-community.aws-10 SKIPPED
⚠️ integration-community.aws-11 SKIPPED
⚠️ integration-community.aws-12 SKIPPED
⚠️ integration-community.aws-13 SKIPPED

Copy link
Contributor

@alinabuzachis alinabuzachis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I run the tests locally and they pass. There are two tasks failing and masked by ignore_errors: true. Don't we also need to camelize the returned result?

TASK [ecs_cluster : create same ECS service definition (should not change)] **********************************************************
task path: /Users/alinabuzachis/dev/collections/ansible_collections/community/aws/tests/output/.tmp/integration/ecs_cluster-1n9q2tio-ÅÑŚÌβŁÈ/tests/integration/targets/ecs_cluster/tasks/full_test.yml:217
Using module file /Users/alinabuzachis/dev/collections/ansible_collections/community/aws/plugins/modules/ecs_service.py
Pipelining is enabled.
<testhost> ESTABLISH LOCAL CONNECTION FOR USER: alinabuzachis
<testhost> EXEC /bin/sh -c 'ANSIBLE_DEBUG_BOTOCORE_LOGS=True /Users/alinabuzachis/anaconda3/envs/py38/bin/python && sleep 0'
changed: [testhost] => {
    "changed": true,
    "invocation": {
        "module_args": {
            "aws_access_key": "xxx",
            "aws_ca_bundle": null,
            "aws_config": null,
            "aws_secret_key": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
            "client_token": "",
            "cluster": "ansible-test-25844396-alinas-macbook-pro",
            "debug_botocore_endpoint_logs": true,
            "delay": 10,
            "deployment_configuration": {
                "maximum_percent": 100,
                "minimum_healthy_percent": 0
            },
            "desired_count": 1,
            "ec2_url": null,
            "force_deletion": false,
            "force_new_deployment": false,
            "health_check_grace_period_seconds": 60,
            "launch_type": null,
            "load_balancers": [
                {
                    "containerName": "ansible-test-25844396-alinas-macbook-pro-task",
                    "containerPort": 8080,
                    "targetGroupArn": "xxx"
                }
            ],
            "name": "ansible-test-25844396-alinas-macbook-pro-service",
            "network_configuration": null,
            "placement_constraints": [],
            "placement_strategy": [
                {
                    "field": "memory",
                    "type": "binpack"
                },
                {
                    "field": "attribute:ecs.availability-zone",
                    "type": "spread"
                }
            ],
            "platform_version": null,
            "profile": null,
            "region": "us-east-1",
            "repeat": 10,
            "role": "ecsServiceRole",
            "scheduling_strategy": null,
            "security_token": null,
            "service_registries": [],
            "state": "present",
            "task_definition": "ansible-test-25844396-alinas-macbook-pro-task:2",
            "validate_certs": true
        }
    },
    "resource_actions": [
        "ecs:DescribeServices",
        "ecs:UpdateService"
    ],
    "service": {
        "clusterArn": "xxx",
        "createdAt": "2022-05-12 10:41:58.171000+02:00",
        "createdBy": "xxxx",
        "deploymentConfiguration": {
            "deploymentCircuitBreaker": {
                "enable": false,
                "rollback": false
            },
            "maximumPercent": 100,
            "minimumHealthyPercent": 0
        },
        "deployments": [
            {
                "createdAt": "2022-05-12 10:41:58.171000+02:00",
                "desiredCount": 1,
                "failedTasks": 0,
                "id": "ecs-svc/2450666585425580140",
                "launchType": "EC2",
                "pendingCount": 0,
                "rolloutState": "IN_PROGRESS",
                "rolloutStateReason": "ECS deployment ecs-svc/2450666585425580140 in progress.",
                "runningCount": 0,
                "status": "PRIMARY",
                "taskDefinition": "xxxx",
                "updatedAt": "2022-05-12 10:41:58.171000+02:00"
            }
        ],
        "desiredCount": 1,
        "enableECSManagedTags": false,
        "enableExecuteCommand": false,
        "events": [],
        "healthCheckGracePeriodSeconds": 60,
        "launchType": "EC2",
        "loadBalancers": [
            {
                "containerName": "ansible-test-25844396-alinas-macbook-pro-task",
                "containerPort": 8080,
                "targetGroupArn": "xxxx"
            }
        ],
        "pendingCount": 0,
        "placementConstraints": [],
        "placementStrategy": [
            {
                "field": "MEMORY",
                "type": "binpack"
            },
            {
                "field": "attribute:ecs.availability-zone",
                "type": "spread"
            }
        ],
        "propagateTags": "NONE",
        "roleArn": "xxx",
        "runningCount": 0,
        "schedulingStrategy": "REPLICA",
        "serviceArn": "xxxx",
        "serviceName": "ansible-test-25844396-alinas-macbook-pro-service",
        "serviceRegistries": [],
        "status": "ACTIVE",
        "taskDefinition": "xxxx"
    }
}

TASK [ecs_cluster : check that ECS service recreation changed nothing] ***************************************************************
task path: /Users/alinabuzachis/dev/collections/ansible_collections/community/aws/tests/output/.tmp/integration/ecs_cluster-1n9q2tio-ÅÑŚÌβŁÈ/tests/integration/targets/ecs_cluster/tasks/full_test.yml:234
fatal: [testhost]: FAILED! => {
    "assertion": "not ecs_service_again.changed",
    "changed": false,
    "evaluated_to": false,
    "msg": "Assertion failed"
}
...ignoring
TASK [ecs_cluster : attempt to use ECS network configuration on task definition without awsvpc network_mode] *************************
task path: /Users/alinabuzachis/dev/collections/ansible_collections/community/aws/tests/output/.tmp/integration/ecs_cluster-1n9q2tio-ÅÑŚÌβŁÈ/tests/integration/targets/ecs_cluster/tasks/full_test.yml:268
Using module file /Users/alinabuzachis/dev/collections/ansible_collections/community/aws/plugins/modules/ecs_service.py
Pipelining is enabled.
<testhost> EXEC /bin/sh -c 'ANSIBLE_DEBUG_BOTOCORE_LOGS=True /Users/alinabuzachis/anaconda3/envs/py38/bin/python && sleep 0'
The full traceback is:
Traceback (most recent call last):
  File "/tmp/ansible_ecs_service_payload_4uo1q45p/ansible_ecs_service_payload.zip/ansible_collections/community/aws/plugins/modules/ecs_service.py", line 780, in main
  File "/tmp/ansible_ecs_service_payload_4uo1q45p/ansible_ecs_service_payload.zip/ansible_collections/community/aws/plugins/modules/ecs_service.py", line 599, in create_service
  File "/Users/alinabuzachis/anaconda3/envs/py38/lib/python3.8/site-packages/botocore/client.py", line 415, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/Users/alinabuzachis/anaconda3/envs/py38/lib/python3.8/site-packages/botocore/client.py", line 745, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.errorfactory.InvalidParameterException: An error occurred (InvalidParameterException) when calling the CreateService operation: Network Configuration is not valid for the given networkMode of this task definition.
fatal: [testhost]: FAILED! => {
    "boto3_version": "1.21.36",
    "botocore_version": "1.24.36",
    "changed": false,
    "error": {
        "code": "InvalidParameterException",
        "message": "Network Configuration is not valid for the given networkMode of this task definition."
    },
    "invocation": {
        "module_args": {
            "aws_access_key": "xxxx",
            "aws_ca_bundle": null,
            "aws_config": null,
            "aws_secret_key": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",
            "client_token": "",
            "cluster": "ansible-test-25844396-alinas-macbook-pro",
            "debug_botocore_endpoint_logs": true,
            "delay": 10,
            "deployment_configuration": {
                "maximum_percent": 100,
                "minimum_healthy_percent": 0
            },
            "desired_count": 1,
            "ec2_url": null,
            "force_deletion": false,
            "force_new_deployment": false,
            "health_check_grace_period_seconds": null,
            "launch_type": null,
            "load_balancers": [
                {
                    "containerName": "ansible-test-25844396-alinas-macbook-pro-task",
                    "containerPort": 8080,
                    "targetGroupArn": "xxxx"
                }
            ],
            "name": "ansible-test-25844396-alinas-macbook-pro-service3",
            "network_configuration": {
                "assign_public_ip": null,
                "security_groups": [
                    "sg-0d8ba12678fc65168"
                ],
                "subnets": [
                    "subnet-0b4a9a74d9611c7b0",
                    "subnet-013a944c5684affbd"
                ]
            },
            "placement_constraints": [],
            "placement_strategy": [
                {
                    "field": "memory",
                    "type": "binpack"
                },
                {
                    "field": "attribute:ecs.availability-zone",
                    "type": "spread"
                }
            ],
            "platform_version": null,
            "profile": null,
            "region": "us-east-1",
            "repeat": 10,
            "role": "",
            "scheduling_strategy": null,
            "security_token": null,
            "service_registries": [],
            "state": "present",
            "task_definition": "ansible-test-25844396-alinas-macbook-pro-task:2",
            "validate_certs": true
        }
    },
    "msg": "Couldn't create service: An error occurred (InvalidParameterException) when calling the CreateService operation: Network Configuration is not valid for the given networkMode of this task definition.",
    "resource_actions": [
        "ecs:DescribeServices",
        "ecs:CreateService"
    ],
    "response_metadata": {
        "http_headers": {
            "connection": "close",
            "content-length": "136",
            "content-type": "application/x-amz-json-1.1",
            "date": "Thu, 12 May 2022 08:42:02 GMT",
            "x-amzn-requestid": "76f6580c-f56d-4c5d-a390-101232d10408"
        },
        "http_status_code": 400,
        "request_id": "76f6580c-f56d-4c5d-a390-101232d10408",
        "retry_attempts": 0
    }
}
...ignoring

@markuman
Copy link
Member Author

@alinabuzachis thx for test it.

create same ECS service definition (should not change)

I guess the first ignore_errors task you've mentioned might be a bug.
Mostly I keep the tasks in the integration tests as they were. Means, the ignore_errors exists before.

The second ignore_errors task

TASK [ecs_cluster : attempt to use ECS network configuration on task definition without awsvpc network_mode] *************************

I need investigate more. It might be a bug or a service limitation itself. Means, the network change miight not be possible - like changing ALB configuration (the task before).

@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded.

ansible-galaxy-importer FAILURE in 4m 10s (non-voting)
✔️ build-ansible-collection SUCCESS in 5m 00s
✔️ ansible-test-sanity-docker-devel SUCCESS in 10m 25s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 11m 29s
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 10m 50s
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 11m 35s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 10m 29s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 6m 12s
✔️ ansible-test-splitter SUCCESS in 2m 32s
✔️ integration-community.aws-1 SUCCESS in 6m 47s
⚠️ integration-community.aws-2 SKIPPED
⚠️ integration-community.aws-3 SKIPPED
⚠️ integration-community.aws-4 SKIPPED
⚠️ integration-community.aws-5 SKIPPED
⚠️ integration-community.aws-6 SKIPPED
⚠️ integration-community.aws-7 SKIPPED
⚠️ integration-community.aws-8 SKIPPED
⚠️ integration-community.aws-9 SKIPPED
⚠️ integration-community.aws-10 SKIPPED
⚠️ integration-community.aws-11 SKIPPED
⚠️ integration-community.aws-12 SKIPPED
⚠️ integration-community.aws-13 SKIPPED

@markuman markuman added backport-2 PR should be backported to the stable-2 branch backport-3 PR should be backported to the stable-3 branch labels May 19, 2022
@ansibullbot
Copy link

@softwarefactory-project-zuul
Copy link
Contributor

Build failed.

ansible-galaxy-importer FAILURE in 3m 58s (non-voting)
✔️ build-ansible-collection SUCCESS in 5m 01s
ansible-test-sanity-docker-devel FAILURE in 9m 17s (non-voting)
ansible-test-sanity-docker-milestone FAILURE in 11m 31s
ansible-test-sanity-docker-stable-2.9 FAILURE in 12m 36s
ansible-test-sanity-docker-stable-2.11 FAILURE in 11m 02s
ansible-test-sanity-docker-stable-2.12 FAILURE in 12m 17s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 7m 14s
✔️ ansible-test-splitter SUCCESS in 2m 39s
✔️ integration-community.aws-1 SUCCESS in 6m 22s
⚠️ integration-community.aws-2 SKIPPED
⚠️ integration-community.aws-3 SKIPPED
⚠️ integration-community.aws-4 SKIPPED
⚠️ integration-community.aws-5 SKIPPED
⚠️ integration-community.aws-6 SKIPPED
⚠️ integration-community.aws-7 SKIPPED
⚠️ integration-community.aws-8 SKIPPED
⚠️ integration-community.aws-9 SKIPPED
⚠️ integration-community.aws-10 SKIPPED
⚠️ integration-community.aws-11 SKIPPED
⚠️ integration-community.aws-12 SKIPPED
⚠️ integration-community.aws-13 SKIPPED

@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded.

ansible-galaxy-importer FAILURE in 5m 33s (non-voting)
✔️ build-ansible-collection SUCCESS in 5m 42s
✔️ ansible-test-sanity-docker-devel SUCCESS in 10m 26s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 9m 18s
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 12m 27s
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 11m 21s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 9m 56s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 6m 13s
✔️ ansible-test-splitter SUCCESS in 2m 29s
✔️ integration-community.aws-1 SUCCESS in 7m 32s
⚠️ integration-community.aws-2 SKIPPED
⚠️ integration-community.aws-3 SKIPPED
⚠️ integration-community.aws-4 SKIPPED
⚠️ integration-community.aws-5 SKIPPED
⚠️ integration-community.aws-6 SKIPPED
⚠️ integration-community.aws-7 SKIPPED
⚠️ integration-community.aws-8 SKIPPED
⚠️ integration-community.aws-9 SKIPPED
⚠️ integration-community.aws-10 SKIPPED
⚠️ integration-community.aws-11 SKIPPED
⚠️ integration-community.aws-12 SKIPPED
⚠️ integration-community.aws-13 SKIPPED

@markuman markuman changed the title fix ecs_cluster integration test; fix ecs_taskdefinition change detection fix ecs_cluster integration test May 19, 2022
@markuman
Copy link
Member Author

@alinabuzachis I've made some more clean-ups and hits some more bugs.
can you review and retry the integration test locally please?

@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded.

ansible-galaxy-importer FAILURE in 3m 59s (non-voting)
✔️ build-ansible-collection SUCCESS in 5m 23s
✔️ ansible-test-sanity-docker-devel SUCCESS in 11m 03s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 9m 49s
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 11m 35s
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 12m 38s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 11m 08s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 6m 27s
✔️ ansible-test-splitter SUCCESS in 2m 33s
✔️ integration-community.aws-1 SUCCESS in 6m 43s
⚠️ integration-community.aws-2 SKIPPED
⚠️ integration-community.aws-3 SKIPPED
⚠️ integration-community.aws-4 SKIPPED
⚠️ integration-community.aws-5 SKIPPED
⚠️ integration-community.aws-6 SKIPPED
⚠️ integration-community.aws-7 SKIPPED
⚠️ integration-community.aws-8 SKIPPED
⚠️ integration-community.aws-9 SKIPPED
⚠️ integration-community.aws-10 SKIPPED
⚠️ integration-community.aws-11 SKIPPED
⚠️ integration-community.aws-12 SKIPPED
⚠️ integration-community.aws-13 SKIPPED

@github-actions
Copy link

github-actions bot commented May 23, 2022

Docs Build 📝

Thank you for contribution!✨

This PR has been merged and your docs changes will be incorporated when they are next published.

@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded.

ansible-galaxy-importer FAILURE in 4m 20s (non-voting)
✔️ build-ansible-collection SUCCESS in 4m 59s
✔️ ansible-test-sanity-docker-devel SUCCESS in 10m 00s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 10m 22s
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 11m 17s
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 10m 01s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 11m 05s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 6m 03s
✔️ ansible-test-splitter SUCCESS in 2m 22s
✔️ integration-community.aws-1 SUCCESS in 6m 35s
⚠️ integration-community.aws-2 SKIPPED
⚠️ integration-community.aws-3 SKIPPED
⚠️ integration-community.aws-4 SKIPPED
⚠️ integration-community.aws-5 SKIPPED
⚠️ integration-community.aws-6 SKIPPED
⚠️ integration-community.aws-7 SKIPPED
⚠️ integration-community.aws-8 SKIPPED
⚠️ integration-community.aws-9 SKIPPED
⚠️ integration-community.aws-10 SKIPPED
⚠️ integration-community.aws-11 SKIPPED
⚠️ integration-community.aws-12 SKIPPED
⚠️ integration-community.aws-13 SKIPPED

@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded.

ansible-galaxy-importer FAILURE in 4m 08s (non-voting)
✔️ build-ansible-collection SUCCESS in 4m 46s
✔️ ansible-test-sanity-docker-devel SUCCESS in 11m 10s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 10m 12s
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 12m 42s
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 11m 56s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 9m 20s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 6m 50s
✔️ ansible-test-splitter SUCCESS in 2m 38s
✔️ integration-community.aws-1 SUCCESS in 6m 31s
⚠️ integration-community.aws-2 SKIPPED
⚠️ integration-community.aws-3 SKIPPED
⚠️ integration-community.aws-4 SKIPPED
⚠️ integration-community.aws-5 SKIPPED
⚠️ integration-community.aws-6 SKIPPED
⚠️ integration-community.aws-7 SKIPPED
⚠️ integration-community.aws-8 SKIPPED
⚠️ integration-community.aws-9 SKIPPED
⚠️ integration-community.aws-10 SKIPPED
⚠️ integration-community.aws-11 SKIPPED
⚠️ integration-community.aws-12 SKIPPED
⚠️ integration-community.aws-13 SKIPPED

@markuman markuman requested a review from jatorcasso May 23, 2022 12:14
Copy link
Contributor

@jatorcasso jatorcasso left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@markuman markuman removed the request for review from alinabuzachis May 23, 2022 17:13
@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded.

ansible-galaxy-importer FAILURE in 4m 54s (non-voting)
✔️ build-ansible-collection SUCCESS in 5m 02s
✔️ ansible-test-sanity-docker-devel SUCCESS in 10m 13s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 10m 42s
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 13m 07s
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 10m 47s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 10m 45s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 5m 53s
✔️ ansible-test-splitter SUCCESS in 2m 23s
✔️ integration-community.aws-1 SUCCESS in 6m 46s
⚠️ integration-community.aws-2 SKIPPED
⚠️ integration-community.aws-3 SKIPPED
⚠️ integration-community.aws-4 SKIPPED
⚠️ integration-community.aws-5 SKIPPED
⚠️ integration-community.aws-6 SKIPPED
⚠️ integration-community.aws-7 SKIPPED
⚠️ integration-community.aws-8 SKIPPED
⚠️ integration-community.aws-9 SKIPPED
⚠️ integration-community.aws-10 SKIPPED
⚠️ integration-community.aws-11 SKIPPED
⚠️ integration-community.aws-12 SKIPPED
⚠️ integration-community.aws-13 SKIPPED

@markuman markuman added the mergeit Merge the PR (SoftwareFactory) label May 23, 2022
@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded (gate pipeline).

ansible-galaxy-importer FAILURE in 3m 37s (non-voting)
✔️ build-ansible-collection SUCCESS in 5m 15s
✔️ ansible-test-sanity-docker-devel SUCCESS in 10m 23s (non-voting)
✔️ ansible-test-sanity-docker-milestone SUCCESS in 9m 41s
✔️ ansible-test-sanity-docker-stable-2.9 SUCCESS in 13m 01s
✔️ ansible-test-sanity-docker-stable-2.11 SUCCESS in 10m 42s
✔️ ansible-test-sanity-docker-stable-2.12 SUCCESS in 10m 49s
✔️ ansible-test-units-community-aws-python38 SUCCESS in 5m 53s
✔️ ansible-test-splitter SUCCESS in 2m 38s
✔️ integration-community.aws-1 SUCCESS in 6m 35s
⚠️ integration-community.aws-2 SKIPPED
⚠️ integration-community.aws-3 SKIPPED
⚠️ integration-community.aws-4 SKIPPED
⚠️ integration-community.aws-5 SKIPPED
⚠️ integration-community.aws-6 SKIPPED
⚠️ integration-community.aws-7 SKIPPED
⚠️ integration-community.aws-8 SKIPPED
⚠️ integration-community.aws-9 SKIPPED
⚠️ integration-community.aws-10 SKIPPED
⚠️ integration-community.aws-11 SKIPPED
⚠️ integration-community.aws-12 SKIPPED
⚠️ integration-community.aws-13 SKIPPED

@softwarefactory-project-zuul softwarefactory-project-zuul bot merged commit 35f4f59 into ansible-collections:main May 23, 2022
@patchback
Copy link

patchback bot commented May 23, 2022

Backport to stable-2: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-2/35f4f5921f39fe85d1af0fb1f96e6084678c31b4/pr-1145

Backported as #1153

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

patchback bot pushed a commit that referenced this pull request May 23, 2022
fix ecs_cluster integration test

SUMMARY

ecs_cluster: make ecs_cluster integration test work again - as it is

bugs I've hit and must be fixed to complete this challenge

ecs_taskdefinition: fix change detection of changing launch_type parameter
ecs_service:

compare of task_definition never works and results always in a changed task
change detect of health_check_grace_period_seconds was never implemented, but tested and failing, after the task_definition is compared correctly

ref: #1142
ISSUE TYPE

Bugfix Pull Request

COMPONENT NAME
ecs_taskdefinition
ecs_service
ADDITIONAL INFORMATION
basically the existing test tasks are not changed. just sorted and removed what was marked as fixme because it's simple not possible (changing network settings of a created service).

Reviewed-by: Alina Buzachis <None>
Reviewed-by: Joseph Torcasso <None>
Reviewed-by: Mark Chappell <None>
Reviewed-by: Markus Bergholz <[email protected]>
(cherry picked from commit 35f4f59)
@patchback
Copy link

patchback bot commented May 23, 2022

Backport to stable-3: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-3/35f4f5921f39fe85d1af0fb1f96e6084678c31b4/pr-1145

Backported as #1154

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

patchback bot pushed a commit that referenced this pull request May 23, 2022
fix ecs_cluster integration test

SUMMARY

ecs_cluster: make ecs_cluster integration test work again - as it is

bugs I've hit and must be fixed to complete this challenge

ecs_taskdefinition: fix change detection of changing launch_type parameter
ecs_service:

compare of task_definition never works and results always in a changed task
change detect of health_check_grace_period_seconds was never implemented, but tested and failing, after the task_definition is compared correctly

ref: #1142
ISSUE TYPE

Bugfix Pull Request

COMPONENT NAME
ecs_taskdefinition
ecs_service
ADDITIONAL INFORMATION
basically the existing test tasks are not changed. just sorted and removed what was marked as fixme because it's simple not possible (changing network settings of a created service).

Reviewed-by: Alina Buzachis <None>
Reviewed-by: Joseph Torcasso <None>
Reviewed-by: Mark Chappell <None>
Reviewed-by: Markus Bergholz <[email protected]>
(cherry picked from commit 35f4f59)
softwarefactory-project-zuul bot pushed a commit that referenced this pull request May 25, 2022
[PR #1145/35f4f592 backport][stable-3] fix ecs_cluster integration test

This is a backport of PR #1145 as merged into main (35f4f59).
SUMMARY

ecs_cluster: make ecs_cluster integration test work again - as it is

bugs I've hit and must be fixed to complete this challenge

ecs_taskdefinition: fix change detection of changing launch_type parameter
ecs_service:

compare of task_definition never works and results always in a changed task
change detect of health_check_grace_period_seconds was never implemented, but tested and failing, after the task_definition is compared correctly







ref: #1142
ISSUE TYPE


Bugfix Pull Request

COMPONENT NAME
ecs_taskdefinition
ecs_service
ADDITIONAL INFORMATION
basically the existing test tasks are not changed. just sorted and removed what was marked as fixme because it's simple not possible (changing network settings of a created service).

Reviewed-by: Markus Bergholz <[email protected]>
softwarefactory-project-zuul bot pushed a commit that referenced this pull request May 25, 2022
[PR #1145/35f4f592 backport][stable-2] fix ecs_cluster integration test

This is a backport of PR #1145 as merged into main (35f4f59).
SUMMARY

ecs_cluster: make ecs_cluster integration test work again - as it is

bugs I've hit and must be fixed to complete this challenge

ecs_taskdefinition: fix change detection of changing launch_type parameter
ecs_service:

compare of task_definition never works and results always in a changed task
change detect of health_check_grace_period_seconds was never implemented, but tested and failing, after the task_definition is compared correctly







ref: #1142
ISSUE TYPE


Bugfix Pull Request

COMPONENT NAME
ecs_taskdefinition
ecs_service
ADDITIONAL INFORMATION
basically the existing test tasks are not changed. just sorted and removed what was marked as fixme because it's simple not possible (changing network settings of a created service).

Reviewed-by: Markus Bergholz <[email protected]>
abikouo pushed a commit to abikouo/community.aws that referenced this pull request Oct 24, 2023
Enable ec2_metadata integration tests

SUMMARY
Enable ec2_metadata_facts integration tests
ISSUE TYPE

Feature Pull Request

COMPONENT NAME
ec2_metadata_facts
ADDITIONAL INFORMATION
As shown by ansible-collections#1138 we should try to ensure that the integration tests are enabled

Reviewed-by: Alina Buzachis <None>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-2 PR should be backported to the stable-2 branch backport-3 PR should be backported to the stable-3 branch bug This issue/PR relates to a bug community_review has_issue integration tests/integration mergeit Merge the PR (SoftwareFactory) module module needs_triage plugins plugin (any type) tests tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants