oldcrowew / dcos-ansible Goto Github PK

Hi, thanks for sharing this repo. Cloning fails with permission denied because one of the submodules uses [email protected] instead of https:

[submodule "roles/ansible-dcos-bootstrap-node"]
        path = roles/ansible-dcos-bootstrap-node
        url = [email protected]:OldCrowEW/ansible-dcos-bootstrap-node.git

I was able to work around it by manually changing .gitmodules and resyncing, but it would be easier if all the subs used https.

Thanks!

Unless you want to follow the DCOS upgrades around it's best to keep the Docker version set in a variable. In DCOS 1.9 it's now at 1.13.1.

Some odd about this repo:

neil@luna:~/src/neil/dcos$ git clone [email protected]:OldCrowEW/dcos-ansible.git
Cloning into 'dcos-ansible'...
remote: Counting objects: 282, done.
remote: Total 282 (delta 0), reused 0 (delta 0), pack-reused 282
Receiving objects: 100% (282/282), 27.68 KiB | 0 bytes/s, done.
Resolving deltas: 100% (117/117), done.
Checking connectivity... done.

neil@luna:~/src/neil/dcos$ find dcos-ansible/roles/
dcos-ansible/roles/
dcos-ansible/roles/ansible-dcos-bootstrap-master
dcos-ansible/roles/ansible-dcos-common
dcos-ansible/roles/ansible-dcos-bootstrap-agent
dcos-ansible/roles/ansible-dcos-bootstrap-node

You don't have a group for public slaves ?

Hello

I've been testing your Ansible playbook, and it's absolutely great (as long as I stick to CentOS/RHEL 7.2 and do not go to 7.3). However the : ansible-dcos-common/tasks/main.yml

• name: Upgrade all packages
  yum: name=* state=latest

Results in upgrading CentOS/RHEL 7.2 point release to 7.3

Unfortunately that particular point release has a bug in its microcode.service, which cannot start properly, and as a result, causes docker daemon to fail to start, as microcode.service is a dependency of docker.service in systemd.

Which as a result breaks the playbook :(

Details:
https://bugzilla.redhat.com/show_bug.cgi?id=1411232

Thought I would make you aware of it.
best regards
/Moolibden