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

Travis CI pip-based builds failing with Segmentation fault while gathering facts #15

Closed
geerlingguy opened this issue Apr 24, 2018 · 3 comments

Comments

@geerlingguy
Copy link
Owner

This happens on both Python 2.7 and 3.6, but does not happen on the ansible-container source build, for some reason. I also can't reproduce it on my local environment installing 0.9.2 from pip either :/

Example:

$ ansible-container --var-file vars-7.x.yml build --no-container-cache
Building Docker Engine context...	
Starting Docker build of Ansible Container Conductor image (please be patient)...	
Parsing conductor CLI args.
Docker™ daemon integration engine loaded. Build starting.	project=solr-container
Building service...	project=solr-container service=solr

PLAY [solr] ********************************************************************
TASK [Gathering Facts] *********************************************************
fatal: [solr]: FAILED! => {"failed": true, "msg": "failed to transfer file /tmp/tmpOFGVkn to /root/.ansible/tmp/ansible-tmp-1524517954.77-134106081382654/setup.py:\n\nSegmentation fault (core dumped)\n"}
	to retry, use: --limit @/tmp/tmpqGrK2I/playbook.retry
PLAY RECAP *********************************************************************
solr                       : ok=0    changed=0    unreachable=0    failed=1
ERROR	Error applying role!	engine=<container.docker.engine.Engine object at 0x7fde68507950> exit_code=2 playbook=[{'hosts': u'solr', 'roles': ['setup'], 'vars': {u'solr_version': u'7.1.0', u'container_start_command': [u'/opt/solr/bin/solr', u'start', u'-f', u'-force'], u'container_working_dir': u'/', u'java_packages': [u'openjdk-8-jdk'], u'solr_remove_cruft': True}}]
Traceback (most recent call last):
  File "/usr/local/bin/conductor", line 11, in <module>
    load_entry_point('ansible-container', 'console_scripts', 'conductor')()
  File "/_ansible/container/__init__.py", line 19, in __wrapped__
    return fn(*args, **kwargs)
  File "/_ansible/container/cli.py", line 399, in conductor_commandline
    **params)
  File "/_ansible/container/__init__.py", line 19, in __wrapped__
    return fn(*args, **kwargs)
  File "/_ansible/container/core.py", line 813, in conductorcmd_build
    raise RuntimeError('Build failed.')
RuntimeError: Build failed.
Conductor terminated. Cleaning up.	command_rc=1 conductor_id=6ac0daeabe35bc741ee4325a52a7e55d2eb1c93f24ff6aa231f674fbd364d9be save_container=False
ERROR	Conductor exited with status 1	
The command "ansible-container --var-file vars-7.x.yml build --no-container-cache" exited with 1.

Build: https://travis-ci.org/geerlingguy/solr-container/builds/370292203

@geerlingguy
Copy link
Owner Author

For now, I think I'll just allow failures for the pip install method, since the main point of the tests is to make sure the ansible-container configuration works with master (and incidentally, I can prove it works with 0.9.2 locally too :P).

@geerlingguy
Copy link
Owner Author

Possibly related? ansible/ansible#21562 (comment)

@geerlingguy geerlingguy changed the title Travis CI builds failing during ansible-container build with Segmentation fault Travis CI pip-based builds failing with Segmentation fault while gathering facts Apr 24, 2018
@geerlingguy
Copy link
Owner Author

I think I'll instead drop Ansible Container as a requirement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant