Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Open Issues

Learn about the open issues in APM 3.1.1

  • The bbecloudsetup utility that ships with APM 3.1.1 sometimes fails to construct a working Kubernetes cluster even when the target hosts used to create the cluster are running Ubuntu version 18.04 LTS. After running bbecloudsetup at least once, and the "Apply Flannel Manifest" task of the playbook fails, apply this workaround:

    1. Login to each node of the cluster as root and enter apt-get install kubernetes-cni=1.1.1-00.

    2. Re-login in to the master node. This updates an environment variable that was set during the first install of the BBE cloud environment utility.
    3. Restart the bbecloudsetup utility from the install host.

    PR1732264

  • Private configuration mode (‘configuration private’ or ‘edit private’) is not currently supported for APM. Use the shared configuration mode (‘configure’ or ‘edit’) to make changes to APM configuration. PR1713447
  • The reclamation-hold-down attribute in the pool-domain-profile configuration statement is only supported with BNGs running 22.1R1 and higher. PR1732264

  • APMi v0 entity connections close unexpectedly with too many pings error. There might be unexpected impact to the system during times of high load while APM reconnects. Workaround: On Junos OS Releases prior to 22.1R1, we recommend setting the grpc keep-alive interval to 60 seconds when interworking with APM. Set the grpc keep-alive interval to 60 by issuing the set system services extension-service request-response grpc grpc-keep-alive 60 statement. PR1681031

  • The warning message "W: Unable to read /etc/apt/sources.list.d/kubernetes.list - open (13: Permission denied)" might display after APM installation. There is no functionality impact due to this error message and you can ignore it. PR1681963