New module release on the Forge. Clients still fetch the old ?

[Samir Cury]

Hi,

Maybe I'm overlooking something basic, but I apparently successfully updated this module :

https://forge.puppetlabs.com/samircur...

To version 1.2.0 but still :

[root@darkstar ~]# puppet module install samircury-kvm 

Notice: Preparing to install into /etc/puppet/modules ... 

Notice: Downloading from https://forge.puppetlabs.com ... 

Notice: Installing -- do not interrupt ... /etc/puppet/modules └── samircury-kvm (v1.1.2) 

[root@darkstar ~]# date Sun May 4 15:05:34 PDT 2014 # 1.2.0 release date in the Forge is 

Tried in a "virgin" Docker container to make sure there were no caches, but still the same.

Any ideas? puppet module update claims it's up-to-date in 1.1.2.

If I try to force it to 1.2.0 it doesn't actually find it :

[root@darkstar ~]# puppet module install samircury-kvm --version 1.2.0

Notice: Preparing to install into /etc/puppet/modules ...

Notice: Downloading from https://forge.puppetlabs.com ...

Error: Could not install module 'samircury-kvm' (v1.2.0)

  No version of 'samircury-kvm' will satisfy dependencies

    You specified 'samircury-kvm' (v1.2.0)

    Use `puppet module install --force` to install this module anyway

Thanks,
Samir

[root@darkstar ~]# cat /etc/issue

Fedora release 20 (Heisenbug)

Kernel \r on an \m (\l)

[root@darkstar ~]# rpm -qa | grep puppet

puppet-3.4.2-1.fc20.noarch