Issue with deployment of pre-registration. "Docker Image tag latest, 1.2.0"

Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘documentServiceUtil’: Injection of autowired dependencies failed; nested exception is java.lang.IllegalArgumentException: Could not resolve placeholder ‘s3.pretext.value’ in value “${s3.pretext.value}prereg”
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.postProcessPropertyValues(
at org.springframework.beans.factory.config.DependencyDescriptor.resolveCandidate(
at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(
… 66 common frames omitted
Caused by: java.lang.IllegalArgumentException: Could not resolve placeholder ‘s3.pretext.value’ in value “${s3.pretext.value}prereg”
at org.springframework.util.PropertyPlaceholderHelper.parseStringValue(
at org.springframework.util.PropertyPlaceholderHelper.replacePlaceholders(

@vinay.yadav8525 This is little strange. how are you running this? Are you using kubernetes or this is direct docker run?

Thanks @gsasikumar for your response. We are using kubernetes (RKE) on-premise.

ok so the error is at s3.pretext.value. Do you have some value for the same in your configuration?

No, this configuration property is not available in source code, neither in mosip-config server. So actually unable to locate. Not sure where this value is getting pulled in the docker image? Would there be a possibility of version mismatch. We had build mosip cluster using master branch and tried pulling docker images - “latest, 1.2.0-B1, 1.2.0”. All three showing the same issue.

This fix was part of our latest B2, in the khazana library. This fix was not provided to pre-registration and our dockers should not be having this problem. Are you building the docker from the source code? during installation, these values were supposed to be collected and configurations should have been set automatically.

Did the installation scripts ask these values?

@gsasikumar we are not building image from source. The docker image is being pulled from

No installation script or code having this value. (Code and config-server reference for checking purpose only)

@gsasikumar Can you help getting this resove?

@vinay.yadav8525 apologise for the delay. Can you please check this thread Packetmanager - CrashLoopBackOffF in MOSIP v1.2.0.1-B2 - #7 by vishwa

Thanks @gsasikumar for the link. We were able to come over this issue by changing branch. Now we stuck at Partner Management Portal. While accessing the portal we are getting issue with /validatetoken API with 401 unauthorized.