The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:

Bug #15961

Too vague of a depreciation warning when using source with out "modules" in the file path

Added by Anonymous over 3 years ago. Updated over 3 years ago.

Status:AcceptedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Affected Puppet version:2.7.17 Branch:
Keywords:errors telly_deprecation

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com


Description

While looking through my puppet logs I came across the following:

Aug 14 15:11:53 puppet-tn puppet-master[30650]: DEPRECATION NOTICE: Files found in modules without specifying ‘modules’ in file path will be deprecated in the next major release. Please fix module ‘tn_batch’ when no 0.24.x clients are present

This error is less than helpful, as it does not tell me where the offending file is or which file is the problem or anything that would actually be useful when it comes to fixing this potential problem.


Related issues

Related to Puppet - Bug #16667: Misleading error message "Not authorized to call find" af... Investigating 10/01/2012
Related to Puppet - Bug #17017: Improve puppet's error handling and exit code correctness. Accepted

History

#1 Updated by eric sorenson over 3 years ago

  • Status changed from Unreviewed to Accepted
  • Start date deleted (08/14/2012)
  • Keywords set to errors telly_deprecation

Since this will be going away completely in telly we’d have to put a fix into 2.7.x only. Tagging with ‘errors’ to group with other exit code / error message tickets.

#2 Updated by eric sorenson over 3 years ago

  • Parent task set to #17017

#3 Updated by eric sorenson over 3 years ago

  • Parent task deleted (#17017)

In fact our handling about this got worse in 3.0.0! See #16667

Also available in: Atom PDF