Qingyang Nong

Hi @zanewgray, I can not reproduce the issue, are you reproduce it always? If so, could you help check `spec.template.spec.volumes.persistentVolumeClaim.claimName` of VM whether can be found in PVC

The issue can be reproduced by the following steps: 1. Deploy a rancher server by docker run 2. Access the rancher UI 3. Remove the rancher server and deploy the...

Requires backend help. The harvester-public namespace should not be edited on the namespace page. Thus UI can filter the namespace select options by `links.update`. Feel free to assign me again...

Hi, @noahgildersleeve. Sorry I cannot reproduce this issue. Could you use the Rancher v2.6.9-rc1 and Harvester v1.1.0-rc1 test again?

Also the same as https://github.com/harvester/harvester/issues/2485#issuecomment-1252333909

@noahgildersleeve Thanks for your testing. Sorry for the reproduced steps are not detailed. And there have a backend issue [2788](https://github.com/harvester/harvester/issues/2788) that makes harvester-public very confused. Here are my reproduce steps:...

> I created the namespace and then when I tried to create the template I got this error Yep, as the issue [2788](https://github.com/harvester/harvester/issues/2788), The harvester-public can select but cannot create...

Close in favor same as https://github.com/harvester/harvester/issues/3362 and https://github.com/harvester/harvester/issues/3413

[预览](https://n313893254.github.io/demo/resumer/dist/index.html) [代码](https://github.com/n313893254/demo/tree/master/resumer)

Also found a minor issue in the latest UI index（1/19）: The tooltip of the "Add Receiver" button can be clicked and then throw an error with the page crash. ...