Siva Kanakala

https://github.com/rancher/shell/pull/206

[fix(workload/Upgrading): fix DaemonSet/StatefulSet update strategy failed issue #9875 ](https://github.com/rancher/dashboard/pull/9875)

@pankajsqe seems you're checking something wrong... I could see the configmaps are correctly landed in the dashboard namespace... ``` root@master-0:~# kubectl get cm -A | egrep -i "nodes-darwin|grafana-overview" cattle-dashboards rancher-monitoring-grafana-overview...

Yes, this issue is reproducible with Rancher version v2.7.5-rc4. The following secret was created after the cluster was created: ``` newrancherserver:~ # kubectl get clusters -A NAMESPACE NAME READY KUBECONFIG...

I can't seem to reproduce the problem with rancher 2.7.6, local cluster: v1.25.13+k3s1, ds cluster: v1.24.17-rancher1-1 ``` { "mode": "managed", "type": "rancher2_cluster", "name": "cluster_az", "provider": "provider[\"registry.terraform.io/rancher/rancher2\"]", "instances": [ { "schema_version":...

I've attempted to reproduce the issue using Rancher version 2.6.13, but it remains non-reproducible.... ds cluster: tried with both rke2 and k3s ``` { "mode": "managed", "type": "rancher2_cluster", "name": "cluster_az",...

internal ref: https://jira.suse.com/browse/SURE-5659

It would appear that it's a UI issue...

@prachidamle @MKlimuszka @alexandreLamarre The fix was incorrectly tested [here](https://github.com/rancher/rancher/issues/43502#issuecomment-1991790047) To clarify, with the [fix](https://github.com/rancher/charts/pull/3466) applied, the configmap is correctly created in the appropriate namespace(you can see my test results), so...

It appears to be functioning as intended, but the process is exceptionally swift, making it challenging to capture the information effectively. I think the job is continually being deleted and...