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

Test fails on Ubuntu 16.04 (sudo privilege failure) #47

Closed
juliendufresne opened this issue Jul 11, 2016 · 0 comments · Fixed by #48
Closed

Test fails on Ubuntu 16.04 (sudo privilege failure) #47

juliendufresne opened this issue Jul 11, 2016 · 0 comments · Fixed by #48
Assignees
Labels
Milestone

Comments

@juliendufresne
Copy link
Owner

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

  • 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?

@juliendufresne juliendufresne added this to the First stable release milestone Jul 11, 2016
@juliendufresne juliendufresne self-assigned this Jul 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant