Page MenuHomeSoftware Heritage

Vagrantfile: Explicit the mount point should happen with rsync

Authored by ardumont on Jan 11 2022, 6:21 PM.



Otherwise, puppet fails to mount nfs volumes (using nfs v3 badly supported with bullseye
node [1]).


Related to T3833

Test Plan

Without this diff, see [1]

With it, the vm is mounted without issues:

vagrant reload dali
==> dali: Attempting graceful shutdown of VM...
==> dali: Starting domain.
==> dali: Waiting for domain to get an IP address...
==> dali: Waiting for machine to boot. This may take a few minutes...
    dali: SSH address:
    dali: SSH username: vagrant
    dali: SSH auth method: private key
==> dali: Machine booted and ready!
==> dali: Creating shared folders metadata...
==> dali: Exporting NFS shared folders...
==> dali: Preparing to edit /etc/exports. Administrator privileges will be required...
[sudo] password for tony:
Sorry, try again.
[sudo] password for tony:
==> dali: Mounting NFS shared folders...
==> dali: Installing rsync to the VM...
==> dali: Rsyncing folder: /tmp/puppet/environments/ => /tmp/vagrant-puppet/environments
==> dali: Rsyncing folder: /home/tony/work/inria/repo/swh/puppet-environment/swh-site/manifests/ => /tmp/vagrant-puppet/manifests-158062c63b8270a305072fe9a8eecc79
==> dali: Running provisioner: shell...
    dali: Running: /tmp/
    dali: + DEPLOYMENT=admin
    dali: + SUBNET=vagrant
    dali: + FACTS_D=/etc/facter/facts.d
    dali: + '[' '!' -d /etc/facter/facts.d ']'
    dali: + mkdir -p /etc/facter/facts.d
    dali: + echo deployment=admin
    dali: + echo subnet=vagrant
==> dali: Running provisioner: puppet...
==> dali: Running Puppet with environment production...
==> dali: Info: Loading facts
==> dali: Info: Loading facts
==> dali: Info: Loading facts

Diff Detail

rSENV Puppet Environment
Automatic diff as part of commit; lint not applicable.
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

ardumont created this revision.
vsellier added inline comments.

Perhaps put this line under the L600 to be closed to the relative comment ?


totally, i did not connect the dot here.

Adapt according to suggestion

This revision is now accepted and ready to land.Jan 12 2022, 11:24 AM

By the way, I had forgotten to check that buster nodes are ok with this.
They still are [1]

$ vagrant up --no-destroy-on-error test
==> test: Notice: Applied catalog in 125.52 seconds