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

Vagrant Box "UP" fails at "puppet" installation #204

Open
MJMcC9 opened this issue Apr 21, 2020 · 0 comments
Open

Vagrant Box "UP" fails at "puppet" installation #204

MJMcC9 opened this issue Apr 21, 2020 · 0 comments

Comments

@MJMcC9
Copy link

MJMcC9 commented Apr 21, 2020

Hi all,

during the vagrant up process the connection to puppet failed and thus the complete initalisation of the vagrant box did not run correctly. I ran the command for the standalone system.

Unfortunately I no longer have the error in my cmd. The error message stated that a connection could not be established to the downloadable ".rpm" puppet file.

Normally puppet should be downloaded and installed as it is a prequisite to execute the following steps.

Failing the download doesn't abort the hole setup of the VM. A "ssh" connection issue is protocolled and information that further information can be retrieved from the logs... I did not find those logs.
With vagrant ssh a connection can be established to the newly created VM icinga2.
Neither Icinga nor it's required components are installed on the new virutal machine. (puppet does this)

I did notice that Icinga was not up and running but didn't know what triggered this.
I finally discovered that with the vagrant provision the setup of puppet could be restarted.
The vagrant file contains the following:

provision: Puppet and friends

  provision_pre(node_config, name, options)

  provision_puppet(node_config, name, options)

  provision_post(node_config, name, options)

After running vagrant provision puppet was successfully installed. The following steps where also automatically triggered, which concluded in the correct setup of Icinga.

What I discribed above is a fix in case the setup fails.

Below an idea how this issue could be mitigated:
Within the setup the connection to puppet should be enclosed with a retry after a few seconds. Let's say the connection can't be established on first try. Wait 5 seconds and try again, if that didn't work try a last time after e.g. 10 more seconds...
Then either the installation of puppet has succeeded or the process should inform the user that due to the missing installation of puppet the box is not correctly setup and could be "fixed" with vagrant provision

My Environment
Vagrant version (vagrant -v): 2.2.7
Box name: icinga2
Operating system: WIN 10
Provider (VirtualBox, Parallels, libvirt): VirtualBox (OS Centos 7.7)

pull bot pushed a commit to Mattlk13/icinga-vagrant that referenced this issue Nov 10, 2022
96a95cc9 Release 4.0.5
e120ab6b Setup module specific facts
84760c17 Restore deploy step in Travis
16dd9867 Update pdk version
1b58de0e When upgrading to Filebeat 7.x you should set the major_version to 7 otherwise the configuration tests will fail to execute. (#221)
2b0b6103 Update metadata versions (#220)
9925e5bf Release v4.0.4
d1b98521 Adding support for config file validation for version 7 on Windows (#219)
96aaec44 Release version 4.0.3
bfb79da1 Adding support for version check of Windows filebeat version 5 though 7 (#218)
bc676580 Release v4.0.2
55023038 Clear the yum cache after making changes to the yum repo
0c0b077c Require the puppetlabs/yumrepo_core module
6756f005 Release 4.0.1
045f112c Fix regression on fresh installs (#216)
869f5d74 Update pdk and fix unit tests (#213)
49f45602 Release 4.0.0
c4a11770 Add unreleased tag to 4.0.0
a1b47e2b Remove queue_size
49430962 Add support for http metrics and filebeat 7
33507880 Convert prospector to input
a60f6954 Prospectors depends on filebeat.yml (Icinga#211)
0a654dd8 Don't test against Puppet 4
9575d782 Document adding registry_flush
d179388a Merge branch 'add_registry_flush'
3724d1b2 Make registry_flush optional
ea3855fb Allow strings for clean_inactive
757ab26a Merge remote-tracking branch 'pcfens/master' into add_registry_flush
9138c8f9 Release v3.4.0
c902e924 Bring changelog up to date
796eb2a1 Fix filebeat::prospector::fields_under_root (Icinga#205)
bca8323c Add a filebeat.config.modules section (Icinga#204)
fdc28f97 Support filebeat.registry_flush in filebeat.yml

git-subtree-dir: .puppet/modules/filebeat
git-subtree-split: 96a95cc9b90aff5dc02238b18596ed9c1096424c
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

1 participant