Closed skaven81 closed 11 months ago
I have a strong suspicion that the reference to harvester is just by chance...we have absolutely NO HarvesterHCI configuration or deployment or anything in this cluster or even at our company. So I have no idea why Vue would be looking up anything about Harvester at all.
Interestingly, I'm able to access other workloads in this cluster+Project and they are able to load the config panel just fine. It just seems to be this one workload that is doing this.
The fdat
workload YAML:
apiVersion: apps/v1
kind: Deployment
metadata:
annotations:
deployment.kubernetes.io/revision: "1"
field.cattle.io/publicEndpoints: '[{"addresses":["10.86.215.43"],"port":32767,"protocol":"TCP","serviceName":"fdat:fdat-nodeport","allNodes":true}]'
creationTimestamp: "2023-10-10T19:28:55Z"
generation: 16
labels:
workload.user.cattle.io/workloadselector: apps.deployment-fdat-fdat
name: fdat
namespace: fdat
resourceVersion: "812392567"
uid: 3acb8d57-90c6-44bb-8b38-c8fff1e5483d
spec:
progressDeadlineSeconds: 600
replicas: 0
revisionHistoryLimit: 10
selector:
matchLabels:
workload.user.cattle.io/workloadselector: apps.deployment-fdat-fdat
strategy:
rollingUpdate:
maxSurge: 25%
maxUnavailable: 25%
type: RollingUpdate
template:
metadata:
creationTimestamp: null
labels:
workload.user.cattle.io/workloadselector: apps.deployment-fdat-fdat
namespace: fdat
spec:
affinity: {}
containers:
- image: <redacted>
imagePullPolicy: Always
name: container-0
ports:
- containerPort: 5000
name: fdat-integ
protocol: TCP
resources: {}
securityContext:
allowPrivilegeEscalation: false
privileged: false
readOnlyRootFilesystem: false
runAsNonRoot: false
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
dnsPolicy: ClusterFirst
imagePullSecrets:
- name: docker-registry
restartPolicy: Always
schedulerName: default-scheduler
securityContext: {}
terminationGracePeriodSeconds: 30
status:
conditions:
- lastTransitionTime: "2023-10-10T19:28:55Z"
lastUpdateTime: "2023-10-10T19:29:00Z"
message: ReplicaSet "fdat-6664bdc95c" has successfully progressed.
reason: NewReplicaSetAvailable
status: "True"
type: Progressing
- lastTransitionTime: "2023-10-24T07:29:28Z"
lastUpdateTime: "2023-10-24T07:29:28Z"
message: Deployment has minimum availability.
reason: MinimumReplicasAvailable
status: "True"
type: Available
observedGeneration: 16
I have same bug on StatefulSet
.but if I use clone
or edit yaml
,it will open success.
I have update k3s(1.24->1.26) and rancher 2.7.2->2.7.8(docker)
We also had this problem. I added the missing annotations in the service of the workload and it works.
apiVersion: v1 kind: Service metadata: annotations: field.cattle.io/targetWorkloadIds: '["namespace/workloadName"]' management.cattle.io/ui-managed: 'true'
It is also mentioned here: https://forums.rancher.com/t/got-cannot-read-properties-of-undefined-reading-cloudprovider-harvesterhci-io-ipam-when-viewing-or-editing-config/41362/4
It is a bug
changer this file shell/edit/workload/mixins/workload.js
- const ui = svc?.metadata?.annotations[UI_MANAGED];
+ const ui = svc?.metadata?.annotations?.[UI_MANAGED];
It is a bug
changer this file shell/edit/workload/mixins/workload.js
- const ui = svc?.metadata?.annotations[UI_MANAGED]; + const ui = svc?.metadata?.annotations?.[UI_MANAGED];
where can find this file “shell/edit/workload/mixins/workload.js”?i find this file in rancher container, but can't find
@stdec 我是在 v2.7.9 上修改的,也许更新的版本上有改动
Rancher Server Setup
Information about the Cluster
User Information
Describe the bug Both admins and unprivileged users trying to access the configuration panel for a specific workload (which was created using the Rancher UI) get a Vue error and a long traceback in the browser console.
To Reproduce
Result Vue error appears, "Cannot read properties of undefined (reading 'cloudprovider.harvesterhci.io/ipam')"
Expected Result The config page appears.
Screenshots
Additional context