sergevs / ansible-serviced-zenoss Goto Github PK

Copying the ssh keys fails with the error:
failed: [35.224.101.16] (item=id_rsa) => {"changed": false, "checksum": "5dd9f8c62a7478a6452786731bd26603f8812659", "item": "id_rsa", "msg": "Destination directory .ssh does not exist"}
failed: [35.224.101.16] (item=id_rsa.pub) => {"changed": false, "checksum": "d1374ff736889ed95d43832fde852fb7b425f53f","item": "id_rsa.pub", "msg": "Destination directory .ssh does not exist"}
failed: [35.224.101.16] (item=authorized_keys) => {"changed": false, "checksum": "d1374ff736889ed95d43832fde852fb7b425f53f", "item": "authorized_keys", "msg": "Destination directory .ssh does not exist"}
failed: [35.224.101.16] (item=known_hosts) => {"changed": false, "checksum": "e59cd5f8c0d6037853d68e4a82911f6102a5a4db", "item": "known_hosts", "msg": "Destination directory .ssh does not exist"}
to retry, use: --limit @/vagrant/zenoss_google/site.retry

In ssh-auth.yml, the copy line:

• name: distribute ssh files and keys
  copy: src={{ inventory_dir }}/workdir/{{ item }} dest=.ssh/{{ item }} mode=600
  Should be:
• name: distribute ssh files and keys
  copy: src={{ inventory_dir }}/workdir/{{ item }} dest=/home/{{ serviced_user }}/.ssh/{{ item }} mode=600

Still learning git to submit a pull request.

HI community,

What is de default username and password to log into the control center ??.

BR,

Edgar

I had Zenoss deployed using this ansible script and it was running fine. Yesterday, due to an emergency, the instance needed to be restarted and after reboot, the services are not starting. The main dependency docker is not starting and nothing else is starting.

I can see LVM intact however docker is not starting.

Anyone has seen this issue before?

Hi!
There is a default version mismatch for docker-ce package on Ubuntu 16.04 installation, so serviced package installation fails.
Workaround:

echo 'Package: docker-ce
Pin: version 17.09.0~ce-0~ubuntu
Pin-Priority: 900' >/etc/apt/preferences.d/docker

Then install.

I think it would be useful if the storage driver could be specified as a variable to this script.
A simpler request could be to specify whether or not VFS is used as a storage driver.
LVM is sometimes tricky to configure and VFS works out of the box in all environments.

Hello,

Can I use this same playbook to deploy Zenoss Core complete nine yards on native linux debian? If yes, can someone guide on how to proceed?

Thanks,
Mayur Patel