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.

Description of problem: 'hammer virt-who-config" has an arg ``-satellite-url`` to specify the satellite hostname. 

However, it does not handle URLs properly. We should consider changing it to --satellite-server to match the webui and other things. 


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

I suppose that would be --satellite-server-fqdn then? Btw this is current help output

> --satellite-url SATELLITE_URL             Satellite server FQDN

This name is derived from API attribute name. I don't think it's a big issue, just nice to have.

I think just --satellite-server for the option is fine. This matches the hypervisor-server option

Agreed though this is just a nice to have.

Created redmine issue http://projects.theforeman.org/issues/22123 from this bug

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 Rich Jerrido or Bryan Kearney. Thank you.