egeria-base chart: Glossary author cannot connect to server

[planetf1]

After deploying the egeria-base chart in master, we cannot use the glossary author UI, which fails with:

Opening here to analyze any issues with the chart itself -likely a config problem. Also need to verify the lab chart

[planetf1]

Checking logs from configuration pod --

• call to POST /open-metadata/admin-services/users/garygeeke/servers/view1/view-services/glossary-author failed

• Script should have detected this

  Curl only reports:

  > POST /open-metadata/admin-services/users/garygeeke/servers/view1/view-services/glossary-author HTTP/1.1
  > Host: base-platform:9443
  > User-Agent: curl/7.76.1
  > Accept: */*
  > Content-Type: application/json
  > Content-Length: 119
  >
  } [119 bytes data]
  * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
  { [50 bytes data]
  ^M100   119    0     0  100   119      0   3718 --:--:-- --:--:-- --:--:--  3606* Mark bundle as not supporting multiuse
  < HTTP/1.1 400
  < Content-Type: application/json
  < Transfer-Encoding: chunked
  < Date: Thu, 20 May 2021 16:39:44 GMT
  < Connection: close
  * The requested URL returned error: 400
  ^M100   119    0     0  100   119      0   1950 --:--:-- --:--:-- --:--:--  1919
  * Closing connection 0
  } [5 bytes data]
  * TLSv1.3 (OUT), TLS alert, close notify (256):
  } [2 bytes data]
  curl: (22) The requested URL returned error: 400

The server reports no error

Config script is in open-metadata-resources/open-metadata-deployment/charts/egeria-base/scripts with the segment:

# Configure the view services
 echo -e '\n\n > Setting up Glossary Author:\n'

  curl -f -k --verbose --basic admin:admin \
    --header "Content-Type: application/json" \
    "${EGERIA_ENDPOINT}/open-metadata/admin-services/users/${EGERIA_USER}/servers/${VIEW_SERVER}/view-services/glossary-author" \
    --data @- <<EOF
 {
   "class": "ViewServiceConfig",
   "omagserverPlatformRootURL": "${EGERIA_ENDPOINT}"
   "omagserverName" : "${EGERIA_SERVER}"
 }
 EOF

[planetf1]

The error was caused by a missing , in the json body. (no response body is produced in this case)