Closed
Bug 1299268
Opened 8 years ago
Closed 8 years ago
hgmaster container build failing with "TimeoutError: Timer expired" when gathering ansible facts
Categories
(MozReview Graveyard :: Testing / Development Environment, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: mars, Unassigned)
Details
Spotted running create-test-environment in a fresh vagrant box, rev 4ca271431a51efe5597fd2fbd26096a2db381aec. create-test-environment's output: ERROR hgmaster> GATHERING FACTS *************************************************************** ERROR hgmaster> failed: [localhost] => {"cmd": "/usr/bin/lsblk -ln --output UUID /dev/mapper/centos-root", "failed": true, "rc": 257} ERROR hgmaster> msg: Traceback (most recent call last): ERROR hgmaster> File "/root/.ansible/tmp/ansible-tmp-1472583213.0-216805394946070/setup", line 1668, in run_command ERROR hgmaster> cmd = subprocess.Popen(args, **kwargs) ERROR hgmaster> File "/usr/lib64/python2.7/subprocess.py", line 711, in __init__ ERROR hgmaster> errread, errwrite) ERROR hgmaster> File "/usr/lib64/python2.7/subprocess.py", line 1308, in _execute_child ERROR hgmaster> data = _eintr_retry_call(os.read, errpipe_read, 1048576) ERROR hgmaster> File "/usr/lib64/python2.7/subprocess.py", line 478, in _eintr_retry_call ERROR hgmaster> return func(*args) ERROR hgmaster> File "/root/.ansible/tmp/ansible-tmp-1472583213.0-216805394946070/setup", line 1823, in _handle_timeout ERROR hgmaster> raise TimeoutError(error_message) ERROR hgmaster> TimeoutError: Timer expired ERROR hgmaster> TASK: [ius-repo | download IUS community configuration RPMs (RedHat 6)] ******* ERROR hgmaster> fatal: [localhost] => error while evaluating conditional: ansible_distribution == 'Red Hat Enterprise Linux' and ansible_distribution_major_version == '6' ERROR hgmaster> FATAL: all hosts have already failed -- aborting ERROR hgmaster> PLAY RECAP ******************************************************************** ERROR hgmaster> to retry, use: --limit @/root/docker-hgmaster.retry ERROR hgmaster> localhost : ok=0 changed=0 unreachable=1 failed=1
Reporter | ||
Comment 1•8 years ago
|
||
This is working now. It may have been a VM misconfiguration, or it may have come from running on docker 1.11.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•