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

icinga2-ansible-web2-ui is incomplete and requires manual intervention #57

Open
ghost opened this issue Sep 17, 2017 · 6 comments
Open

Comments

@ghost
Copy link

ghost commented Sep 17, 2017

The icinga2-ansible-web2-ui role is does not allow for a fully automated installation and requires manual intervention to finish the installation as indicated by the following message Now generate a token with 'icingacli setup token create' and go at http://IP//icingaweb2/setup to continue the installation

@Skeen
Copy link

Skeen commented Dec 27, 2017

The token can be picked up rather easily with a delegation of a shell command:

 - name: Get setup token.
   shell: 'icingacli setup token create | sed "s/.*token is: \(.*\)/\1/g"'
   register: setup_token
   delegate_to: "{{ server }}"

After this, the value can be accessed as: "{{ setup_token.stdout }}"

@aflatto
Copy link
Contributor

aflatto commented Dec 27, 2017

@Skeen thanks you for the code contribution , commit 68ff54e is based on your suggestion

@aflatto aflatto closed this as completed Dec 27, 2017
@Skeen
Copy link

Skeen commented Dec 28, 2017

I'm not convinced this issue should be closed yet, there's still the manual step which requires a web browser.

@aflatto aflatto reopened this Dec 28, 2017
@Skeen
Copy link

Skeen commented Dec 28, 2017

It might be better to pull the setup_token from the /etc/icingaweb2/setup.token file.

@maccadia
Copy link
Contributor

The steps to automate IcingaWeb2 setup are documented here. It would be nice to have a zero-touch install. However, I don't know how much work is needed to cover all possible setups.

@Bitblade
Copy link
Contributor

Bitblade commented Apr 2, 2019

I've managed to do it for Debian as a proof of concept. My playbook is far from 'viewable' at the moment, but it can be done. I've started to rewrite it based on that playbook. #101 is the first step.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants