USABLE and LATEST columns showing wrong values
@janiskemper is already working on this.
Since Feb 7, 2024.
Assessment
This issue has not been assessed yet.
Description
/kind bug
What steps did you take and what happened:
Create clusterstack with multiple versions, e.g.:
apiVersion: clusterstack.x-k8s.io/v1alpha1
kind: ClusterStack
metadata:
name: clusterstack
namespace: cluster
spec:
provider: openstack
name: ferrol
kubernetesVersion: "1.27"
channel: stable
autoSubscribe: false
providerRef:
apiVersion: infrastructure.clusterstack.x-k8s.io/v1alpha1
kind: OpenStackClusterStackReleaseTemplate
name: cspotemplate
versions:
- v1
- v2
- v3
- v4
Wait for clusterstackreleases to be Ready:
$ kubectl get clusterstackreleases.clusterstack.x-k8s.io -n cluster
NAME K8S VERSION READY AGE REASON MESSAGE
openstack-ferrol-1-27-v1 v1.27.5 true 113m
openstack-ferrol-1-27-v2 v1.27.5 true 113m
openstack-ferrol-1-27-v3 v1.27.8 true 113m
openstack-ferrol-1-27-v4 v1.27.8 true 113m
Get clusterstack:
$ kubectl get clusterstack clusterstack -n cluster
NAME PROVIDER CLUSTERSTACK K8S CHANNEL AUTOSUBSCRIBE USABLE LATEST AGE REASON MESSAGE
clusterstack openstack ferrol 1.27 stable false v3, v3, v3, v3 openstack-ferrol-1-27-v3 | v1.27.8 113m
$ kubectl get clusterstack clusterstack -n cluster
NAME PROVIDER CLUSTERSTACK K8S CHANNEL AUTOSUBSCRIBE USABLE LATEST AGE REASON MESSAGE
clusterstack openstack ferrol 1.27 stable false v1, v1, v1, v1 openstack-ferrol-1-27-v1 | v1.27.5 119m
I see the wrong USABLE and LATEST columns. It is also changing over time.
What did you expect to happen:
USABLE: v1, v2, v3, v4
LATEST: openstack-ferrol-1-27-v4 | v1.27.8
Environment:
- cluster-stack-operator version: v0.1.0-alpha.2
- Kubernetes version: v1.27.2
- Dominant language
- Go
- Stars
- 18
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from SovereignCloudStack/cluster-stack-operator
-
CI issues (1) Openbug Container
SovereignCloudStack/cluster-stack-operator#340 · 1 comment · 3 assignees ·
-
cso: crash .... Open
Difficulty 3/5 1-2 days Newbie friendliness 58/100
SovereignCloudStack/cluster-stack-operator#337 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 50/100
SovereignCloudStack/cluster-stack-operator#336 · 3 comments ·
-
bug
SovereignCloudStack/cluster-stack-operator#327 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
SovereignCloudStack/cluster-stack-operator#272 · 32 comments ·
All issues in SovereignCloudStack/cluster-stack-operator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug group: validation priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
codecheckers/chekhov#51 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100