Creating a group fails

[Steve Larsen]

Is this because I have some setting that is only able to be set when the group actually exists?

gam create group sec_marketing name MarketingSecurityGroup description MarketingSecurityGroup gal false showingroupdirectory false whocanadd none_can_add whocanjoin invited_can_join whocanleavegroup none_can_leave whocanviewgroup all_managers_can_view whocanviewmembership all_managers_can_view whocanpostmessage none_can_post
Group: sec_ma...@fhs.marketing, Create Failed: Does not exist

[Kevin Melillo ✉]

It looks like it is trying to create sec_ma...@fhs.marketing which does not look like a fully qualified domain name email address.  Should it be

@fhs.marketing.com or something else?

--
You received this message because you are subscribed to the Google Groups "GAM for G Suite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-man...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-manager/CAA0XtT1SomOpDRfpZShUeW31a%2BOD54puLDcHqpW-GFd_zOU8aQ%40mail.gmail.com.

--

Kevin Melillo Electronic Communications Analyst, Information Technology Phone: 732.465.6609 | Mobile: 732-609-4331 Email: k.me...@ieee.org 445 Hoes Lane Piscataway, NJ 08854

[Steve Larsen]

No, it's just fhs.marketing - it's one of those new just for revenue generating pruposes TLDs now

https://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#M

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-manager/CAKM%3DboadzMSDCtUA9eDY4mMbPkK7_xwJjf2JTo9YHsdK%3D6cAyQ%40mail.gmail.com.

[Jay Lee]

When you set group settings when creating a group GAM has to make 2 API calls, one to create the group and the other to set the group settings (which is a separate API). I have seen very rare cases where the call to set the group settings fails because it doesn't think the group is created yet. Can you confirm if the group did get created here?

How reproducible is this for you? Generally "group does not exist" is a hard error but in this case, if we are certain we just created the group we can maybe assume this is just Google propagation/sync issue and do a backoff/retry.

How reproducible is this for you?

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-manager/CAA0XtT25%3DdQrH8_m6hyLBVq8_D-xX2e75g-bKdw3wXXnZMsSGg%40mail.gmail.com.

[Steve Larsen]

I ran the command 3 times with variations on the email. Same happened each time.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-manager/CA%2BVVBp8cg8Z91JqZnkM%3D%3DXVs4-yRgt9LKji6EJb%2BHNsqq_ti2Q%40mail.gmail.com.

[Steve Larsen]

It happens with creating a user too. Something is wrong with the TLD apparently. Bearer and pwd values suppressed 

Also looking at the API Explorer I get a Domain not found response with a bit more descript.

connect: (www.googleapis.com, 443)
send: b'GET /discovery/v1/apis/admin/directory_v1/rest HTTP/1.1\r\nHost: www.googleapis.com\r\nuser-agent: Python-httplib2/0.13.0 (gzip)\r\naccept-encoding: gzip, deflate\r\nif-none-match: "F5McR9eEaw0XRpaO3M9gbIugkbs/NqxQAUkUIvUDCo2pCkVJ3_L6Gh4"\r\n\r\n'
reply: 'HTTP/1.1 304 Not Modified\r\n'
header: Expires: Thu, 31 Oct 2019 19:42:30 GMT
header: Date: Thu, 31 Oct 2019 19:37:30 GMT
header: Cache-Control: public, max-age=300, must-revalidate, no-transform
header: ETag: "F5McR9eEaw0XRpaO3M9gbIugkbs/NqxQAUkUIvUDCo2pCkVJ3_L6Gh4"
header: Vary: Origin
header: Vary: X-Origin
header: Server: GSE
send: b'POST /admin/directory/v1/users?fields=primaryEmail%2Cname&prettyPrint=true&alt=json HTTP/1.1\r\nHost: www.googleapis.com\r\naccept: application/json\r\naccept-encoding: gzip, deflate\r\nuser-agent: GAMADV-XTD3 4.96.05 - https://github.com/taers232c/GAMADV-XTD3 / Ross Scroggs <ross.s...@gmail.com> / Python 3.8.0 final / Linux-4.18.0-1015-gcp-x86_64-with-glibc2.3.4 x86_64 / google-api-python-client/1.7.8 (gzip)\r\ncontent-type: application/json\r\ncontent-length: 239\r\nauthorization: Bearer ya29.c\r\n\r\n'
send: b'{"name": {"givenName": "steve", "familyName": "test"}, "primaryEmail": "te...@fhs.marketing", "password": "$/", "hashFunction": "crypt"}'
reply: 'HTTP/1.1 404 Not Found\r\n'
header: Vary: Origin
header: Vary: X-Origin
header: Content-Type: application/json; charset=UTF-8
header: Content-Encoding: gzip
header: Date: Thu, 31 Oct 2019 19:37:30 GMT
header: Expires: Thu, 31 Oct 2019 19:37:30 GMT
header: Cache-Control: private, max-age=0
header: X-Content-Type-Options: nosniff
header: X-Frame-Options: SAMEORIGIN
header: X-XSS-Protection: 1; mode=block
header: Server: GSE
header: Transfer-Encoding: chunked
User: te...@fhs.marketing, Create Failed: Does not exist

steve@gam:~/gam-data/$ gam create user test@1.a firstname steve lastname test
User: test@1.a, Create Failed: Does not exist
steve@gam:~/gam-data/$ gam create user te...@1.com firstname steve lastname test
User: te...@1.com, Create Failed: Not Authorized to access this resource/api

[Steve Larsen]

ok.. nevermind

fhc.marketing != fhs.marketing