Error in Registration processor landing zone

Support
1

Hi Team,

We are facing an issue in the registration processor landing zone. Currently, we are not receiving regproc-landingzone version 1.2.0.1. Therefore, we changed to version 12.0.2, but we are still encountering errors in regproc-landingzone.
Please help me to resolve this issue

Helm chart version

image
image1495×80 8.14 KB

Error:
Connecting to artifactory.artifactory:80 (10.43.51.2:80)

Mon, Jul 15 2024 11:19:12 amsaving to ‘/home/mosip/additional_jars//kernel-auth-adapter.jar’

Mon, Jul 15 2024 11:19:13 amkernel-auth-adapter. 100% |********************************| 34.9M 0:00:00 ETA

Mon, Jul 15 2024 11:19:13 am’/home/mosip/additional_jars//kernel-auth-adapter.jar’ saved

Mon, Jul 15 2024 11:19:13 amNOTE: Picked up JDK_JAVA_OPTIONS: -Xms3000M -Xmx3000M

Mon, Jul 15 2024 11:19:13 amNOTE: Picked up JDK_JAVA_OPTIONS: -Xms3000M -Xmx3000M

Mon, Jul 15 2024 11:19:17 am05:49:16,011 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]

Mon, Jul 15 2024 11:19:17 am05:49:16,014 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy]

Mon, Jul 15 2024 11:19:17 am05:49:16,014 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [jar:nested:/home/mosip/registration-processor-landing-zone.jar/!BOOT-INF/lib/khazana-1.2.1-SNAPSHOT.jar!/logback.xml]

Mon, Jul 15 2024 11:19:17 am05:49:16,017 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs multiple times on the classpath.

Mon, Jul 15 2024 11:19:17 am05:49:16,017 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:nested:/home/mosip/registration-processor-landing-zone.jar/!BOOT-INF/lib/kernel-dataaccess-hibernate-1.2.1-SNAPSHOT.jar!/logback.xml]

Mon, Jul 15 2024 11:19:17 am05:49:16,017 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:nested:/home/mosip/registration-processor-landing-zone.jar/!BOOT-INF/lib/kernel-pdfgenerator-itext-1.2.1-SNAPSHOT.jar!/logback.xml]

Mon, Jul 15 2024 11:19:17 am05:49:16,017 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:nested:/home/mosip/registration-processor-landing-zone.jar/!BOOT-INF/lib/kernel-templatemanager-velocity-1.2.1-SNAPSHOT.jar!/logback.xml]

Mon, Jul 15 2024 11:19:17 am05:49:16,017 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:nested:/home/mosip/registration-processor-landing-zone.jar/!BOOT-INF/lib/kernel-idvalidator-rid-1.2.1-SNAPSHOT.jar!/logback.xml]

Mon, Jul 15 2024 11:19:17 am05:49:16,017 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:nested:/home/mosip/registration-processor-landing-zone.jar/!BOOT-INF/lib/khazana-1.2.1-SNAPSHOT.jar!/logback.xml]

Mon, Jul 15 2024 11:19:17 am05:49:16,017 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:nested:/home/mosip/registration-processor-landing-zone.jar/!BOOT-INF/lib/kernel-keymanager-service-1.2.1-SNAPSHOT-lib.jar!/logback.xml]

Mon, Jul 15 2024 11:19:17 am05:49:16,108 |-INFO in ch.qos.logback.core.joran.spi.ConfigurationWatchList@7331196b - URL [jar:nested:/home/mosip/registration-processor-landing-zone.jar/!BOOT-INF/lib/khazana-1.2.1-SNAPSHOT.jar!/logback.xml] is not of type file

Mon, Jul 15 2024 11:19:17 am05:49:16,308 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set

Mon, Jul 15 2024 11:19:17 am05:49:16,315 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@2:83 - no applicable action for [springProperty], current ElementPath is [[configuration][springProperty]]

Mon, Jul 15 2024 11:19:17 am05:49:16,316 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]

Mon, Jul 15 2024 11:19:17 am05:49:16,321 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]

Mon, Jul 15 2024 11:19:17 am05:49:17,617 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO

