Bug 1291775

Summary:	[RFE] Choose puppet class while creating a Smart Variable from any other class.
Product:	Red Hat Satellite	Reporter:	Jitendra Yejare <jyejare>
Component:	Smart Variables	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	Nightly	CC:	inecas, jyejare, orabin
Target Milestone:	Unspecified	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/12833
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-13 11:34:14 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:
Bug Depends On:
Bug Blocks:	1278718

Description Jitendra Yejare 2015-12-15 15:15:37 UTC

Description of problem:
I believe we should be able to choose puppet class while creating a Smart Variable. As of now we can do that after editing variable.

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


How reproducible:
Always 

Scenario 1:
Steps to Reproduce:
-> From Config -> Classes -> Class -> Smart Variables, create a new Smart Variable.
Actual results:
-> The smart variable is created in the same class from where we created it.

Scenario 2:
Steps:
-> Edit the above created variable. And Change the Puppet Class it belongs to.
Actual Result:
This changes the puppet class of that smart variable.

Expected results:
we should be able to choose puppet class while 'creating' Smart Variable.

Additional info:

Comment 4 Ivan Necas 2016-04-26 12:16:22 UTC

I'm not sure being able to select a puppet class for a smart variable while being in a context of one puppet class wouldn't cause too much confusion. What about being able to create a smart variable from the list of smart variables?

IMO that would make more sense and could be prepared for non-puppet smart variables.

Comment 5 Ivan Necas 2016-04-26 12:35:38 UTC

Moving target to 6.3, as it would not make much sense until we have puppet-independent class variables

Comment 6 Jitendra Yejare 2016-06-06 08:25:36 UTC

@Ivan,

Good Suggestion ! I would vote for creating a smart var from Smart Variables list which will allow us to choose puppet class there itself.

Comment 7 Bryan Kearney 2016-07-08 20:39:51 UTC

Per 6.3 planning, moving out non acked bugs to the backlog

Comment 9 Bryan Kearney 2016-08-10 19:12:12 UTC

Upstream bug component is Configuration Management

Comment 10 Bryan Kearney 2016-08-10 20:13:10 UTC

Upstream bug component is Provisioning

Comment 11 Bryan Kearney 2016-08-10 22:12:49 UTC

Upstream bug component is Configuration Management

Comment 12 Bryan Kearney 2016-08-12 12:50:37 UTC

Upstream bug component is Smart Variables

Comment 13 orabin 2016-12-13 11:34:14 UTC

As per comment 6 this request has changed to allow creating a new smart variable from the smart variable list, which already has a bz: 1373447.

*** This bug has been marked as a duplicate of bug 1373447 ***