Closed weijianwen closed 4 months ago
Rerun vagrant gives different error messages.
debian-10-x86_64: Installing sys-filesystem 1.4.4
debian-10-x86_64: Bundle complete! 4 Gemfile dependencies, 7 gems now installed.
debian-10-x86_64: Bundled gems are installed into `./vendor/bundler`
debian-10-x86_64: Fetching gem metadata from https://rubygems.org/........
debian-10-x86_64: Resolving dependencies...
debian-10-x86_64: Could not find compatible versions
debian-10-x86_64:
debian-10-x86_64: Because facter >= 4.0.7.pre, < 4.2.0 depends on Ruby ~> 2.3
debian-10-x86_64: and facter >= 4.0.0, < 4.0.7.pre could not be found in rubygems repository
debian-10-x86_64: https://rubygems.org/ or installed locally,
debian-10-x86_64: facter >= 4.0.0, < 4.2.0 requires Ruby ~> 2.3.
debian-10-x86_64: So, because Gemfile depends on facter ~> 4.0.0
debian-10-x86_64: and current Ruby version is = 3.2.2,
debian-10-x86_64: version solving has failed.
debian-10-x86_64: bundle update failed for facter version: 4.0.0
debian-10-x86_64: Fetching gem metadata from https://rubygems.org/........
debian-10-x86_64: Resolving dependencies...
debian-10-x86_64: Could not find compatible versions
debian-10-x86_64:
debian-10-x86_64: Because facter >= 4.0.7.pre, < 4.2.0 depends on Ruby ~> 2.3
debian-10-x86_64: and Gemfile depends on facter ~> 4.1.0,
debian-10-x86_64: Ruby ~> 2.3 is required.
debian-10-x86_64: So, because current Ruby version is = 3.2.2,
debian-10-x86_64: version solving has failed.
debian-10-x86_64: bundle update failed for facter version: 4.1.0
debian-10-x86_64: Fetching gem metadata from https://rubygems.org/........
debian-10-x86_64: Resolving dependencies...
debian-10-x86_64: Fetching facter 4.2.14 (was 4.5.0)
debian-10-x86_64: Installing facter 4.2.14 (was 4.5.0)
debian-10-x86_64: Bundle updated!
debian-10-x86_64: Fetching gem metadata from https://rubygems.org/........
debian-10-x86_64: Resolving dependencies...
debian-10-x86_64: Fetching facter 4.3.1 (was 4.2.14)
debian-10-x86_64: Installing facter 4.3.1 (was 4.2.14)
debian-10-x86_64: Bundle updated!
debian-10-x86_64: Fetching gem metadata from https://rubygems.org/........
debian-10-x86_64: Resolving dependencies...
debian-10-x86_64: Fetching facter 4.4.3 (was 4.3.1)
debian-10-x86_64: Installing facter 4.4.3 (was 4.3.1)
debian-10-x86_64: Bundle updated!
==> debian-10-x86_64: Running provisioner: shell...
debian-10-x86_64: Running: inline script
Guest-specific operations were attempted on a machine that is not
ready for guest communication. This should not happen and a bug
should be reported.
Do you need to run every OS in the Vagrantfile just to generate facts for one new OS? Seems like there must be a better way.
You can run just a single image via:
vagrant up --provision $img_name
where the img_name is the bit in quotes after the config.vm.define
in the Vagrantfile.
In order to add facterdb facts for OpenEuler, you'll need to alter Vagrantfile and potentially the facts/get_facts.sh script.
facterdb no longer supports Debian 10. Please reopen if this is an issue with a different OS.
I'm trying to add OpenEuler 23 as a supported OS by Puppet. But I failed in
vagrant up --provision
when following instructions to add more OS facter into facterdb.https://github.com/voxpupuli/puppet-yum/pull/322
I tried this on OpenEuler 22.03 (x86_64) + VirtualBox 6.1 + Vagrant 2.3.7 . Steps to reproduce this issue are:
git clone https://github.com/voxpupuli/facterdb.git
.cd facterdb/facts && vagrant up --provision
then get the following messages. Please find the full log file attached.vagrantlog.txt