apt::update after apt::source in Ubuntu/Debian

[BDelacour]

Affected Puppet, Ruby, OS and module versions/distributions

• Puppet: 7.11.0
• Ruby:
• Distribution: Debian Buster
• Module version: puppet-nomad 2.0.0

How to reproduce (e.g Puppet code you use)

class { 'nomad':
  version => '1.1.5'
  config_hash => {
    ...
  }
}

What are you seeing

On first run, package fails to install because update has not been executed.

What behaviour did you expect instead

Working on first run to be able to redeploy from scratch without failure.

Output log

vsphere_virtual_machine.vm-standalone (remote-exec): Notice: /Stage[main]/Hashi_stack::Repo/Apt::Source[HashiCorp]/Apt::Setting[list-HashiCorp]/File[/etc/apt/sources.list.d/HashiCorp.list]/ensure: defined content as '{sha256}93eac247ee61654e5dcfec4f6bf2c1a23e629db7f306f463c500d806ea2f12a5'
vsphere_virtual_machine.vm-standalone (remote-exec): Info: /Stage[main]/Hashi_stack::Repo/Apt::Source[HashiCorp]/Apt::Setting[list-HashiCorp]/File[/etc/apt/sources.list.d/HashiCorp.list]: Scheduling refresh of Class[Apt::Update]
vsphere_virtual_machine.vm-standalone (remote-exec): Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install nomad=1.1.5' returned 100: Reading package lists..

Any additional information you'd like to impart

After some researches, I saw a very similar (and corrected) problem here : voxpupuli/puppet-virtualbox#25

Thank you !