Project

General

Profile

Bug #17402

Puppet module appear in content view but doesn't appear in lifecycle environment

Added by Brad Buckingham over 4 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Category:
Lifecycle Environments
Target version:
Difficulty:
easy
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1395151

Description of problem:
Following the correct workflow, the puppet module should be visible in the lifecycle environment, but this one doesn't happen, appear in the content view and after this one be published and promoted to one specific lifecycle environment, the puppet module still doesn't appearing in the lifecycle environment.

How reproducible:
100%

Steps to Reproduce:
1. Add puppet module into cv, publish
2. Promote this cv to one specific lifecycle environment
3. Open lifecycle environment and click on Puppet Modules tab
4. Will see the message "There are no Puppet Modules that match the criteria."

Actual results:
"There are no Puppet Modules that match the criteria."

Expected results:
See the puppet module

Associated revisions

Revision 13f1896c (diff)
Added by Brad Buckingham over 4 years ago

fixes #17402 - lifecycle environment - fix puppet modules filter

This commit will fix the filtering to obtain the list of
puppet modules in a non-library (e.g. dev, test,...)
lifecycle environment. (Ref: Content -> Lifecycle Environments)

History

#1 Updated by Brad Buckingham over 4 years ago

  • Subject changed from Puppet module appear in content view but doesn't appear in lifecycle environment to Puppet module appear in content view but doesn't appear in lifecycle environment
  • Target version set to 140
  • Difficulty set to easy

#2 Updated by The Foreman Bot over 4 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Brad Buckingham
  • Pull request https://github.com/Katello/katello/pull/6464 added

#3 Updated by Brad Buckingham over 4 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#4 Updated by Justin Sherrill over 4 years ago

  • Legacy Backlogs Release (now unused) set to 188

Also available in: Atom PDF