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-31 11:04:01 UTC
Description of problem:
The templates are not exported with associated org and loc when metadata-export-mode is set to refresh
Version-Release number of selected component (if applicable):
Satellite 6.4.0 snap 5.0
How reproducible:
Always
Steps to Reproduce:
1. Create a template in satellite and associate Org/Loc.
2. Using hammer/API, export the template containing metadata with Org/Loc specs and specify the metadata_export_mode parameter as 'refresh'.
# hammer -u admin -p changeme export-templates --metadata-export-mode refresh --repo /usr/share/jitu/exported/ --filter begawade
Actual results:
The template is not exported with associated org and location. Even there is no organizations and locations key in exported template metadata.
Expected results:
The template should be exported with associated org and location.
Additional info:
Verified !
@ Satellite 6.4 snap 12
Steps:
1. Created a template in satellite and associated Org and Loc.
2. Using hammer, exported the template containing metadata with Org and Loc and with option metadata_export_mode parameter as 'refresh'.
# hammer -u admin -p changeme export-templates --metadata-export-mode refresh --repo /usr/share/jitu/exported/ --filter begawade
Behavior:
The Provisioning Template and Partition Table template has been exported with metadata having explicitly associated org and loc.
Only, the job template is not exported with org and loc, for which Dev agree that its expected.
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