cc isn

Question

cc < Prafulla Mahindrakar> < Yuvraj> < Yash Panchwatkar> isn t able to start a demo cluster on Ubuntu and RHEL 1 On Ubuntu the above screenshot explains the error 2 On RHEL the error is `context default doesn t exist` Reference

Prafulla Mahindrakar · Answer

1 Can we get docker logs from the failed container 2 Seems it failed in the last step when copying the sandbox context to local machines context and switch it over So can we check is locally we have kube config Atleast a local kube client is expected to be there before using sandbox or sandbox lite

Yash Panchwatkar · Answer

yes sure will post you soon

Yash Panchwatkar · Answer

hello < Prafulla Mahindrakar> here are the logs for the same

Yash Panchwatkar · Answer

will install local kube client and let you know current status thanks for the reply

Prafulla Mahindrakar · Answer

Not much we can get from those logs We have ticket to collect diagnostic info to help more on this <https github com flyteorg flyte issues 2192> But on RHEL your logs show it went forward but failed in last step so do let us know once you have local kube client

Yash Panchwatkar · Answer

hello < Prafulla Mahindrakar> its working when i have installed the kubernetes in backend

Yash Panchwatkar · Answer

Thanks Team for support

Yash Panchwatkar · Answer

hello < Prafulla Mahindrakar> i am trying to start sandbox environment on k8s but minio goes in crashloobbackoff again and again could you please help me to find what s getting wrong here

Yash Panchwatkar · Answer

result from describe command for minio ```Tolerations op=Exists for 300s op=Exists for 300s Events Type Reason Age From Message Normal Scheduled 16m default scheduler Successfully assigned flyte minio 5745464bb zthw8 to ip 172 31 31 189 ap south 1 compute internal Normal Pulling 16m kubelet Pulling image Normal Pulled 16m kubelet Successfully pulled image in 13 816089274s Normal Created 14m x5 over 16m kubelet Created container minio Normal Started 14m x5 over 16m kubelet Started container minio Normal Pulled 14m x4 over 16m kubelet Container image already present on machine Warning BackOff 85s x61 over 15m kubelet Back off restarting failed container``` and result from logs ``` root ip 172 31 31 189 ~ kubectl logs minio 5745464bb zthw8 n flyte 07 15 01 89 07 15 01 90 Welcome to the Bitnami minio container 07 15 01 90 Subscribe to project updates by watching 07 15 01 90 Submit issues and feature requests at 07 15 01 90 07 15 01 90 INFO == gt Starting MinIO setup 07 15 02 01 INFO == gt Starting MinIO in background 07 15 12 01 INFO == gt Adding local Minio host to mc configuration 07 15 12 41 INFO == gt MinIO is already stopped ```

Prafulla Mahindrakar · Answer

Strange we haven t seen this issue Can you check this one from bitnami issues <https github com bitnami bitnami docker minio issues 3> Which platform are you running this on and did you ever get minio pod running

Yash Panchwatkar · Answer

nope this is not working

Yash Panchwatkar · Answer

cause i have followed helm chart to install and not any dokcer container so directly run the commands which was given in <https docs flyte org en latest deployment sandbox html deployment sandbox>

Prafulla Mahindrakar · Answer

You can change to the latest minio image directly and restart the minio pod and see if that fixes the issue Flyte just reuses the minio community project Might be the version flyte comes with is not compatible on your platform and hence you can check with latest image and see if that helps Also if it still fails would be worth commenting on the issue i posted so that minio community can help more on it too

Yash Panchwatkar · Answer

so which means i need to change the helm chart conf right

Prafulla Mahindrakar · Answer

easy way would be to just edit the deployment if that works then you can edit the helm chart conf to persist this info <https github com flyteorg flyte blob master charts flyte values yaml L723>

Yash Panchwatkar · Answer

what will be the value for the same

Yash Panchwatkar · Answer

for edit

Yash Panchwatkar · Answer

```PostgreSQL init process complete ready for start up 2022 10 08 09 19 24 525 UTC 1 LOG starting PostgreSQL 13 5 Ubuntu 13 5 0ubuntu0 21 04 1 on x86 64 pc linux gnu compiled by gcc Ubuntu 10 3 0 1ubuntu1 10 3 0 64 bit 2022 10 08 09 19 24 526 UTC 1 LOG listening on IPv4 address 0 0 0 0 port 5432 2022 10 08 09 19 24 526 UTC 1 LOG listening on IPv6 address port 5432 2022 10 08 09 19 24 528 UTC 1 LOG listening on Unix socket var run postgresql s PGSQL 5432 2022 10 08 09 19 24 533 UTC 66 LOG database system was shut down at 2022 10 08 09 19 24 UTC 2022 10 08 09 19 24 539 UTC 1 LOG database system is ready to accept connections 2022 10 08 09 20 37 000 UTC 74 ERROR relation projects does not exist at character 15 2022 10 08 09 20 37 000 UTC 74 STATEMENT SELECT FROM projects WHERE state lt gt $1 ORDER BY created at desc 2022 10 08 09 20 51 434 UTC 75 FATAL database datacatalog does not exist```

Yash Panchwatkar · Answer

pleaes convey this to team so that will run smooth I was trying installation from long time but it s getting failed multiple times so if possible please let someone help me in the process

Prafulla Mahindrakar · Answer

Are you available for a call today We can check what s happening over google meet Let me know if that works or Tuesday

Yash Panchwatkar · Answer

yes I will be available what will be your preferred time

Prafulla Mahindrakar · Answer

How about 8 pm IST

Yash Panchwatkar · Answer

sure i will be available

Yash Panchwatkar · Answer

hello please join

Yash Panchwatkar · Answer

Prafulla Mahindrakar · Answer