tag 492718 +moreinfo thanks I've tested this problem and am having trouble coming up with a reproducable case. If you can come up with a way for me to reproduce the problem, I can push this upstream, but until I can also do it, I'm not able to convince them its a problem.
It sounds like this is probably a fact caching issue, where the hostname cached doesn't match the name found for the Node. You should be able to look in :yamldir/facts and :yamldir/nodes and see data for the same node under different names (e.g., fully qualified and unqaulified). According to upstream, this definitely shouldn't happen in 0.24.5, and if we can come up with a case where we can replicate it, then we are likely to get a quick resolution. micah
signature.asc
Description: Digital signature
