deploy_logging.sh fails when trying to load content into OpenSearch

[gsmith-sas]

@ahsokm07 reports:

I have the same problem. I have verified i have sufficient resources in my cluster.

Release "es-exporter" does not exist. Installing it now.
NAME: es-exporter
LAST DEPLOYED: Fri Jun 7 17:00:34 2024
NAMESPACE: logging
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:

1. Get the application URL by running these commands:
   export POD_NAME=$(kubectl get pods --namespace logging -l "app=v4m-es-exporter" -o jsonpath="{.items[0].metadata.name}")
   echo "Visit http://127.0.0.1:9108/metrics to use your application"
   kubectl port-forward $POD_NAME 9108:9108 --namespace logging
   INFO Elasticsearch metric exporter has been deployed

INFO Loading Content into OpenSearch
ERROR Unable to identify the temporary port used for port-forwarding [v4m-search]; exiting script.
ERROR Exiting script [deploy_logging.sh] due to an error executing the command [logging/bin/deploy_opensearch_content.sh].

I see following resources in my name space

NAME READY STATUS RESTARTS AGE
pod/v4m-es-exporter-6854fd79f7-gl72g 1/1 Running 0 4m4s
pod/v4m-osd-78f8ddfc57-j98k5 1/1 Running 0 13m
pod/v4m-search-0 1/1 Running 0 8m24s
pod/v4m-search-1 1/1 Running 0 8m24s
pod/v4m-search-2 1/1 Running 0 8m24s

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/v4m-es-exporter ClusterIP 10.0.3.144 9108/TCP 4m5s
service/v4m-osd ClusterIP 10.0.253.147 5601/TCP 13m
service/v4m-search ClusterIP 10.0.121.64 9200/TCP,9300/TCP 8m26s
service/v4m-search-headless ClusterIP None 9200/TCP,9300/TCP,9600/TCP 8m26s

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/v4m-es-exporter 1/1 1 1 4m5s
deployment.apps/v4m-osd 1/1 1 1 13m

NAME DESIRED CURRENT READY AGE
replicaset.apps/v4m-es-exporter-6854fd79f7 1 1 1 4m5s
replicaset.apps/v4m-osd-78f8ddfc57 1 1 1 13m

NAME READY AGE
statefulset.apps/v4m-search 3/3 8m27s

Originally posted by @ahsokm07 in #520 (comment)

[gsmith-sas]

Closing...duplicate of #649