Jira (PUP-5988) "puppet module upgrade" ignores changes if a module is upgraded as dependency

[Francois Lafont (JIRA)]

Title: Message Title

Francois Lafont created an issue   Puppet / PUP-5988 "puppet module upgrade" ignores changes if a module is upgraded as dependency Issue Type: Bug Affects Versions: PUP 4.3.2 Assignee: Unassigned Components: AIO Created: 2016/02/28 8:37 PM Environment: Ubuntu Trusty package puppet-agent 1.3.5-1trusty package puppetserver 2.2.1-1puppetlabs1 Priority: Normal Reporter: Francois Lafont Hi, I have a personal module (installed from a personal forge) that I have changed locally directly in the puppetserver. So I have this: ~# puppet module changes /etc/puppetlabs/code/environments/production/modules/raid/ Warning: 1 files modified manifests/init.pp In this case, the command puppet module upgrage flaf-raid fails and, personally, this behavior seems to be a very good thing: ~# puppet module upgrade flaf-raid Notice: Preparing to upgrade 'flaf-raid' ... Notice: Found 'flaf-raid' (v0.1.5) in /etc/puppetlabs/code/environments/production/modules ... Error: Could not upgrade module 'flaf-raid' (v0.1.5 -> latest) Installed module has had changes made locally Use `puppet module upgrade --ignore-changes` to upgrade this module anyway But the problem is when the module is upgraded by the play of module dependencies. For instance, I have a module flaf-role_generic (installed via my personal forge too) and the version 0.1.10 of this module, not yet installed in my puppetserver, needs the module flaf-raid version 0.1.6 exactly. The problem is: when I upgrade the module flaf-role_generic, the module flaf-raid is upgraded automatically without error: ~# puppet module upgrade flaf-role_generic Notice: Preparing to upgrade 'flaf-role_generic' ... Notice: Found 'flaf-role_generic' (v0.1.9) in /etc/puppetlabs/code/environments/production/modules ... Notice: Downloading from http://puppetforge.lss1.backbone.education:8080 ... Notice: Upgrading -- do not interrupt ... /etc/puppetlabs/code/environments/production/modules └─┬ flaf-role_generic (v0.1.9 -> v0.1.10) └── flaf-raid (v0.1.5 -> v0.1.6) If a "direct" upgrade is impossible when a module has had changes made locally, it seems that an upgrade "as dependency" should be impossible too. Regard. François Lafont Add Comment   This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.