Unable to run Aerialist on Kubernates(k8)

[ObaidulKabirRubayed]

Hello,
I am new to px4 and aerialist and don't understand a lot of concepts. I am trying to execute mission1-k8s.yaml file by looking at read me but I am encountering issues and could not successfully run. I have tried both "python3 aerialist exec --test samples/tests/mission1-k8s.yaml" and "python3 aerialist exec --test samples/tests/mission1.yaml --agent k8s -n 5 --id mission-test --path webdav://", But both giving same error.

Here is the execution log and error I am getting.

I fear I might have wrongly configured some of the required configurations.

For reference, my .ev file is like following:

I have some confusion about the following point of the instruction:

1. 

here both of the commands are same for generating and uploading Kubeconfig file. Is this correct?

2. for step 6:
   
   I didn't find where I need to mention the output folder.
   
   Can you please tell me where to change the output folder.

I am stuck with running test on k8 for a long time. Please help me out on this.

[ObaidulKabirRubayed]

Surprisingly when I tried to run the same command from vs code. I am getting different error.

if I am not wrong it is trying to located a folder "/mission-test-26-08-10-55-13/" at the nextcloud server. Somehow it was not created by the code base.

[skhatiri]

Hi, Thanks for spotting these issues. The documentation was a bit outdated and incomplete.
I just updated the instructions with this commit: 7f13e85
I hope things are more clear now and your setup will be working with the changes.
Especially, be sure that you are setting the ENVs correctly, as mentioned.

Local K8S is an experimental feature that has not yet been used and tested much yet, so please let me know how it goes and if you get further issues. You can help improve the documentation and code as well, it will be very much appreciated.

[ObaidulKabirRubayed]

Hi, Thanks for spotting these issues. The documentation was a bit outdated and incomplete. I just updated the instructions with this commit: 7f13e85 I hope things are more clear now and your setup will be working with the changes. Especially, be sure that you are setting the ENVs correctly, as mentioned.

Local K8S is an experimental feature that has not yet been used and tested much yet, so please let me know how it goes and if you get further issues. You can help improve the documentation and code as well, it will be very much appreciated.

I have added KUBE_USE_VOLUME and KUBE_VOLUME_PATH in the .env file.

Still I am getting this error :

After debugging I have found out that, during the following code segment, inside the local //webdev//test directory, there should be some template log(.ulog) file. But, I can see the .ulog file is not being copied or generated when the files inside the test was generated in the previous steps.

Can you please advice me, why this .ulog file is not generated?

Also, I have a slight confusion, if I still need local PX4-Autopilot and catkin_ws folders. As in the .env file, two variable is defined like:

Looking forward for your help to understand this. @skhatiri

[ObaidulKabirRubayed]

After a little bit of debugging, I think it might be the case that Kubernetes implementation is not there in the main branch, I have tried to run the k8 code by reverting back commented out codes and updating them like the following:

Now, new issues are coming up like the following error:

Can you please recheck if k8 code is pushed in master branch or some part of it is still not implemented? @skhatiri

[skhatiri]

Still I am getting this error :

As you see in the error message, the Kubernetes job has failed. this means somehow the simulation containers did not start or there was an error during their execution.

• How long did it take to start the k8s job, and failing it? did they actually start?
• You need to look into Kubernetes/docker while running the tests, see if any container is created, and check the logs of those containers for issues they face.
• To be sure, you are using Docker Desktop's Kubernetes features, right? because this probably will not work with any other setup.

Can you please advice me, why this .ulog file is not generated?

Since the simulation containers are not working properly, you do not have the flight logs (.ulg") in your folders. these are copied by the CONTAINERS to the location after their execution, and not your local code.

[skhatiri]

Also, I have a slight confusion, if I still need local PX4-Autopilot and catkin_ws folders. As in the .env file, two variable is defined like:

I understand the confusion. No you don't need those folders on your local machine. but because of current limitations, you need to have those keys in your .env files (they don't have a default, and you will get an error if you remove them completely). you can just leave an empty string there. Anyway, They are never used if you use docker or k8s agents. I am refactoring the code and will fix this issue.

[skhatiri]

After a little bit of debugging, I think it might be the case that Kubernetes implementation is not there in the main branch, I have tried to run the k8 code by reverting back commented out codes and updating them like the following:

Now, new issues are coming up like the following error:

Can you please recheck if k8 code is pushed in master branch or some part of it is still not implemented? @skhatiri

The code is there already, those commented codes are not needed for test execution, and i am refactoring and removing them. You can safely revert back to the original version (commented code)