On MID Server startup, GetMIDInfo/GetCloudServiceAccountInfo uses CloudServiceAccountInfoUtil script include, which queries cloud_service_account_view without checking the tables exist - Known Error

On MID Server startup, GetMIDInfo/GetCloudServiceAccountInfo uses CloudServiceAccountInfoUtil script include, which queries cloud_service_account_view without checking the tables exist Description On MID Server startup, GetMIDInfo/GetCloudServiceAccountInfo uses CloudServiceAccountInfoUtil script include, which queries cloud_service_account_view without checking the tables exist. This is common if ITOM products are not installed, and MID Servers are just being used for integrations such as REST/SOAP, LDAP and Import Sets.

Database view cloud_service_account_view joins tables cmdb_ci_cloud_service_account, cloud_service_account_aws_cross_assume_role_params and cloud_service_account_aws_org_assume_role_params. The soap webservice, script include, database view and first table are from the MID Server plugin, which all instances have enabled by default. The last 2 of those tables only exist if the "Discovery Core" (com.snc.discovery.core) plugin is installed, which a lot of instances will not have.

syslog will show the following warning:

org.mozilla.javascript.EvaluatorException: GlideRecord.addNotNullQuery() - invalid table name: cloud_service_account_view (sys_script_include.392afd336b783010da1e64ed1e44afb9.script; line 20)

MID Server log shows the following Error:

INFO (StartupSequencer) [CloudServiceAccountInfo:100] About to load/reload cloud service account information from the instance... ERROR (StartupSequencer) [CloudServiceAccountInfo:391] Failed to parse cloud service account information from XML payload from instance. WARN (StartupSequencer) [CloudServiceAccountInfo:110] Was not able to load/reload cloud service account information from the instance.

Steps to Reproduce

In a Tokyo instance (although also seen in at least San Diego Patch 7):

Do NOT install Discovery Core installed (which is a dependency of Discovery, Service Mapping, Cloud Provisioning and Governance, and others) Install and start a mid server Check syslog for anything with message contains cloud_service_account_view org.mozilla.javascript.EvaluatorException: GlideRecord.addNotNullQuery() - invalid table name: cloud_service_account_view (sys_script_include.392afd336b783010da1e64ed1e44afb9.script; line 20) EvaluatorException(JavaScript evaluation error on: if (gs.hasRole("mid_server") && (isAgentValid() || (request.purpose == "UpdatePublicKey"))) { var requestType = request.purpose; var MIDServerInfoAccessor = new GlideMIDServerInfoAccessor(); ... function getCloudServiceAccountInfo() { var cloudServiceAccountInfoUtil = new CloudServiceAccountInfoUtil(); var doc = cloudServiceAccountInfoUtil.getCloudServiceAccountInfoXML();

response.midInfo = doc; } ...

Check the agent log for the errors to do with failing to parse the response due to this problem

INFO (StartupSequencer) [CloudServiceAccountInfo:100] About to load/reload cloud service account information from the instance... ERROR (StartupSequencer) [CloudServiceAccountInfo:391] Failed to parse cloud service account information from XML payload from instance. WARN (StartupSequencer) [CloudServiceAccountInfo:110] Was not able to load/reload cloud service account information from the instance. Workaround This problem has no workaround, is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.