Bug 1255017

Summary: [vdsm-python] SASL_USERNAME is vdsm@ovirt instead of vdsm@rhevh on downstream
Product: Red Hat Enterprise Virtualization Manager Reporter: Jiri Belka <jbelka>
Component: vdsmAssignee: Nobody <nobody>
Status: CLOSED NOTABUG QA Contact: Aharon Canan <acanan>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.6.0CC: amureini, bazulay, ecohen, gklein, jbelka, lpeer, lsurette, oourfali, ycui, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-24 08:37:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jiri Belka 2015-08-19 12:44:14 UTC
Description of problem:

# grep -IR vdsm@ /usr/lib/python2.7/site-packages
/usr/lib/python2.7/site-packages/vdsm/tool/configurators/passwd.py:SASL_USERNAME = "vdsm@ovirt"
igurators/passwd.py3 ~]# rpm -qf /usr/lib/python2.7/site-packages/vdsm/tool/conf 
vdsm-python-4.17.2-1.el7ev.noarch

Version-Release number of selected component (if applicable):
3.6.0-9 / vdsm-python-4.17.2-1.el7ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. check what user vdsm creates for libvirt
2.
3.

Actual results:
vdsm@ovirt

Expected results:
vdsm@rhevh

Additional info:

Comment 1 Oved Ourfali 2015-08-24 06:30:49 UTC
Why does it matter?
Any functional issue?

Comment 2 Jiri Belka 2015-08-24 08:18:54 UTC
It was always like this.

Comment 3 Oved Ourfali 2015-08-24 08:37:58 UTC
(In reply to Jiri Belka from comment #2)
> It was always like this.

Chatting with Dan it was changed a while ago, and it really is something internal.
Closing as NOTABUG.