Search Engine: Elastic

Article ID: 132659, created on May 18, 2018, last review on May 18, 2018

  • Applies to:
  • Operations Automation 7.3


During GDPR deployment the following issue is observed on the last step:

# python /tmp/

    2018-05-14 23:49:15.863 [ERROR] {
            "error": "APS::Util::NetworkException",
            "message": "Network error: Host not found: gdpr-backend.default.svc.cluster.local.  Application endpoint: gdpr-backend.default.svc.cluster.local.  Request: POST /rest/application."


A generic reason is that Kubernetes dedicated DNS server could not be reached from OSS Core over the network.

In particular, this happens, when GDPR virtual machine is created with IP/MAC filtering enabled.

Kubernetes networking suggests bringing up virtual networks inside the VM and network communications to IPs different from VM configuration should be allowed to make it operable.

More details can be found in the official Kubernetes pages: Kubernetes Cluster Network.


Resolution for a Virtuozzo virtual machine:

# prlctl set GDPR_VM --device-set net0 --macfilter no --ipfilter no --preventpromisc no

APS Controller may keep DNS servers list in its cache, so it's recommended to perform a restart additionally:

# service pa-agent stop && service pau restart && service pa-agent start

Re-run afterwards.

5356b422f65bdad1c3e9edca5d74a1ae 8fc71f07abe5b233fea1ae0377cd5e3d dd79f16c76b9dca75205ab5e9f5465ea 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF