[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
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.

Sign up for GitHub

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

Jump to bottom

Install: [Errno 16] Device or resource busy #313

Open
seanhig opened this issue Dec 5, 2017 · 1 comment
Open

Install: [Errno 16] Device or resource busy #313

seanhig opened this issue Dec 5, 2017 · 1 comment

Comments

@seanhig
Copy link
seanhig commented Dec 5, 2017 •
edited
Loading

Docker Version: 17.09
CentOS 7 (1708) base
Existing docker native swarm
Remote API TLS secured on 2376
Firewalld disabled (all ports open)

Apologies if I should be posting this in the ansible project, the repo layout is a bit confusing. I assume (hope) the same folks are working on both projects.

I am performing the install steps on the one manager node in a four node docker swarm. Swarm is fully functional and tested.

Following the minimal, if not ambiguous, installation documentation, the installation fails in https://github.com/contiv/ansible/blob/master/roles/contiv_network/tasks/main.yml

at the step:

- name: setup netmaster host alias
  lineinfile:
    dest: /etc/hosts
    line: "127.0.0.1 netmaster"
    regexp: " netmaster$"
    state: present
  when: (run_as == "master")

With the error:

An exception occurred during task execution. To see the full traceback, use -vvv. The error was: OSError: [Errno 16] Device or resource busy", "fatal: [node1]: FAILED! => {\"changed\": false, \"failed\": true, \"msg\": \"Unable to rename file: /tmp/tmpsgmY9l to /etc/hosts: [Errno 16] Device or resource busy\"}"

This appears to be a known issue, updating /etc/hosts within a docker container causes this error.
moby/moby#22281

As per the cpuguy83, editing /etc/hosts is not even supported (though there is a workaround Contiv does not employ). Bizarre.

So I am confused.
Why would something not supported be attempted as part of the Contiv install?
Why would an error so basic come up and yet be unreported?

I must be doing something wrong, yet it doesn't seem relevant to any particular configuration item.

Help?

PS.

Containers: 2
 Running: 2
 Paused: 0
 Stopped: 0
Images: 3
Server Version: 17.09.0-ce
Storage Driver: devicemapper
 Pool Name: docker-thinpool
 Pool Blocksize: 524.3kB
 Base Device Size: 10.74GB
 Backing Filesystem: xfs
 Data file: 
 Metadata file: 
 Data Space Used: 536.9MB
 Data Space Total: 255GB
 Data Space Available: 254.5GB
 Metadata Space Used: 413.7kB
 Metadata Space Total: 2.68GB
 Metadata Space Available: 2.68GB
 Thin Pool Minimum Free Space: 25.5GB
 Udev Sync Supported: true
 Deferred Removal Enabled: true
 Deferred Deletion Enabled: true
 Deferred Deleted Device Count: 0
 Library Version: 1.02.140-RHEL7 (2017-05-03)
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host ipvlan macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: active
 NodeID: izeofieioqnz2lttf6xuvhwxu
 Is Manager: true
 ClusterID: z66z0ewyu2qchjmtfqbhxdu33
 Managers: 1
 Nodes: 4
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
  Force Rotate: 0
 Autolock Managers: false
 Root Rotation In Progress: false
 Node Address: 192.168.100.90
 Manager Addresses:
  192.168.100.90:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 06b9cb35161009dcb7123345749fef02f7cea8e0
runc version: 3f2f8b84a77f73d38244dd690525642a72156c64
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 3.10.0-693.5.2.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 2.781GiB
Name: demo-swarm-m1
ID: F7YZ:LXDS:ZWF2:HZVW:7SGN:XJBB:MSWM:K3MT:UMGM:4XUK:Z2N5:FDB4
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false
@kusumaningrat
Copy link

Does anyone can helo to solve this problem ? Iam trying to deploy openstack using kolla-ansible. but when I run bootsrap servers deploy, I got this error
dse

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@seanhig @kusumaningrat