New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UPF Orchestration : IPAM Injection Failure in the draft stage #127
Comments
is it possible to do a log on the ipam k logs -n Nephio-system ipam-... -f. Would like to see the logs to understand why it is not allocating the prefixes. One reason I saw was when the package was approved there was no way to update the package as it was already approved and an update could not be handled. Also this should be visible in the condition of the ipam allocation. |
Sure, will share the logs with you, will have to recreate the scenario.. ","labels":{"nephio.org/gateway":"true"}}} |
ok I know this issue and this is indeed a shortcut I took to get the poc going. Since you redeploy the new prefix it uses the pool as an aggregate iso the real aggregate and this is why this fails. Let me see how I can fix this. |
I had left it overnight, and when i saw this evening, the conditions had resolved didnt have to delete the and reapply the n3-net-prefix1 , not sure that the controller just takes some time to inject the prefixes, also see IpPrefix/n3 in the false state.. |
I was looking at this in more detail this morning and create/delete sample-n3-net-prefix1 is not a good idea, since this allows the pool to take its place since it is dynamically allocated and takes whatever prefix that is available. so in nephio/config/templates/ipam.j2 change to this. apiVersion: ipam.nephio.org/v1alpha1 Could you try this? |
I see even just deleting and re-applying the new IPprefix works in the draft stage, but can try the above before i even clone the package to the edge deployment and see if that resolves the condition correctly |
Now having done this few times, and after realizing that the delay in resolving the IP Injection condition is random, i'm assuming it is some problem in how the timers are expiring in the code and reconciling the state. Otherwise, if one has that in mind, the conditions are being resolved. But the problem of Gateway IP missing still exists. |
The gateway I did not analyse in detail yet but this one should be fixed with the change I proposed. Can you confirm that? |
You mean the "Split IP" to handle the ip injection conditions ?, i see this is OK now.. |
When i recreate a new resource type “fivegcoretopology-sample”, this will invoke all the controllers. At this stage, most likely, the IPAM injection preconditions flag are raised on PORCH, so then the patch is to delete and reapply “sample-n3-net-prefix1", this fixes the preconditions.
The text was updated successfully, but these errors were encountered: