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 1267525 - [RFE] Variable to identify Satellite version in provisioning templates
Summary: [RFE] Variable to identify Satellite version in provisioning templates
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning Templates
Version: 6.1.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 260381 1122832
TreeView+ depends on / blocked
 
Reported: 2015-09-30 09:41 UTC by Peter Vreman
Modified: 2018-09-04 19:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 19:09:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 21613 0 None None None 2017-11-09 12:12:46 UTC

Description Peter Vreman 2015-09-30 09:41:11 UTC
Description of problem:
To be able to use the same provisioning template in multiple Satellite versions it would be good for understanding to have a variable to identify the version of Satellite also in the provisioning templates.
This variable can then be used to have clear Satellite version dependent code fragments

<% if @satellite.version >= 6.2 %>
... new satellite 6.2 features / variables
<% else %>
... legacy satellite 6.0/6.1 code
<% end %>

Alternative is to have @foreman.version


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Bryan Kearney 2016-07-08 20:48:02 UTC
Per 6.3 planning, moving out non acked bugs to the backlog

Comment 3 Ondřej Pražák 2017-11-09 12:12:43 UTC
Created redmine issue http://projects.theforeman.org/issues/21613 from this bug

Comment 4 Bryan Kearney 2018-09-04 18:58:27 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

Comment 5 Bryan Kearney 2018-09-04 19:09:57 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


Note You need to log in before you can comment on or make changes to this bug.