Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1787355

Summary:	[API] [Import] The skip message in additional errors in not shown, for filter based skipped template
Product:	Red Hat Satellite	Reporter:	Jitendra Yejare <jyejare>
Component:	Templates Plugin	Assignee:	Ondřej Pražák <oprazak>
Status:	CLOSED ERRATA	QA Contact:	Jitendra Yejare <jyejare>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.7.0	CC:	mhulan, oprazak, pcreech
Target Milestone:	6.7.0	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-foreman_templates-7.0.6-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-14 13:28:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jitendra Yejare 2020-01-02 14:27:40 UTC

Description of problem:
Earlier the 'additional errors' used to show an error/info not importing the template due to the filter while importing the templates. But that seems to be not working now.

Version-Release number of selected component (if applicable):
Satellite 6.7 snap 7

How reproducible:
Always

Steps to Reproduce:
1. Using API calls, Attempt to import the template with a name that does not match the filter.

Actual results:
1. The json output does not have an info 'Name is not matching filter condition, skipping' text and it shows None.

Expected results:
1. Assert json output should have an info contains 'Name is not matching filter condition, skipping' text.

Additional info:

Comment 4 Ondřej Pražák 2020-01-03 13:25:20 UTC

Created redmine issue https://projects.theforeman.org/issues/28632 from this bug

Comment 5 Ondřej Pražák 2020-01-03 13:34:49 UTC

The information about template being filtered out was moved out of the additional_errors into additional_info field. The additional_info will need to be exposed in API.

Comment 6 Bryan Kearney 2020-01-03 15:01:08 UTC

Upstream bug assigned to oprazak

Comment 7 Bryan Kearney 2020-01-03 15:01:10 UTC

Upstream bug assigned to oprazak

Comment 8 Bryan Kearney 2020-01-14 09:01:18 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28632 has been resolved.

Comment 9 Jitendra Yejare 2020-01-17 07:42:51 UTC

Verified!

@Satellite 6.7 snap 8


Steps:
-----------
1. Using API calls, Attempt to import the template with a name that does not match the filter.


Behavior:
------------
1. The json output now shows an info 'Skipping, 'name' filtered out based on 'filter' and 'negate' settings' text in additional_info.

Comment 12 errata-xmlrpc 2020-04-14 13:28:12 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1454