Mon, Jul 15 2024 11:19:17 am05:49:17,617 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT]

Mon, Jul 15 2024 11:19:17 am05:49:17,617 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.

Mon, Jul 15 2024 11:19:17 am05:49:17,618 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@3f9342d4 - Registering current configuration as safe fallback point

Mon, Jul 15 2024 11:19:17 am

Mon, Jul 15 2024 11:19:18 amException in thread “main” java.lang.reflect.InvocationTargetException

Mon, Jul 15 2024 11:19:18 am at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(Unknown Source)

Mon, Jul 15 2024 11:19:18 am at java.base/java.lang.reflect.Method.invoke(Unknown Source)

Mon, Jul 15 2024 11:19:18 am at org.springframework.boot.loader.launch.Launcher.launch(Launcher.java:91)

Mon, Jul 15 2024 11:19:18 am at org.springframework.boot.loader.launch.Launcher.launch(Launcher.java:53)

Mon, Jul 15 2024 11:19:18 am at org.springframework.boot.loader.launch.PropertiesLauncher.main(PropertiesLauncher.java:574)

Mon, Jul 15 2024 11:19:18 amCaused by: java.lang.AbstractMethodError: Receiver class org.springframework.boot.env.EnvironmentPostProcessorApplicationListener does not define or inherit an implementation of the resolved method ‘abstract boolean supportsSourceType(java.lang.Class)’ of interface org.springframework.context.event.SmartApplicationListener.

Mon, Jul 15 2024 11:19:18 am at org.springframework.context.event.GenericApplicationListenerAdapter.supportsSourceType(GenericApplicationListenerAdapter.java:81)

Mon, Jul 15 2024 11:19:18 am at org.springframework.context.event.AbstractApplicationEventMulticaster.supportsEvent(AbstractApplicationEventMulticaster.java:294)

Mon, Jul 15 2024 11:19:18 am at org.springframework.context.event.AbstractApplicationEventMulticaster.retrieveApplicationListeners(AbstractApplicationEventMulticaster.java:224)

Mon, Jul 15 2024 11:19:18 am at org.springframework.context.event.AbstractApplicationEventMulticaster.getApplicationListeners(AbstractApplicationEventMulticaster.java:195)

Mon, Jul 15 2024 11:19:18 am at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:133)

Mon, Jul 15 2024 11:19:18 am at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:127)

Mon, Jul 15 2024 11:19:18 am at org.springframework.boot.context.event.EventPublishingRunListener.environmentPrepared(EventPublishingRunListener.java:74)

Mon, Jul 15 2024 11:19:18 am at org.springframework.boot.SpringApplicationRunListeners.environmentPrepared(SpringApplicationRunListeners.java:54)

Mon, Jul 15 2024 11:19:18 am at org.springframework.boot.SpringApplication.prepareEnvironment(SpringApplication.java:358)

Mon, Jul 15 2024 11:19:18 am at org.springframework.boot.SpringApplication.run(SpringApplication.java:317)

Mon, Jul 15 2024 11:19:18 am at org.springframework.boot.SpringApplication.run(SpringApplication.java:1255)

Mon, Jul 15 2024 11:19:18 am at org.springframework.boot.SpringApplication.run(SpringApplication.java:1243)

Mon, Jul 15 2024 11:19:18 am at io.mosip.registration.processor.RegistrationProcessorLandingZoneApplication.main(RegistrationProcessorLandingZoneApplication.java:23)

Mon, Jul 15 2024 11:19:18 am … 5 more

2

Dear @Jayant,

We are looking into your query and one of our expert colleagues will respond here with inputs to resolve it.

Best Regards
Team MOSIP

3

Dear @syed.salman , please check this query and see anything from DevOps team can help quickly?

4

@Jayant

Could you please provide full logs of the regproc landing-zone pod, please use the below command to get the previous container logs

kubectl -n regproc logs <pod-name> --previous

Also, share the details of pod via the below command:

kubectl -n regproc describe pod <pod-name>
5

Hi @Jayant ,

