You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that a bug has been introduced with PR #44 (Issue #43)
Running the pre script in privileged seems to fail. My guess is it's a vagrant issue but we should find a way to solves this.
Testing ansible role juliendufresne.influxdb in vagrant box bento/ubuntu-16.04
booting vagrant box: pass
Testing clean install: fail
==> default: Running provisioner: pre_script (shell)...
default: Running: /tmp/vagrant-shell20160711-1326-1oaz9s1.sh
==> default: mesg:
==> default: ttyname failed
==> default: :
==> default: Inappropriate ioctl for device
==> default: empty provision used
==> default: Running provisioner: ansible (ansible_local)...
default: Installing Ansible...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
apt-get update -y -qq
Stdout from the command:
Stderr from the command:
mesg: ttyname failed: Inappropriate ioctl for device
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
Idempotent test: fail
==> default: Running provisioner: pre_script (shell)...
default: Running: /tmp/vagrant-shell20160711-1862-ce7rjy.sh
==> default: mesg:
==> default: ttyname failed
==> default: :
==> default: Inappropriate ioctl for device
==> default: empty provision used
==> default: Running provisioner: ansible (ansible_local)...
default: Installing Ansible...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
apt-get update -y -qq
Stdout from the command:
Stderr from the command:
mesg: ttyname failed: Inappropriate ioctl for device
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
The text was updated successfully, but these errors were encountered:
It seems that a bug has been introduced with PR #44 (Issue #43)
Running the pre script in privileged seems to fail. My guess is it's a vagrant issue but we should find a way to solves this.
$ ./test.sh --ansible-role juliendufresne.influxdb -v --vagrant-box bento/ubuntu-16.04
Testing ansible role juliendufresne.influxdb in vagrant box bento/ubuntu-16.04
==> default: Running provisioner: pre_script (shell)...
default: Running: /tmp/vagrant-shell20160711-1326-1oaz9s1.sh
==> default: mesg:
==> default: ttyname failed
==> default: :
==> default: Inappropriate ioctl for device
==> default: empty provision used
==> default: Running provisioner: ansible (ansible_local)...
default: Installing Ansible...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
apt-get update -y -qq
Stdout from the command:
Stderr from the command:
mesg: ttyname failed: Inappropriate ioctl for device
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
==> default: Running provisioner: pre_script (shell)...
default: Running: /tmp/vagrant-shell20160711-1862-ce7rjy.sh
==> default: mesg:
==> default: ttyname failed
==> default: :
==> default: Inappropriate ioctl for device
==> default: empty provision used
==> default: Running provisioner: ansible (ansible_local)...
default: Installing Ansible...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
apt-get update -y -qq
Stdout from the command:
Stderr from the command:
mesg: ttyname failed: Inappropriate ioctl for device
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
The text was updated successfully, but these errors were encountered: