This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 1467514 - [RFE] Add "owner" field in Activation Key that will set the owner of the provisioned host automatically
Summary: [RFE] Add "owner" field in Activation Key that will set the owner of the prov...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Activation Keys
Version: 6.2.8
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: Unspecified
Assignee: Eric Helms
QA Contact: Cole Higgins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-04 06:12 UTC by monish
Modified: 2024-06-05 21:24 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-05 21:24:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-5037 0 None Migrated None 2024-06-05 21:24:33 UTC

Description monish 2017-07-04 06:12:03 UTC
1. Proposed title of this feature request  
            
[RFE] Add "owner" field in Activation Key that will set the owner of the provisioned host automatically.
    
2. Who is the customer behind the request?  
   
Name	:Eero TORRI
Account Name :	European Parliament
Phone	:3222832776
Email	 :eero.torri.eu

    
  
    TAM customer: no
    SRM customer: no  
    Strategic: no 
      
3. What is the nature and description of the request?  

Currently hosts provisioned with satellite end up owned by the User who created them unless the operator goes to the last "Host" tab to set the correct  User / User Group as the owner. 
This makes life difficult in situation where servers are provisioned for others.

The Host Collection can be set with activation key. Similar to this, it would be interesting to create Activation Keys for different Users and organizational User Groups that would be the collective owners of the servers.

Detailed Description by Customer:

Operator (who belongs to department A in the organization hierarcy) creates a new server for department B with Satellite UI.
By default, the Owner field (in the Host object of Satellite) of the server will be set to the Operator person.  Most other parameters
of the server can be automatically set by the taxonomy, Host Groups and Activation Keys.  

In this scenario the Owner should be the User Group that contains system administrators of department B. None of the automatic configuration
mechanisms (Activation Key,  Hostgroup, parameters) seem to allow doing this automatically.  

In general, having the Operator person as the Owner (instead of a group of system administrators) is almost never the right thing to do
in large organizations.  

We use User Groups as Owner to limit the view to servers (like satellite 5 systemgroups) for our client departments with special filtered Role.

Current solution:
Operator will remember that server with HostGroup like  "/standard_el7/client1_base_server" and activation key "el7_virtual_client1" needs to have
the Owner manually assigned to User Group "Client1".



   
4. How would the customer like to achieve this? (List the functional requirements here)  
      
a) We can create an Activation Key that assigns the Owner exactly like there can be an Activation Key that assigns Host Collection (Activation keys are cheap)
b) Host  Group can assign the Owner (host groups are heavy but acceptable)
c) We create an Activation Key that assigns a Host Collection with the exact same name as the User Group of our client.  A homemade script
runs now and then to re-own the servers  in case Operator has forgotten to set the right owner.

Comment 1 Bryan Kearney 2019-02-07 12:09:26 UTC
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 2 Bryan Kearney 2019-02-28 19:35:05 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.

Comment 4 Eric Helms 2024-06-05 21:24:35 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.


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