Is this issue resolved from your end. if not could you please share the logs for the team to analyze.

Regards,
Varaniya
On behalf of MOSIP

1 Like
6

Hy @Varaniya1 , I’m having the same issue with regproc-landingzone
These are my logs

(base) [k8s:prod-prgs] ➜  config-server git:(release-1.2.0.1) ✗ kubectl -n regproc logs regproc-landingzone-5fddc54698-wzwzn
Connecting to artifactory.artifactory:80 (172.16.95.6:80)
saving to '/home/mosip/additional_jars//kernel-auth-adapter.jar'
kernel-auth-adapter.   4% |*                               | 1584k  0:00:21 ETA
kernel-auth-adapter. 100% |********************************| 34.9M  0:00:00 ETA
'/home/mosip/additional_jars//kernel-auth-adapter.jar' saved
NOTE: Picked up JDK_JAVA_OPTIONS: -Xms3000M -Xmx3000M
NOTE: Picked up JDK_JAVA_OPTIONS: -Xms3000M -Xmx3000M
03:48:52,644 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
03:48:52,648 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy]
03:48:52,648 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [jar:nested:/home/mosip/registration-processor-landing-zone.jar/!BOOT-INF/lib/khazana-1.2.1-SNAPSHOT.jar!/logback.xml]
03:48:52,728 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs multiple times on the classpath.
03:48:52,728 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:nested:/home/mosip/registration-processor-landing-zone.jar/!BOOT-INF/lib/kernel-dataaccess-hibernate-1.2.1-SNAPSHOT.jar!/logback.xml]
03:48:52,728 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:nested:/home/mosip/registration-processor-landing-zone.jar/!BOOT-INF/lib/kernel-pdfgenerator-itext-1.2.1-SNAPSHOT.jar!/logback.xml]
03:48:52,728 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:nested:/home/mosip/registration-processor-landing-zone.jar/!BOOT-INF/lib/kernel-templatemanager-velocity-1.2.1-SNAPSHOT.jar!/logback.xml]
03:48:52,728 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:nested:/home/mosip/registration-processor-landing-zone.jar/!BOOT-INF/lib/kernel-idvalidator-rid-1.2.1-SNAPSHOT.jar!/logback.xml]
03:48:52,728 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:nested:/home/mosip/registration-processor-landing-zone.jar/!BOOT-INF/lib/khazana-1.2.1-SNAPSHOT.jar!/logback.xml]
03:48:52,728 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:nested:/home/mosip/registration-processor-landing-zone.jar/!BOOT-INF/lib/kernel-keymanager-service-1.2.1-SNAPSHOT-lib.jar!/logback.xml]
03:48:52,742 |-INFO in ch.qos.logback.core.joran.spi.ConfigurationWatchList@3f9342d4 - URL [jar:nested:/home/mosip/registration-processor-landing-zone.jar/!BOOT-INF/lib/khazana-1.2.1-SNAPSHOT.jar!/logback.xml] is not of type file
03:48:53,027 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
03:48:53,036 |-ERROR in ch.qos.logback.core.joran.spi.Interpreter@2:83 - no applicable action for [springProperty], current ElementPath  is [[configuration][springProperty]]
03:48:53,036 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
03:48:53,043 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]
03:48:54,727 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO
03:48:54,727 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT]
03:48:54,728 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
03:48:54,729 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@ab7395e - Registering current configuration as safe fallback point

Exception in thread "main" java.lang.reflect.InvocationTargetException
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(Unknown Source)
	at java.base/java.lang.reflect.Method.invoke(Unknown Source)
	at org.springframework.boot.loader.launch.Launcher.launch(Launcher.java:91)
	at org.springframework.boot.loader.launch.Launcher.launch(Launcher.java:53)
	at org.springframework.boot.loader.launch.PropertiesLauncher.main(PropertiesLauncher.java:574)
