Jira (PUP-2584) Spurious warnings when using multiple file sources

[Kylo Ginsberg (JIRA)]

Title: Message Title

Kylo Ginsberg commented on an issue   Re: Spurious warnings when using multiple file sources [16:56:32] <spikebike> hrm, anyone know of a change in puppet 3.6.0 that breaks/changes file source commands? [16:56:57] <spikebike> seems like this nolonger will fall down to the second source [16:56:58] <spikebike> source=> ["puppet:///modules/slurm/$ {fqdn} /slurm.conf","puppet:///modules/slurm/$ {domain} /slurm.conf"], [17:10:40] <zaphod42> spikebike: there is PUP-1892 : Puppet remote fileserver facility for file resources [17:10:47] <zaphod42> https://tickets.puppetlabs.com/browse/PUP-1892 [17:19:22] <@eric0> zaphod42: i think that's different, afaict that only applies if you specify a server name ; in spikebike's case there's the implicit 'puppet' fileserver [17:26:19] <zaphod42> true, it was just the only change to source for files that I remember [17:28:59] <spikebike> zaphod42: looking at that, it's weird, I am just trying to serve out module/files, but it fails when the $ {FQDN} doesn't exist, and doesn't try the $ {DOMAIN} file [17:29:43] <spikebike> zaphod42: could the missing file trigger the andy parker mentioned source.nil? [17:31:20] <zaphod42> spikebike: since it isn't falling back to the other source, what is it doing? failing the resource? [17:32:31] <spikebike> I get: Warning: Find /production/file_metadata/modules/slurm/c12-8.ymir.cse.ucdavis.edu/slurm.sh?links=manage&source_permissions=use resulted in 404 with the message: Not Found: Could not find file_metadata modules/slurm/c12-8.ymir.cse.ucdavis.edu/slurm.sh [17:32:40] <spikebike> works fine on puppet-3.4.3 [17:33:25] <@eric0> zaphod42 == andy parker [17:33:34] <spikebike> ha, oops, greetings [17:33:44] <zaphod42> I was going to try staying anonymous for a while [17:34:26] <zaphod42> spikebike: so that warning doesn't mean it failed. That is a warning we had to put in to explain some other things that can happen, which ends up also showing up in this case [17:35:06] <spikebike> zaphod42: well it happens every run, and fills my screen with red, not the kind of thing I normally expect from a properly working manifest [17:35:53] <zaphod42> sigh...yeah. We might have to revisit the warning there [17:36:09] <zaphod42> spikebike: does the file on the node end up with the correct contents? [17:37:39] <kylo_> spikebike: did you try this on 3.5.1 by any chance? [17:39:27] <spikebike> kylo_: no, got a ubuntu trusty machine that used the ubuntu puppet till today (3.4.3) when puppetlabs pushed 3.6.0 [17:40:12] <spikebike> zaphod42: I'll have to test, I get 100s of lines of red every run, didn't think to check if it actually worked [17:41:15] <spikebike> zaphod42: is there a more er, puppet appropriate way to source a per host, per domain, per org type file that doesn't trigger the warnings? [17:42:20] <zaphod42> spikebike: no you are using the correct way to do that kind of fallback. The problem is that the warning is showing up in a bunch of places that we'd prefer not [17:43:46] <spikebike> zaphod42: ah, cool, well good to know what is going on and that (I think) it's working. Need to bring up a newly installed node to test Add Comment   Puppet / PUP-2584 Spurious warnings when using multiple file sources When a file resource uses multiple sources puppet issues a warning like (the example manifest and the warning are not intended to match in file names): {code} Warning: Find /production/file_metadata/modules/slurm/c12-8.ymir.cse.ucdavis.edu/slurm.sh?links=manage&source_permissions=use resulted in 404 with the message: Not Found: Could not find file_metad... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.