Sametime Meeting Pre-Release 11.5 on Kubernetes 1.17.12

HCL Sametime Sametime Forum
,
1

Hi,

I am trying to install HCL Sametime Meeting Pre-Release 11.5 on Kubernetes 1.17.12 on the cloud provider.

With recording and video pods with the status of PodInitializing, with messages of await-prosody.

# kubectl logs deployment/recorder
error: a container name must be specified for pod recorder-5f584bd6db-nzvt8, choose one of: [jibri pushgateway] or one of the init containers: [await-prosody]

# kubectl logs deployment/video
Error from server (BadRequest): container "jvb" in pod "video-647855c885-wztkh" is waiting to start: PodInitializing

Could someone help with this problem, follow the others checks below:

# kubectl get pods
NAME READY STATUS RESTARTS AGE
auth-57f55ffd7b-k9vdz 1/1 Running 0 36m
jibri-web-6f857b8655-8lm8f 1/1 Running 0 36m
jitsi-76849f946d-6vwtv 3/3 Running 0 36m
myhello-world-5964cf947b-mzqd6 1/1 Running 0 20h
myubuntu-network-8b6b6f5fc-h2dxg 1/1 Running 0 20h
recorder-5f584bd6db-nzvt8 0/2 Init:0/1 0 36m
recordings-7bb489fb46-zhllx 1/1 Running 0 36m
video-647855c885-wztkh 0/1 Init:0/1 0 36m
web-784fd6c994-v2tvd 1/1 Running 0 36m

# kubectl version --short
Client Version: v1.17.9
Server Version: v1.17.12+IKS

Thanks

2

'error: a container name must be specified for pod recorder-5f584bd6db-nzvt8, choose one of: [jibri pushgateway] or one of the init containers: [await-prosody]'

Makes me think you need to create the 'Create the meeting recordings volume.' and assign it - or you haven't assigned the pods to the correct containers in teh cloud environement.


It would be better to have a ticket on this so we can work thru it.

3

Hi, Anthony

See the container recordings using the 100GB volume.
The video / recorder containers also need a volume, because I haven't found them in the helm chart yaml.
I would like to better understand this prosody check, which is preventing containers from starting.
Thanks