Problem: The 2 aliases we set in LDAP manage for email@example.com is not being synced to Google. In LDAP manage we updated his gapps alias to firstname.lastname@example.org to match what he has in Zimbra to fix issues he's had with getting emails sent to the all-mofo group. Here is his information in Google: jennifers-mbp:~ jhayashi$ gam info user email@example.com User: firstname.lastname@example.org First Name: Ali Last Name: Al Dallal Is a Super Admin: False Is Delegated Admin: False Has Agreed to Terms: True IP Whitelisted: False Account Suspended: False Must Change Password: False Google Unique ID: 116013045515025971414 Customer ID: C02oz2d3h Mailbox is setup: True Included in GAL: True Creation Time: 2014-12-09T02:05:00.000Z Last login time: 2015-01-09T22:13:20.000Z Google Org Unit Path: /production Photo URL: https://plus.google.com/_/focus/photos/private/AIbEiAIAAABECNbxo_rhgfGc3gEiC3ZjYXJkX3Bob3RvKig3NjE5MDVhNjQzNmMxNGM2ZTI0ZmI0ZjkyNWE0ZjA5OTYxMDNiZGU5MAGhy1ctdFhx-T0Ghfh2YQTum8R6Pg Addresses: type: work primary: True Organizations: department: 900 Mozilla Foundation customType: work location: Regional Toronto Office name: Mozilla Foundation primary: True Other Emails: type: address: email@example.com Custom Schemas: Email Aliases: firstname.lastname@example.org Groups: (2) Everybody Mofo and Moco <email@example.com> firstname.lastname@example.org <email@example.com> Licenses: Google-Apps-For-Business
Ali also wanted firstname.lastname@example.org as an alias and that was added to LDAP manage. However, after waiting several hours - we still don't see those new aliases in Google.
I believe this is currently broken because the postini transition introduced too many changes to Google at once and GADS refuses to operate on any objects with that many changes pending. We are working on moving the postini work to an OU that is ignored by GADS, so that GADS can proceed.
This is now fixed. GADS has resumed, and I verified Ali's aliases in LDAP are now synced to google now.
Assignee: infra → jdow
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.