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

Unstable integration test azure_rm_containerinstance #36080

Closed
mattclay opened this issue Feb 12, 2018 · 6 comments
Closed

Unstable integration test azure_rm_containerinstance #36080

mattclay opened this issue Feb 12, 2018 · 6 comments
Assignees
Labels
affects_2.5 This issue/PR affects Ansible v2.5 azure bug This issue/PR relates to a bug. cloud module This issue/PR relates to a module. support:community This issue/PR relates to code supported by the Ansible community. test This PR relates to tests. traceback This issue/PR includes a traceback.

Comments

@mattclay
Copy link
Member

ISSUE TYPE

Bug Report

COMPONENT NAME

azure_rm_containerinstance integration test

ANSIBLE VERSION

2.5

CONFIGURATION

N/A

OS / ENVIRONMENT

Shippable

SUMMARY

Unstable integration test azure_rm_containerinstance:

https://app.shippable.com/github/ansible/ansible/runs/54332/51/tests

STEPS TO REPRODUCE

Run tests on Shippable.

EXPECTED RESULTS

Tests pass.

ACTUAL RESULTS

Tests are unstable or fail.

test/integration/targets/azure_rm_containerinstance/tasks/main.yml:98 / [localhost] azure: azure_rm_containerinstance : Assert the container instance is deleted that=[u'output.changed']

failure: rc=0

{
    "assertion": "output.changed", 
    "changed": false, 
    "evaluated_to": false, 
    "failed": true
}

test/integration/targets/azure_rm_containerinstance/tasks/main.yml:1 / [localhost] azure: azure_rm_containerinstance : Create sample container instance name=aci{{ resource_group | hash('md5') | truncate(7, True, '') }}, resource_group={{ resource_group }}, os_type=linux, ip_address=public, ports=[80], containers=[{u'image': u'httpd', u'ports': [80, 81], u'name': u'mycontainer1', u'memory': 1.5}, {u'image': u'httpd', u'name': u'mycontainer2', u'memory': 1.5}], location=eastus

error: Message: The container group 'aciaebe055' is still transitioning, please retry later.

Traceback (most recent call last):
  File "/tmp/ansible_1CMYew/ansible_module_azure_rm_containerinstance.py", line 424, in <module>
    main()
  File "/tmp/ansible_1CMYew/ansible_module_azure_rm_containerinstance.py", line 421, in main
    AzureRMContainerInstance()
  File "/tmp/ansible_1CMYew/ansible_module_azure_rm_containerinstance.py", line 264, in __init__
    supports_tags=False)
  File "/tmp/ansible_1CMYew/ansible_modlib.zip/ansible/module_utils/azure_rm_common.py", line 345, in __init__
  File "/tmp/ansible_1CMYew/ansible_module_azure_rm_containerinstance.py", line 318, in exec_module
    response = self.create_update_containerinstance()
  File "/tmp/ansible_1CMYew/ansible_module_azure_rm_containerinstance.py", line 384, in create_update_containerinstance
    container_group=parameters)
  File "/usr/local/lib/python2.7/dist-packages/azure/mgmt/containerinstance/operations/container_groups_operations.py", line 307, in create_or_update
    raise exp
msrestazure.azure_exceptions.CloudError: Azure Error: ContainerGroupTransitioning
Message: The container group 'aciaebe055' is still transitioning, please retry later.
@mattclay
Copy link
Member Author

@zikalino Can you take a look at this?

@ansibot ansibot added affects_2.5 This issue/PR affects Ansible v2.5 azure bug_report cloud module This issue/PR relates to a module. needs_triage Needs a first human triage before being processed. support:community This issue/PR relates to code supported by the Ansible community. labels Feb 12, 2018
@mattclay mattclay removed the needs_triage Needs a first human triage before being processed. label Feb 12, 2018
@mattclay
Copy link
Member Author

/cc @nitzmahone

@zikalino
Copy link
Contributor

@mattclay i will investigate these issues. they don't seem to be related to Ansible in any way though...

@mattclay
Copy link
Member Author

@zikalino At a minimum there is a bug in the module (or one of its dependencies), as modules should not traceback. Either the error should be handled internally within the module or it should be reported as an error without a traceback.

If the test is expected to fail intermittently due to errors reported by the module, then the test may not be suitable for running in CI.

@zikalino
Copy link
Contributor

working on it

@mattclay mattclay added this to To do in Broken Azure Tests Mar 22, 2018
@ansibot ansibot added test This PR relates to tests. traceback This issue/PR includes a traceback. labels May 24, 2018
@yungezz yungezz moved this from To do to In progress in Broken Azure Tests May 29, 2018
@yungezz yungezz moved this from In progress to Done in Broken Azure Tests May 29, 2018
@mattclay
Copy link
Member Author

Resolved by #40780

@ansible ansible locked and limited conversation to collaborators May 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.5 This issue/PR affects Ansible v2.5 azure bug This issue/PR relates to a bug. cloud module This issue/PR relates to a module. support:community This issue/PR relates to code supported by the Ansible community. test This PR relates to tests. traceback This issue/PR includes a traceback.
Projects
No open projects
Development

No branches or pull requests

3 participants