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.
DescriptionJitendra Yejare
2018-05-29 12:21:54 UTC
Description of problem:
The taxonomies in template metadata are not getting overridden explicitly while importing it. The template gets imported in org and loc mentioned in template metadata.
Version-Release number of selected component (if applicable):
Satellite 6.3 snap 5.0
How reproducible:
Always
Steps to Reproduce:
1. Create a template with metadata having org and loc specified
2. Attempt to import that template by explicitly providing other orgs and locs than in template metadata.
Actual results:
Template gets imported in org and loc specified in template metadata
Expected results:
The template should get imported in explicitly provided org and loc.
Additional info:
1. The test is exercised through API.
2. API doc provides 2 options for org and locs which is wrong and for that separate bug is filed.
option 1: organization_id and location_id which accepts string
option 2: organization_ids and location_ids which accepts array
The same is happening from CLI end.
@Marek, You can check this as well,
Template Metadata:
<%#
name: jacks job temp fake
snippet: false
model: JobTemplate
job_category: Miscellaneous
provider_type: SSH
kind: job_template
organizations: Default Organization
locations: Default Location
%>
The command:
# hammer import-templates --repo /usr/share/jitu/imported/ --organization-ids 3 --location-ids 4 --associate new
Where org id 3 is org1 and loc id 4 is loc1 which is not associated with template post import.
Verified !
@ Satellite 6.4 snap 11
Steps:
1. Import the template in taxonomies in explicitly mentioned taxonomies regardless to the template meatadata taxonomies.
Behavior:
The templates are being imported to explicitly mentioned taxonomies.
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-2018:2927