Package upgrade to the new revision fails

[deepakal]

The remote package upgrade command fails to update to the newer version of the package. This behavior occurs consistently whether using porchctl or packageVariant

Steps to reproduce the issue:

• Created two blueprint package v1 and v2

NAME	PACKAGE	WORKSPACENAME	REVISION	LATEST	LIFECYCLE	REPOSITORY
blueprint-a0d0db2db66901a6ff26f44ff8c65f06280fcf7e	cert-manager-basic	v1	main	false	Published	blueprint
blueprint-f80ce9bdd3e52daa8efbf41e6212580c9b35aee1	cert-manager-basic	v0	v1	false	Published	blueprint
blueprint-235dd102397166675b5ef6e6267490174a9d44d8	cert-manager-basic	v1	v2	true	Published	blueprint

• Cloned v1 package from blueprint package to deployment package

1. ./porchctl rpkg clone blueprint-f80ce9bdd3e52daa8efbf41e6212580c9b35aee1 cert-manager-basic --repository deployments --workspace=v0 -n NAMESPACE --kubeconfig /home/.kube/management.nc.config
2. Which created the new draft package in deployment repo

NAME	PACKAGE	WORKSPACENAME	REVISION	LATEST	LIFECYCLE	REPOSITORY
deployments-b89549e0374f61620bae75862adb8642e4dfdeb4	cert-manager-basic	v0		false	Draft	deployments

However, when updating the package in Draft to a later version, the following exception occurs

• ./porchctl rpkg update deployments-b89549e0374f61620bae75862adb8642e4dfdeb4 --revision=v2 -n NAMESPACE --kubeconfig /home/.kube/management.nc.config
  Error: Internal error occurred: error updating the package to revision blueprint-235dd102397166675b5ef6e6267490174a9d44d8

This issue occurs not only with the CLI but also when using PackageVariant. For example, creating a Draft with version v1 and then updating the revision to v2 in PackageVariant results in the same exception. Additionally, the error message in the pod logs is not much helpful

component Version:

component	version
porchctl	3.0.0
porch-server	v3.0.0

[nagygergo]

Hey, could you look up porch-server logs for the same?