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:
Created redmine issue http://projects.theforeman.org/issues/23896 from this bug
Upstream bug assigned to oprazak
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23896 has been resolved.
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