Hi Pablo,
in order to have a supported DB I installed Oracle 11gR2 on another CentOS6 server. I tested the connection via my personal laptop with Oracle SQL developer and everything works.
Then I modified the configuration file to take into account the new DB. This is the content of the file:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
# ###########################################################################################################
# Review LICENSE folder, read the license agreement carefully and set ACCEPT_EULA=1 to agree with the
# license and conditions, and to be able to create & configure Kubernetes.
#
# eg:
# ACCEPT_EULA="1"
# ###########################################################################################################
ACCEPT_EULA="1"
# ###########################################################################################################
# Update configuration
# The values that are of format <XXXX> have to be replaced.
# eg:
# EXTERNAL_HOST="<EXTERNAL_FQDN_FOR_INGRESS>"
# ###########################################################################################################
# Ingress External Host, both http & https is supported for ingress protocol
EXTERNAL_HOST="muntest001197.bpc.broadcom.net"
# ###########################################################################################################
# Enabling SSL/TLS for ingress
# eg:
# SSL_REDIRECT=true - to enable SSL and redirect network traffic to SSL
# SSL_CERTIFICATE_NAME=casm-ssl.certificate, give the certificate name here.
# KEY_FILE=/opt/CA/casm-ssl.key, give the complete path of KEY_FILE.
# CERT_FILE=/opt/CA/casm-ssl.cert, give the complete path of CERT_FILE.
# ###########################################################################################################
SSL_REDIRECT=false
SSL_CERTIFICATE_NAME=
KEY_FILE=
CERT_FILE=
# ###########################################################################################################
# Database configuration
# eg:
# MDB_DATABASE_TYPE="<MDB_TYPE>", MDB_DATABASE_NAME="mdb", MDB_DATABASE_SERVER="<MDB_SERVER_IP>",
# MDB_DATABASE_INSTANCE="<DB_INSTANCE_NAME>", MDB_DATABASE_PORT="<MDB_LISTENING_PORT>"
# MDB_DATABASE_USER="<SYSTEM_USER>", MDB_DATABASE_NAMESPACE="<MDB_NAMESPACE>"
# ###########################################################################################################
# MDB Type. e.g. oracle for Oracle Database / mssql for Microsoft SQL Server Database
MDB_DATABASE_TYPE=oracle
# Database name or Oracle Service Name
MDB_DATABASE_NAME=mdb
# Database Server Hostname or IP address
MDB_DATABASE_SERVER="muntest001286.bpc.broadcom.net"
# DB instance name (Not needed for Oracle database)
MDB_DATABASE_INSTANCE=
# Database Port. e.g 1433 for MS Sql or 1521 for Oracle
MDB_DATABASE_PORT=1521
# Database system user to use when creating the DB
# For Oracle it should be "SYS"
# For MSSQL it should be "sa"
MDB_DATABASE_USER="SYS"
# Database Namespace - Specify Oracle table-space path (use file separator as /)
# e.g. C:/app/Administrator/oradata/mdb (the path needs to already exist on the Database server)
# Required only for Oracle
MDB_DATABASE_NAMESPACE=/u01/app/oracle/oradata/orcl
# ###########################################################################################################
# EEM config, provide the EEM details which we want to integrate with.
# eg:
# EEM_SERVER=<EEM_SERVER_NAME>, EEM_ADMIN_USERNAME="eiamadmin"
# ###########################################################################################################
# EEM server
EEM_SERVER=
# EEM admin username
EEM_ADMIN_USERNAME=
# ###########################################################################################################
# PAM config, provide the PAM details which we want to integrate with.
# eg:
# PAM_URL=http://<PAM_SERVER_NAME>:<PAM_SERVER_PORT>/itpam/soap, PAM_USER_NAME=pamadmin
# ###########################################################################################################
# PAM url
PAM_URL=
# PAM username
PAM_USER_NAME=
# #####################################################################
# Telemetry settings for both Service Desk Manager & Catalog
# #####################################################################
# Specify license agreement type, set "TRUE" for PLA customers else false.
TELEMETRY_PLA_AGREEMENT=FALSE
# Enterprise site id (Listed on your agreement and the Broadcom Support portal) - Required
ENTERPRISE_SITE_ID=
# Type of environment( 1 for Production, 2 for Non-Production) - Required
ENVIRONMENT_TYPE=
# Internal identifier (A department or cost center - that you use for internal tracking)
INTERNAL_IDENTIFIER=
# Company Domain (Last part of your company's email address) - Optional
COMPANY_DOMAIN=
# Proxy Server URL (Proxy Server details) - Optional
PROXY_SERVER_URL=
# Proxy User - Optional
PROXY_USER=
# #####################################################################
# Start SDM Configuration
# #####################################################################
# Supported languages ['de_de', 'en_us', 'fr_fr', 'ja_jp']
# BG & STBY Server Language
SDM_BG_LANG=en_us
# APP Server Main Language
SDM_APP_LANG=en_us
# WSP Server Language
SDM_WSP_LANG=en_us
# Main incident microservice language
INMS_LANG=en_us
# RASA language
# Supported languages ['de_de', 'en_us', 'fr_fr', 'it_it', 'es_es', 'pt_br']
RASA_LANG=en_us
# #####################################################################
# End SDM Configuration
# #####################################################################
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
And I got the following error:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Containers:
sdmbg:
Container ID: docker://51a4889af8a9ab2089f6ea3d9a6e9a615674d8cddbe2075129a4ac574fefad0d
Image: servicemanagement.packages.ca.com/ca/casm/sdm/sdm_web_en_us:hyd-368-585
Image ID: docker-pullable://servicemanagement.packages.ca.com/ca/casm/sdm/sdm_web_en_us@sha256:195475f24ce42db7db8a65f70ee185b1bf572d954b5d15d358787ffc50a9cd02
Ports: 2110/TCP, 2109/TCP, 2108/TCP, 2107/TCP, 2106/TCP, 2105/TCP, 2104/TCP, 2103/TCP, 2102/TCP, 2101/TCP, 2100/UDP, 8080/TCP
Host Ports: 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/UDP, 0/TCP
State: Terminated
Reason: Error
Message: Target(logs) dir to be created:
2020/04/13 17.42.47.875 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] 04-13,17:42:47 "/tmp/casm/mdb"
2020/04/13 17.42.48.005 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB]
2020/04/13 17.42.48.008 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] 04-13,17:42:48 Pre-install script starting...
2020/04/13 17.42.58.213 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] 04-13,17:42:58 setupmdb_pre.sh exit return code=10
2020/04/13 17.42.58.218 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] 04-13,17:42:58 setupmdb_pre.sh ERROR: No connection using connect string --
2020/04/13 17.42.58.218 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] "SYS/***@mdb AS SYSDBA"
2020/04/13 17.42.58.223 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] 04-13,17:42:58 Pre-process failed (errorlevel=10)
2020/04/13 17.42.58.225 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] 04-13,17:42:58 Setupmdb exit return code=110
2020/04/13 17.43.02.843 INFO [DeployThread: Configuring CA Service Management common tables] [ActiveProcessHolder] Exit Monitor. Process ID (PID): 42
2020/04/13 17.43.02.843 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] Command terminated with error
2020/04/13 17.43.02.843 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] Exit code of CDB script : 110
2020/04/13 17.43.02.844 INFO [DeployThread: Configuring CA Service Management common tables] [DeployThread] Saving task status to DB for task task.install_CDB
2020/04/13 17.43.02.844 INFO [DeployThread: Configuring CA Service Management common tables] [DeployThread] Skipping task update to database for CDB. Task state is not complete
docker-deploy return code 3
docker-deploy failed
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
For sure I am missing something at configuration level! But now should not be a not supported release.
Cause I am not skilled in Oracle I have doubts about:
# Database name or Oracle Service Name
MDB_DATABASE_NAME=mdb
I tested with:
MDB_DATABASE_NAME=mdb
MDB_DATABASE_NAME=orcl
MDB_DATABASE_NAME=orcl.bpc.broadcom.net (that is the oracle service name I am able to connect with via Oracle SQL Developer)
but I got the same error.
Any help is really appreciated.
Thanks in advance,
Vito
------------------------------
Vito Francesco Mazzotta
CA Technologies a Broadcom Inc. Company
mobile: +39 335 8485131 | office: +39 06 52470308
vitofrances.mazzotta@broadcom.com | broadcom.com
linkedin.com/in/vito-francesco-mazzotta-802918
------------------------------
Original Message:
Sent: 04-09-2020 04:26 PM
From: Pablo Oyarzo
Subject: Service Manager Installation Setup - Unable to connect Error on Docker K8S
Hi Vitu,
Yes, please try using a supported SQL Server version. See:
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/business-management/ca-service-management/17-3/supportability-matrix.html#concept.dita_dd801bb19d89d244b4d622363543c4d9b19fdac9_Database
Regards,
Pablo
------------------------------
Senior Support Engineer
Original Message:
Sent: 04-09-2020 10:49 AM
From: Vito Frances MAZZOTTA
Subject: Service Manager Installation Setup - Unable to connect Error on Docker K8S
Hi Pablo,
I also realized that the MSSQL installed on RHEL is MSSQL 2019. Checking on techdoc comes that the only supported for K8S environments are:
Microsoft SQL Server 2016, 2014
Should this be the issue?
Thanks in advance,
Vito
------------------------------
Vito Francesco Mazzotta
CA Technologies a Broadcom Inc. Company
mobile: +39 335 8485131 | office: +39 06 52470308
vitofrances.mazzotta@broadcom.com | broadcom.com
linkedin.com/in/vito-francesco-mazzotta-802918
Original Message:
Sent: 04-07-2020 11:25 AM
From: Pablo Oyarzo
Subject: Service Manager Installation Setup - Unable to connect Error on Docker K8S
Hi Vito,
The following links will be helpful:
https://www.blackbaud.com/files/support/infinityinstaller/content/installermaster/tkenablenamedpipesandtcpipconnections.htm
https://www.godaddy.com/help/enable-the-sql-server-browser-service-19117
Regards,
Pablo
------------------------------
Senior Support Engineer
Original Message:
Sent: 04-07-2020 02:49 AM
From: Vito Frances MAZZOTTA
Subject: Service Manager Installation Setup - Unable to connect Error on Docker K8S
Hi Pablo,
thanks for your answer.
As a first test I disabled firewalld on both master-node (centos) and mdb-server (rhel) and did some tests but it did not work.
Now I need to find out how to Enable SQL Browser in SQL Server and Enable named pipes in the SQL Server instance being used and will do more tests.
Again thanks,
Vito
------------------------------
Vito Francesco Mazzotta
CA Technologies a Broadcom Inc. Company
mobile: +39 335 8485131 | office: +39 06 52470308
vitofrances.mazzotta@broadcom.com | broadcom.com
linkedin.com/in/vito-francesco-mazzotta-802918
Original Message:
Sent: 04-06-2020 10:01 AM
From: Pablo Oyarzo
Subject: Service Manager Installation Setup - Unable to connect Error on Docker K8S
It sounds like a connectivity issue between the k8s servers and DB Server. I would recommend you to:
1- Disable Firewall on both servers.
2- Enable SQL Browser in SQL Server.
3- Enable named pipes in the SQL Server instance being used.
Regards,
Pablo
------------------------------
Senior Support Engineer
Original Message:
Sent: 04-05-2020 01:21 PM
From: Vito Frances MAZZOTTA
Subject: Service Manager Installation Setup - Unable to connect Error on Docker K8S
HI All,
I am trying to set up a test environment following the techdoc documentation starting here:
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/business-management/ca-service-management/17-3/Docker-Containers/Pre-Requisites-for-Deploying-Docker-Containers.html
So I have 1 master node and one worker node on centos plus an MSSQL on RHEL 7.6. Infrastructure is on BCP.
MSSQL is up and running, tested from my PC with SMSM and by master node with sqlcmd.
I deployed casm-docker package contained in GEN0000000002125.tar
I did all the steps:
file configurations;
./generate_secrets.sh
./apply.sh
I am getting the following situation:
[root@muntest001197 casm-docker]# kubectl get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
casm-docker sdmbg-0 0/1 CrashLoopBackOff 639 3d1h
default my-nginx-nginx-ingress-controller-7864b7856c-b8kfs 1/1 Running 0 11d
default my-nginx-nginx-ingress-default-backend-ddfb86755-pmfbg 1/1 Running 0 11d
default nfs-client-provisioner-1584983300-6b7bc8bb76-2vblt 1/1 Running 0 11d
kube-system coredns-6955765f44-czj7b 1/1 Running 2 17d
kube-system coredns-6955765f44-zdqph 1/1 Running 2 17d
kube-system etcd-muntest001197.bpc.broadcom.net 1/1 Running 2 17d
kube-system kube-apiserver-muntest001197.bpc.broadcom.net 1/1 Running 2 17d
kube-system kube-controller-manager-muntest001197.bpc.broadcom.net 1/1 Running 2 17d
kube-system kube-proxy-5xndm 1/1 Running 2 17d
kube-system kube-proxy-nqhwb 1/1 Running 0 14d
kube-system kube-scheduler-muntest001197.bpc.broadcom.net 1/1 Running 2 17d
kube-system kubernetes-dashboard-7c54d59f66-kcbbd 1/1 Running 0 8d
kube-system weave-net-2qq6p 2/2 Running 4 14d
kube-system weave-net-kn529 2/2 Running 0 14d
kubernetes-dashboard dashboard-metrics-scraper-76585494d8-6w7vj 1/1 Running 0 8d
If I check into kubectl describe I got:
Name: sdmbg-0
Namespace: casm-docker
Priority: 0
Node: muntest001199.bpc.broadcom.net/10.109.48.96
Start Time: Sun, 05 Apr 2020 17:00:47 +0000
Labels: app=casm
component=sdmbg
controller-revision-hash=sdmbg-79cf876b74
product=SDM
statefulset.kubernetes.io/pod-name=sdmbg-0
Annotations: <none>
Status: Running
IP: 10.32.0.4
IPs:
IP: 10.32.0.4
Controlled By: StatefulSet/sdmbg
Containers:
sdmbg:
Container ID: docker://3c37133a655aae6bcb2c5cd2da2d9f3d3707375bec9941395ae93ca637e43e3e
Image: servicemanagement.packages.ca.com/ca/casm/sdm/sdm_web_en_us:hyd-368-585
Image ID: docker-pullable://servicemanagement.packages.ca.com/ca/casm/sdm/sdm_web_en_us@sha256:195475f24ce42db7db8a65f70ee185b1bf572d954b5d15d358787ffc50a9cd02
Ports: 2110/TCP, 2109/TCP, 2108/TCP, 2107/TCP, 2106/TCP, 2105/TCP, 2104/TCP, 2103/TCP, 2102/TCP, 2101/TCP, 2100/UDP, 8080/TCP
Host Ports: 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/TCP, 0/UDP, 0/TCP
State: Running
Started: Sun, 05 Apr 2020 17:03:17 +0000
Last State: Terminated
Reason: Error
Message: at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:677)
2020/04/05 17.03.06.585 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] at java.sql/java.sql.DriverManager.getConnection(DriverManager.java:228)
2020/04/05 17.03.06.585 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] at com.ca.sdm.util.sql.SqlCmd.runQuery(SqlCmd.java:209)
2020/04/05 17.03.06.585 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] at com.ca.sdm.util.sql.SqlCmd.main(SqlCmd.java:174)
2020/04/05 17.03.06.598 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] 2020-Apr-05,Sun,17:03:06,UTC
2020/04/05 17.03.06.600 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] 2020-Apr-05,Sun,17:03:06,UTC ERROR: SQL command error, ERRORLEVEL=, unable to connect to master database
2020/04/05 17.03.06.606 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] 04-05,17:03:06 Pre-process failed (errorlevel=2)
2020/04/05 17.03.06.608 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] 04-05,17:03:06 Setupmdb exit return code=110
2020/04/05 17.03.15.841 INFO [DeployThread: Configuring CA Service Management common tables] [ActiveProcessHolder] Exit Monitor. Process ID (PID): 46
2020/04/05 17.03.15.842 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] Command terminated with error
2020/04/05 17.03.15.842 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] Exit code of CDB script : 110
2020/04/05 17.03.15.842 INFO [DeployThread: Configuring CA Service Management common tables] [DeployThread] Saving task status to DB for task task.install_CDB
2020/04/05 17.03.15.842 INFO [DeployThread: Configuring CA Service Management common tables] [DeployThread] Skipping task update to database for CDB. Task state is not complete
docker-deploy return code 3
docker-deploy failed
Exit Code: 2
Started: Sun, 05 Apr 2020 17:00:51 +0000
Finished: Sun, 05 Apr 2020 17:03:15 +0000
Ready: False
Restart Count: 1
Limits:
cpu: 1750m
memory: 3Gi
Requests:
cpu: 1500m
memory: 2560Mi
Readiness: http-get http://:8080/HealthServlet/GetHealth delay=240s timeout=1s period=10s #success=2 #failure=3
Environment:
POD_NAME: sdmbg-0 (v1:metadata.name)
POD_NAMESPACE: casm-docker (v1:metadata.namespace)
PRIV_USER_PWD: <set to the key 'accounts.privileged_user.password' in secret 'sdmsecret'> Optional: false
SERVER_TYPE: background_or_standby
TWO_TASK: mdb
NX_STDLOG_TO_STDOUT: Yes
NX_NAT_SINGLE_IP: Yes
NX_DB_TYPE: <set to the key 'mdb.database.type' of config map 'mdb-config'> Optional: false
DB_TYPE: <set to the key 'mdb.database.type' of config map 'mdb-config'> Optional: false
NX_ORA_DBMS_HOST: <set to the key 'mdb.database.server' of config map 'mdb-config'> Optional: false
DBMS_PORT: <set to the key 'mdb.database.port' of config map 'mdb-config'> Optional: false
NX_DB_STUFF: <set to the key 'mdb.database.name' of config map 'mdb-config'> Optional: false
INGRESS_URL: <set to the key 'ingress.url' of config map 'sdm-config'> Optional: false
Mounts:
/opt/CAisd/Promotion/Dryrun from nxroot-all (rw,path="Promotion/Dryrun")
/opt/CAisd/Promotion/Export/DB from nxroot-all (rw,path="Promotion/Export/DB")
/opt/CAisd/Promotion/Import/DB from nxroot-all (rw,path="Promotion/Import/DB")
/opt/CAisd/bopcfg/www/CATALINA_BASE/logs from nxroot (rw,path="bopcfg/www/CATALINA_BASE/logs")
/opt/CAisd/bopcfg/www/CATALINA_BASE_FS/logs from nxroot (rw,path="bopcfg/www/CATALINA_BASE_FS/logs")
/opt/CAisd/bopcfg/www/CATALINA_BASE_REST/logs from nxroot (rw,path="bopcfg/www/CATALINA_BASE_REST/logs")
/opt/CAisd/bopcfg/www/CATALINA_BASE_SA/logs from nxroot (rw,path="bopcfg/www/CATALINA_BASE_SA/logs")
/opt/CAisd/bopcfg/www/CATALINA_BASE_VIZ/logs from nxroot (rw,path="bopcfg/www/CATALINA_BASE_VIZ/logs")
/opt/CAisd/log from nxroot (rw,path="log")
/opt/CAisd/post_deploy.sh from sdm-scripts (rw,path="post_deploy.sh")
/opt/CAisd/pre_deploy.sh from sdm-scripts (rw,path="pre_deploy.sh")
/opt/CAisd/site/attachments from nxroot-all (rw,path="site/attachments")
/opt/CAisd/site/data/archive from nxroot-all (rw,path="site/data/archive")
/opt/CAisd/site/ebr from nxroot-all (rw,path="site/ebr")
/opt/CAisd/site/ebr_ADM from nxroot-all (rw,path="site/ebr_ADM")
/opt/CAisd/site/mail_attmnt_unknown from nxroot (rw,path="site/mail_attmnt_unknown")
/opt/CAisd/site/mail_queue from nxroot (rw,path="site/mail_queue")
/opt/CAisd/site/mail_undeliverable from nxroot (rw,path="site/mail_undeliverable")
/opt/CAisd/site/mods from nxroot-all (rw,path="site/mods")
/opt/CAisd/symlinks from nxroot (rw,path="symlinks")
/var/run/secrets/kubernetes.io/serviceaccount from casm-docker-user-token-fvqxr (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
nxroot:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: nxroot-sdmbg-0
ReadOnly: false
sdm-scripts:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: sdm-scripts
Optional: false
nxroot-all:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: nxroot-all
ReadOnly: false
casm-docker-user-token-fvqxr:
Type: Secret (a volume populated by a Secret)
SecretName: casm-docker-user-token-fvqxr
Optional: false
QoS Class: Burstable
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling <unknown> default-scheduler error while running "VolumeBinding" filter plugin for pod "sdmbg-0": pod has unbound immediate PersistentVolumeClaims
Warning FailedScheduling <unknown> default-scheduler error while running "VolumeBinding" filter plugin for pod "sdmbg-0": pod has unbound immediate PersistentVolumeClaims
Normal Scheduled <unknown> default-scheduler Successfully assigned casm-docker/sdmbg-0 to muntest001199.bpc.broadcom.net
Normal Pulled 72s (x2 over 3m38s) kubelet, muntest001199.bpc.broadcom.net Container image "servicemanagement.packages.ca.com/ca/casm/sdm/sdm_web_en_us:hyd-368-585" already present on machine
Normal Created 72s (x2 over 3m38s) kubelet, muntest001199.bpc.broadcom.net Created container sdmbg
Normal Started 71s (x2 over 3m37s) kubelet, muntest001199.bpc.broadcom.net Started container sdmbg
[root@muntest001197 casm-docker]#
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
I tried a lot of DB configuration for containers.config DB related entries but nothing seems to work.
Any idea on where to look to get a more in deep root cause?
Thanks in advance,
Vito
------------------------------
Vito Francesco Mazzotta
CA Technologies a Broadcom Inc. Company
mobile: +39 335 8485131 | office: +39 06 52470308
vitofrances.mazzotta@broadcom.com | broadcom.com
linkedin.com/in/vito-francesco-mazzotta-802918
------------------------------