Project

General

Profile

Actions

Bug #6836

open

Replacing module with same name doesn't update params

Added by Jon Skarpeteig almost 10 years ago. Updated almost 10 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Puppet integration
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

I did an in-place replacement of the puppetdb module on the Puppet master. Deleting the puppetdb module from puppet classes, and importing it again does not update params. (Old params are still present)

Actions #1

Updated by Dominic Cleal almost 10 years ago

  • Project changed from Smart Proxy to Foreman
  • Category set to Puppet integration

It'd be helpful if you could supply a reproducer for this issue, e.g. the module and version you went from and to on the Forge, Puppet & Foreman versions etc.

Actions #2

Updated by Jon Skarpeteig almost 10 years ago

The replace wasn't complete:

The old module was renamed to puppetdb.old (which puts it outside of autoloader scope), but foreman detected it still, and displayed it instead of the actual puppetdb folder.

Subsequent delete of puppetdb.old and import in Foreman displays both: delete and update of 'puppetdb'. Seems both where imported, but ended up a naming collision.

Actions

Also available in: Atom PDF