make aether-amp-install failed

[platyman]

Hello, I followed the tutorial for starting aether onramp and running the command

make aether-amp-install

does not work and is blocked at

TASK [roc: deploy aether-roc-umbrella from aether/aether-roc-umbrella]

I tried without and with the execution of the ‘make aether-5gc-uninstall’ command before and both executions led to the same result. The error I get is the following:

I'm using a virtual machine on proxmox with the same configuration as given in the tutorial

[nobody8v]

I'm having the same problem here, with the same deployment on Proxmox. I would appreciate any help with this please.

[mbilal92]

Could you uninstall everything, including the K8s cluster, and reinstall it?

[Fernandoapg00]

hi, i have the same problem? any solution?

[llpeterson]

Can you share the output. We've seen the install succeed, but there seems to be a timing bug in the Core (causing the simulator to report no successful UEs).

[Fernandoapg00]

Look, this is the error I have

and after that i have this error

[Fernandoapg00]

any solution?

[llpeterson]

I have no concrete suggestions. The sporadic failures of AMP we had been seeing was different (and is now resolved). You might look at the Jenkins job that validates AMP... you wouldn't necessarily mimic it exactly -- it runs on AWS -- but it does offer a known-working script. See https://github.com/opennetworkinglab/aether-jenkins/blob/master/quickstart_amp.groovy

[roomem]

Same problem here.
@Fernandoapg00 did you manage to find any kind of solution to the "aether-roc-umbrella deploy" task execution error?

[Fernandoapg00]

No recuerdo muy bien pero creo que actualizando kubernetes. Si no prueba añadir mas tiempo de espera a la hora de desplegar este task. y si eso tampoco funciona revisa los deployments que genera amp y reinicia los que no lleguen a desplegarse

[roomem]

For anyone experiencing that issue regarding "make roc-load", I solved it checking the internal pod logs, digging in it the was a service (atomix-sidecar-controller) which the ROC was relaying upon that was not in ready state.
It turned out there was a missing TLS certificate that was causing Connection Refused by the atomix pod when makefile roc load was calling it.
Long story short, maybe checking your TLS certificates could help you solve the issue 🫡