Gitlab tags in process of releases do not point to release branch

[shalberd]

/kind bug

@Jooho
When I click on a given releases' tag

https://github.com/opendatahub-io/kserve/tree/odh-v2.33

to get details on commits, I always get the Gitlab message

"This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository."

What is the release-branch anyways?
Regarding the tag-commit message: git tag applies to all branches that contain the commit that was tagged, ok.
But how come the tag is dangling / not belonging to a commit in any branch?

What did you expect to happen:

Tag and branch being connected. I'd expect the tag to point to a certain commit in the release-branch.
Does this have to do with Tekton and/or timing issues in the process?

Maybe holding off on the tagging until you lock-in the release is the answer. And any fixes that go in after tagging will require a new release then.

What's the InferenceService yaml:
[To help us debug please run kubectl get isvc $name -n $namespace -oyaml and paste the output]

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Istio Version:
• Knative Version:
• KServe Version:
• Kubeflow version:
• Open Data Hub version:
• Deployment Environment:[cloud (aws|gcp|ibm|azure), on prem, edge ]
• OpenShift version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[Jooho]

@shalberd I think that is expected because of the process we used. We update the image tag and create a new Tag then we rollback the tag to the previous version. Does this actually cause any practical issues, or is it just the message itself that’s concerning?