Pattern-1 fails to start

[sameerawickramasekara]

Description: In release version v2.1.0.2 Following pods does not start succesfully

wso2apim-manager-worker-455294819-tgx7h    0/1       CrashLoopBackOff   4          2m
wso2apim-worker-458565719-6h1vk                  0/1       CrashLoopBackOff   4          1m

and the log message is

user: wso2user
user home: /home/wso2user
carbon server: wso2am-2.1.0
/bin/chown: changing ownership of '/home/wso2user/wso2am-2.1.0/repository/deployment/server/': Operation not permitted

Cloud Provider : OpenStack kubectl version : v1.8.2 More info : APIM-kubernetes Pattern-1 deployment errors - dev group mail thread.

Suggested Labels: Type/Bug Priority/High

Affected Product Version: v2.1.0.2

Steps to reproduce: Follow the steps provided in the readme file.

[kasunbg]

@sameerawickramasekara can you provide a quick update on where we are on this ticket? Have someone made any progress?

[sameerawickramasekara]

The product team informed that this was not reproduced. IMO following can be a cause for this

• Permission issue from NFS drive
• OS level permission issue

It would be best if someone can review above factors.

[kasunbg]

Thanks @sameerawickramasekara.

@azinneera can you follow-up please?

[azinneera]

Ack. Will have a look.

[AmreeshTyagi]

@sameerawickramasekara I don't think it as NFS permission issue. Not sure, but I am able to mount NFS folders with rw access. This issue is coming inside docker container. I am using pattern-2 kubernetes deployment.

This is what I observed in apim-analytics, which is running fine. Permission is also updated, but here user is root but in above scenario user is wso2user. Not sure, but it can be the issue.

[AmreeshTyagi]

I found one difference in analytics dockerfile (which is working fine) & km dockerfile(which is not working as per above issue)

Difference is that, we are updating PATH variable of USER in km dockerfile but not in analytics dockerfile. It may or may not be the root cause of the issue, because we have updated global user to wso2user in PATH environment variable.

Any idea?