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 #17832

@yumrepo does not create a virtual resource

Added by Steven Nemetz over 3 years ago. Updated over 3 years ago.

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

0%

Category:-
Target version:-
Affected Puppet version: Branch:
Keywords:

We've Moved!

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


Description

@yumrepo does not create a virtual resource or generate an error. Instead it behaves like yumrepo and creates the resource. It is as if the @ is ignored.

I have tested @yumrepo in a node definition in site.pp and in a module define. In both cases the resource was created. I also tested yumrepo in a define with a virtual call (@module::definename). This also created the resource instead of a virtual one.


Related issues

Related to Puppet - Refactor #8758: Yumrepo should be refactored to use a provider In Topic Branch Pending Review

History

#1 Updated by Michael Stahnke over 3 years ago

  • Project changed from Puppet Enterprise (Public) to Puppet

#2 Updated by Dominic Cleal over 3 years ago

Sounds like a dupe of #8758, because the yumrepo isn’t correct split into a type and provider.

#3 Updated by eric sorenson over 3 years ago

  • Status changed from Unreviewed to Duplicate

Agreed, thanks Dominic, marking as a duplicate.

Steven – This is a duplicate of #8758, so I am closing this ticket in favor of the older one. Please add yourself as a watcher on that ticket to track the progress of the fix.

Also available in: Atom PDF