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:
I provisioned a atomic host via satellite but when I login to host, I got 
-Bash-4.2# prompt.

It is because by default on provisioned atomic host $PS1 set as \s-\v\$.

And it should be set to like PS1='\u@\h:\w\$ '

Version-Release number of selected component (if applicable):
Sat6.2 GA snap16

How reproducible:


Steps to Reproduce:
1. provision atomic host via satellite
2. login
3.

Actual results:
shell prompt displays like: -Bash-4.2#

Expected results:
shell prompt should show hostname. Set the PS1

Additional info:
Its a minor issue but its good to update the prompt with hostname.

Created attachment 1171868 [details]
the bash prompt should show hostname

I am gonna close this bug, I see no reason why we should be "fixing" defaults that RHEL Atomic team decided to ship. Please file a bug on Atomic if you feel this is a bug, it's possible this is on purpose tho.

The PS1 variable is being set in /etc/bashrc and we do not modify this configuration in Satellite.