Bug 864379

Summary: No username displayed in header message while adding/removing members from user group.
Product: [Retired] CloudForms Cloud Engine Reporter: Aziza Karol <akarol>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED EOL QA Contact: Rehana <aeolus-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 1.1.0CC: morazi
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:
Attachments:
Description Flags
header message none

Description Aziza Karol 2012-10-09 09:36:00 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.create multiple users by creating firstname as blank.
2.create a user group and try adding the members to this user group.
  
Actual results:
header message displays "These users have been added: ,  ".
see attached screenshot.

No name is dispalyed if firstname is left blank while creating users.

Expected results:
Instead of first name which is an optional field,user id should be displayed.

Additional info:
rpm -qa | grep aeolus
aeolus-conductor-doc-0.13.17-1.el6cf.noarch
rubygem-aeolus-cli-0.7.4-1.el6cf.noarch
aeolus-all-0.13.17-1.el6cf.noarch
aeolus-conductor-0.13.17-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-configure-2.8.9-1.el6cf.noarch
aeolus-conductor-daemons-0.13.17-1.el6cf.noarch
Comment 1 Aziza Karol 2012-10-09 09:36:59 UTC 
Created attachment 624013 [details]
header message