Package variant related query

[SamarSidharth]

Migrating the thread kptdev/kpt#4121 to nephio.

Is it compulsory to for the upstream and downstream repo to be registered in same namespace as package variant.

Follow up question is it a good practice to register a single repo multiple times in different namespace (eg a common upstream repo that contains blueprints with multiple downstream repos)

[SamarSidharth]

Hi @johnbelamaric

Thanks for the clarifications. I noticed an issue when we have same repo registered in multiple namespaces, so I am just documenting it here for your review. Let me know if it is ok to move this to nephio issues.

Issue:

When I try to create a PV using these repos in free5gc namespace I get the below error

      - LastTransitionTime: "2024-02-06T13:55:54Z"
        message: 'Internal error occurred: package revision workspaceNames must be
          unique; package revision with name free5gc-india in repo nif-rom with workspaceName
          packagevariant-1 already exists'
        status: Error

upon investigating it further I see that package is getting created in free5gc namespace in draft state even when I get the above message but its strange that when a do a rpkg list in all namespaces it shows that it got created in a different namespace nrf (repo is registered in this ns) but when I list the individual packages in each namespace it shows it in the correct namespace free5gc.

root@jagrati-rom-newsetup:~/demo2-setup# kpt alpha rpkg get -A
NAMESPACE   NAME                                                          PACKAGE             WORKSPACENAME      REVISION   LATEST   LIFECYCLE   REPOSITORY
nrf         nif-rom-432848f811c87438e477a56fcd897439c3224749              free5gc-india          packagevariant-1              false    Draft       nif-rom
free5gc     package-blueprints-54f9e349a4c87fac4fe39003f7b11958dbb171e8   nif-helm-template   v1                 main       false    Published   package-bluep
free5gc     package-blueprints-0c89fa90b470e8c137b054a58b2472337413c5de   nif-helm-template   v1                 v1         true     Published   package-bluep
nrf         downstream-nif-10f6bf353b7e8e70d1b05ff1e1c3e9077745a66f       free5gc             packagevariant-1              false    Draft       downstream-nif
nrf         downstream-nif-0781df4df416a9eff22e07b4b7198e622f35d18d       nrf-india           packagevariant-1   main       false    Published   downstream-nif

root@jagrati-rom-newsetup:~/demo2-setup# kubectl get packagerevision -n nrf
NAME                                                      PACKAGE     WORKSPACENAME      REVISION   LATEST   LIFECYCLE   REPOSITORY
downstream-nif-10f6bf353b7e8e70d1b05ff1e1c3e9077745a66f   free5gc     packagevariant-1              false    Draft       downstream-nif
downstream-nif-0781df4df416a9eff22e07b4b7198e622f35d18d   nrf-india   packagevariant-1   main       false    Published   downstream-nif

root@jagrati-rom-newsetup:~/demo2-setup# kubectl get packagerevision -n free5gc
NAME                                                          PACKAGE             WORKSPACENAME      REVISION   LATEST   LIFECYCLE   REPOSITORY
nif-rom-432848f811c87438e477a56fcd897439c3224749              free5gc-india          packagevariant-1              false    Draft       nif-rom
package-blueprints-54f9e349a4c87fac4fe39003f7b11958dbb171e8   nif-helm-template   v1                 main       false    Published   package-blueprints
package-blueprints-0c89fa90b470e8c137b054a58b2472337413c5de   nif-helm-template   v1                 v1         true     Published   package-blueprints


Deletion log:
root@jagrati-rom-newsetup:~/demo2-setup# kubectl delete packagerevision nif-rom-432848f811c87438e477a56fcd897439c3224749 -n free5gc
packagerevision.porch.kpt.dev "nif-rom-432848f811c87438e477a56fcd897439c3224749" deleted

[SamarSidharth]

A related discussion thread #491