Caused by: java.lang.AbstractMethodError: Receiver class org.springframework.boot.env.EnvironmentPostProcessorApplicationListener does not define or inherit an implementation of the resolved method 'abstract boolean supportsSourceType(java.lang.Class)' of interface org.springframework.context.event.SmartApplicationListener.
	at org.springframework.context.event.GenericApplicationListenerAdapter.supportsSourceType(GenericApplicationListenerAdapter.java:81)
	at org.springframework.context.event.AbstractApplicationEventMulticaster.supportsEvent(AbstractApplicationEventMulticaster.java:294)
	at org.springframework.context.event.AbstractApplicationEventMulticaster.retrieveApplicationListeners(AbstractApplicationEventMulticaster.java:224)
	at org.springframework.context.event.AbstractApplicationEventMulticaster.getApplicationListeners(AbstractApplicationEventMulticaster.java:195)
	at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:133)
	at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:127)
	at org.springframework.boot.context.event.EventPublishingRunListener.environmentPrepared(EventPublishingRunListener.java:74)
	at org.springframework.boot.SpringApplicationRunListeners.environmentPrepared(SpringApplicationRunListeners.java:54)
	at org.springframework.boot.SpringApplication.prepareEnvironment(SpringApplication.java:358)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:317)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1255)
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1243)
	at io.mosip.registration.processor.RegistrationProcessorLandingZoneApplication.main(RegistrationProcessorLandingZoneApplication.java:23)
	... 5 more

this is the pod defintion

(base) [k8s:prod-prgs] ➜  config-server git:(release-1.2.0.1) ✗ kubectl -n regproc describe pod regproc-landingzone-5fddc54698-wzwzn
Name:             regproc-landingzone-5fddc54698-wzwzn
Namespace:        regproc
Priority:         0
Service Account:  regproc-landingzone
Node:             ip-10-197-8-14.eu-west-1.compute.internal/10.197.8.14
Start Time:       Tue, 27 Aug 2024 05:40:45 +0200
Labels:           app.kubernetes.io/instance=regproc-landingzone
                  app.kubernetes.io/managed-by=Helm
                  app.kubernetes.io/name=regproc-landingzone
                  helm.sh/chart=regproc-landingzone-12.0.2
                  pod-template-hash=5fddc54698
                  security.istio.io/tlsMode=istio
                  service.istio.io/canonical-name=regproc-landingzone
                  service.istio.io/canonical-revision=latest
Annotations:      istio.io/rev: default
                  kubectl.kubernetes.io/default-container: regproc-landingzone
                  kubectl.kubernetes.io/default-logs-container: regproc-landingzone
                  prometheus.io/path: /stats/prometheus
                  prometheus.io/port: 15020
                  prometheus.io/scrape: true
                  sidecar.istio.io/status:
                    {"initContainers":["istio-init"],"containers":["istio-proxy"],"volumes":["workload-socket","credential-socket","workload-certs","istio-env...
Status:           Running
IP:               10.197.9.164
IPs:
  IP:           10.197.9.164
Controlled By:  ReplicaSet/regproc-landingzone-5fddc54698
Init Containers:
  istio-init:
    Container ID:  containerd://9a8b28bfac5dfa299777cff14aa6009db1367e8a9d82c77aad332971eeac0ad8
    Image:         docker.io/istio/proxyv2:1.21.0
    Image ID:      docker.io/istio/proxyv2@sha256:1b10ab67aa311bcde7ebc18477d31cc73d8169ad7f3447d86c40a2b056c456e4
    Port:          <none>
    Host Port:     <none>
    Args:
      istio-iptables
      -p
      15001
      -z
      15006
      -u
      1337
      -m
      REDIRECT
      -i
      *
      -x

      -b
      *
      -d
      15090,15021,15020
      --log_output_level=default:info
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Tue, 27 Aug 2024 05:40:47 +0200
      Finished:     Tue, 27 Aug 2024 05:40:47 +0200
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     2
      memory:  1Gi
    Requests:
      cpu:        10m
      memory:     40Mi
    Environment:  <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-zv5wn (ro)
Containers:
  regproc-landingzone:
    Container ID:   containerd://2ecc0e94292a8fac037f0f07a8a1f81280c121cf68fb5a8a427be4e71e1b085c
    Image:          docker.io/mosipdev/registration-processor-landing-zone:develop
    Image ID:       docker.io/mosipdev/registration-processor-landing-zone@sha256:dc1d7b99cffaf6fe160eefc0b3da4b1e6019818268f2a703bbfa302ab0ca2ba0
    Port:           <none>
    Host Port:      <none>
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Tue, 27 Aug 2024 05:48:48 +0200
      Finished:     Tue, 27 Aug 2024 05:48:59 +0200
    Ready:          False
    Restart Count:  6
    Limits:
      cpu:     500m
      memory:  4000Mi
    Requests:
      cpu:      100m
      memory:   1000Mi
    Liveness:   http-get http://:15020/app-health/regproc-landingzone/livez delay=20s timeout=5s period=10s #success=1 #failure=6
    Readiness:  http-get http://:15020/app-health/regproc-landingzone/readyz delay=0s timeout=5s period=10s #success=1 #failure=6
    Startup:    http-get http://:15020/app-health/regproc-landingzone/startupz delay=0s timeout=5s period=10s #success=1 #failure=30
    Environment Variables from:
      global               ConfigMap  Optional: false
      config-server-share  ConfigMap  Optional: false
      artifactory-share    ConfigMap  Optional: false
    Environment:
      container_user:    mosip
      JDK_JAVA_OPTIONS:  -Xms3000M -Xmx3000M
    Mounts:
      /mnt/landing from landing-folder (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-zv5wn (ro)
  istio-proxy:
    Container ID:  containerd://a6dac083080eb77c788be97ec69537fe795c1ae4dcc7663fa568ab64051330f2
    Image:         docker.io/istio/proxyv2:1.21.0
    Image ID:      docker.io/istio/proxyv2@sha256:1b10ab67aa311bcde7ebc18477d31cc73d8169ad7f3447d86c40a2b056c456e4
    Port:          15090/TCP
    Host Port:     0/TCP
    Args:
      proxy
      sidecar
      --domain
      $(POD_NAMESPACE).svc.cluster.local
      --proxyLogLevel=warning
      --proxyComponentLogLevel=misc:error
      --log_output_level=default:info
    State:          Running
      Started:      Tue, 27 Aug 2024 05:41:00 +0200
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     2
      memory:  1Gi
    Requests:
      cpu:      10m
      memory:   40Mi
    Readiness:  http-get http://:15021/healthz/ready delay=0s timeout=3s period=15s #success=1 #failure=4
    Startup:    http-get http://:15021/healthz/ready delay=0s timeout=3s period=1s #success=1 #failure=600
    Environment:
      JWT_POLICY:                    third-party-jwt
      PILOT_CERT_PROVIDER:           istiod
      CA_ADDR:                       istiod.istio-system.svc:15012
      POD_NAME:                      regproc-landingzone-5fddc54698-wzwzn (v1:metadata.name)
      POD_NAMESPACE:                 regproc (v1:metadata.namespace)
      INSTANCE_IP:                    (v1:status.podIP)
      SERVICE_ACCOUNT:                (v1:spec.serviceAccountName)
      HOST_IP:                        (v1:status.hostIP)
      ISTIO_CPU_LIMIT:               2 (limits.cpu)
      PROXY_CONFIG:                  {}

      ISTIO_META_POD_PORTS:          [
                                     ]
      ISTIO_META_APP_CONTAINERS:     regproc-landingzone
      GOMEMLIMIT:                    1073741824 (limits.memory)
      GOMAXPROCS:                    2 (limits.cpu)
      ISTIO_META_CLUSTER_ID:         Kubernetes
      ISTIO_META_NODE_NAME:           (v1:spec.nodeName)
      ISTIO_META_INTERCEPTION_MODE:  REDIRECT
      ISTIO_META_WORKLOAD_NAME:      regproc-landingzone
      ISTIO_META_OWNER:              kubernetes://apis/apps/v1/namespaces/regproc/deployments/regproc-landingzone
      ISTIO_META_MESH_ID:            cluster.local
      TRUST_DOMAIN:                  cluster.local
      ISTIO_PROMETHEUS_ANNOTATIONS:  {"scrape":"true","path":"","port":""}
      ISTIO_KUBE_APP_PROBERS:        {"/app-health/regproc-landingzone/livez":{"httpGet":{"path":"/registrationprocessor/v1/landingzone/actuator/health","port":8098,"scheme":"HTTP"},"timeoutSeconds":5},"/app-health/regproc-landingzone/readyz":{"httpGet":{"path":"/registrationprocessor/v1/landingzone/actuator/health","port":8098,"scheme":"HTTP"},"timeoutSeconds":5},"/app-health/regproc-landingzone/startupz":{"httpGet":{"path":"/registrationprocessor/v1/landingzone/actuator/health","port":8098,"scheme":"HTTP"},"timeoutSeconds":5}}
    Mounts:
      /etc/istio/pod from istio-podinfo (rw)
      /etc/istio/proxy from istio-envoy (rw)
      /var/lib/istio/data from istio-data (rw)
      /var/run/secrets/credential-uds from credential-socket (rw)
      /var/run/secrets/istio from istiod-ca-cert (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-zv5wn (ro)
      /var/run/secrets/tokens from istio-token (rw)
      /var/run/secrets/workload-spiffe-credentials from workload-certs (rw)
      /var/run/secrets/workload-spiffe-uds from workload-socket (rw)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  workload-socket:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  credential-socket:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  workload-certs:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  istio-envoy:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:     Memory
    SizeLimit:  <unset>
  istio-data:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  istio-podinfo:
    Type:  DownwardAPI (a volume populated by information about the pod)
    Items:
      metadata.labels -> labels
      metadata.annotations -> annotations
  istio-token:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  43200
  istiod-ca-cert:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      istio-ca-root-cert
    Optional:  false
  landing-folder:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  regproc-group1
    ReadOnly:   false
  kube-api-access-zv5wn:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  13m                   default-scheduler  Successfully assigned regproc/regproc-landingzone-5fddc54698-wzwzn to ip-10-197-8-14.eu-west-1.compute.internal
  Normal   Pulled     13m                   kubelet            Container image "docker.io/istio/proxyv2:1.21.0" already present on machine
  Normal   Created    13m                   kubelet            Created container istio-init
  Normal   Started    13m                   kubelet            Started container istio-init
  Normal   Created    13m                   kubelet            Created container istio-proxy
  Normal   Pulled     13m                   kubelet            Successfully pulled image "docker.io/mosipdev/registration-processor-landing-zone:develop" in 11.937s (11.937s including waiting)
  Normal   Pulled     13m                   kubelet            Container image "docker.io/istio/proxyv2:1.21.0" already present on machine
  Normal   Started    13m                   kubelet            Started container istio-proxy
  Normal   Created    12m (x2 over 13m)     kubelet            Created container regproc-landingzone
  Normal   Pulled     12m                   kubelet            Successfully pulled image "docker.io/mosipdev/registration-processor-landing-zone:develop" in 568ms (568ms including waiting)
  Warning  Unhealthy  11m (x7 over 12m)     kubelet            Startup probe failed: HTTP probe failed with statuscode: 500
  Normal   Pulling    11m (x3 over 13m)     kubelet            Pulling image "docker.io/mosipdev/registration-processor-landing-zone:develop"
  Normal   Started    8m14s (x6 over 13m)   kubelet            Started container regproc-landingzone
  Warning  BackOff    3m11s (x43 over 11m)  kubelet            Back-off restarting failed container regproc-landingzone in pod regproc-landingzone-5fddc54698-wzwzn_regproc(4fe49db1-482c-4b9b-af2f-90e333668add)
7

Hey @Tommaso_Doninelli ,

Thanks for notifying your issue. let me check on this issue internally with my team and revert back to you.

8

Hi @Tommaso_Doninelli

We should use the release images which are in available in mosipid.
Please change the docker image to mosipid/registration-processor-landing-zone:1.2.0.1 and try.

9

Hey @Tommaso_Doninelli ,

have you tried with the released docker image as suggested? are you facing this issue yet.

Please do reach out to us if you are facing this issue yet.

Regards,
MOSIP Team