Version 1.1.23 limitations

The following limitations apply to versions 1.1.23 of Agile Service Manager.

General

Deprecation notice: The POST /types/edge API is intended for use only by the File Observer and the Rest Observer. For the other observers, this functionality will be removed in a future release.

Installation, configuration, integration, startup

Unable to reach inventory service (OCP only)

If your OCP deployment of Agile Service Manager system is installed in the same namespace as IBM Cloud Pak® for Network Automation, the connection to the inventory service breaks. This is caused by a clash with another service with the same name.

Workaround: Use the config.yaml file to enforce the correct values for INVENTORY_SERVICE_HOST and INVENTORY_SERVICE_PORT.

Example:

apiVersion: v1
kind: ConfigMap
metadata:
  name: noi-topology-sizing
  namespace: namespace
data:
  asm: |
    ui-api:
      containers:
        ui-api:
          env:
            - name: INVENTORY_SERVICE_HOST
              value: noi-topology-inventory.namespace.svc
            - name: INVENTORY_SERVICE_HOST
              value: "9178"

Failure to restart after RPM upgrade

Following an RHEL 8 update and an attempt to use asm_start.sh, the system fails to restart with the following error message:

ERROR: Network "asm_default" needs to be recreated - IPAM option "driver" has changed

Workaround 1: Run asm_stop.sh before asm_start.sh. This will recreate the network.

Workaround 2: The update may have included an upgrade to Podman 4.x, which can cause an issue with the lookup of unqualified container image names. To fix, create a file named $ASM_HOME/.config/containers/containers.conf containing the following text:

[engine] 
compat_api_enforce_docker_hub=false

This will allow Podman to resolve the short names to the local repository.

Observers

ALM Observer: Resource instance creation failure

When a resource instance fails to be created in CP4NA, the observer receives events of resource instance creation and no failure events. In this case, the observer will create a single resource instance in the topology.

Example error message:

Status code: 500
Unknown Deployment Location [asm] in resource manager [brent] for resource instance [instance4__hw-apache]

Attention:

The ALM observer supports the discovery of Cloud Pak for Network Automation (CP4NA) and has been tested against versions 2.3.x and 2.4.x.

The ALM observer was first developed to integrate with the legacy Telco Network Cloud Manager (TNCM) Orchestrator (TNCO/ALM). A re-branding from ALM (Agile Lifecycle Manager) to CP4NA happened, while the observer retained its ALM name.

The observer has some level of backward compatibility with the legacy ALM.

When creating a Kubernetes observer job that is named 'weave_scope', 'load', 'kubeconfig', or 'local', the job fails to run: If you create a Kubernetes observer job with the name `weave_scope`, `load`, `kubeconfig`, or `local`, the job always fails to run. When this error occurs, you can view an error icon in the schedule column for the job.; Workaround: To avoid this issue, do not use these names for the observer job.

'No tenant Id' warning: A WARN: Cannot schedule job with no tenantId: job1 warning message is displayed. This may affect any observer job under certain circumstances.; The warning message does not prevent the observer service from starting.; Workaround: Ignore the message.

New Relic observer: For new users of the New Relic observer, the observer will not work as it no longer supports the New Relic One dashboard token. However, it will continue to work for existing users who are using the old token that was generated previously via the old dashboard.

UI, Using

The 'Choose neighbors' functionality fails for resources without defined entityType parameters: Guided navigation counts are incorrect when no entityType exists as resources that have no entityType defined (that is, 'placeholder' resources) are not recognized.; Workaround: None

Composite resources with differing geolocation markers are plotted separately in the Resource map: On rare occasions a composite resource may contain more than one geolocation marker. All of these will be plotted on the Resource map. If one of these locations falls outside the displayed map area, its status is not displayed.; Workaround: None. Be aware of this quirk when viewing composite resource on the Resource map.

Inventory service colon (:) error (on-prem only)

When searching topologies using the Inventory Service, the use of a colon (:) results in an error.

Workaround: If a topology name includes the : character, you must either quote the search term, or escape the ':'. For example, use one of the following when searching for myFavouriteResource:two.

"myFavouriteResource:two"

myFavouriteResource\:two

Note: Search suggestions with a colon character will automatically be presented in quotes.

Search fails to roll back to previous release

Restriction: This limitation only applies to legacy releases that pre-date the new indexing service.

When updating to a new release, a new search index is created. When rolling back to a previous release, no index exists.

Workaround: Remove the topology data, then rebroadcast the data to create the index again.

Scale down the core services which access the storage:
```
oc scale deploy $release-topology-search --replicas=0
```

Clear out the search indexes:

oc exec $release-topology-elasticsearch-0 -- bash -c "curl -X DELETE 'http://localhost:9200/searchserv*'"

Scale the core services back up:

oc scale deploy $release-topology-search --replicas=2

Rebroadcast the data (specifying a tenantId) by calling the 'rebroadcast' API of the topology service. This triggers the rebroadcast of all known resources and the Search service will then index those resources in Elasticsearch:
```
https://master_fqdn/1.0/topology/swagger#!/Crawlers/rebroadcastTopology
```

Problems specifying composite seed for dynamic templates: Dynamic templates can fail to find expected seeds when composites are involved. As a result, a composite seed may fail to be included as a seed of a dynamic template (when it should be).; This error only occurs when one resource of a composite has the entity type, while another has the tag.; Workaround: When you encounter this issue, limit the seed entity type and tag selection to types and tags on the same resource member of the composite resource.

Resources with a _compositeId value have 'Related Services' and 'Related resource groups' tabs disabled: Group and service information cannot be fetched for resources that are part of a composite.; This defect is only encountered when viewing the related service or related resource group details of a resource that is part of a composite. This resource will have the Related services and Related resource groups tabs disabled.; Workaround: none

Reference

Swagger UI not responding during high-volume query

When querying for resources using GET /resources, the Swagger UI may become unresponsive if there are in excess of a thousand results.

Cause: This is a Swagger limitation.

Workaround: None.; Avoid high-volume queries.