[BUG] Unable to restore from UI incase user first click on `An S3-compatible object store`

[omkarkhatavkar]

Rancher Server Setup

• Rancher version: 2.11.3
• Installation option (Docker install/Helm Chart): Helm Chart
• RKE2 - v1.32.5+rke2r1

Information about the Cluster

• Kubernetes version: 1.32.5
• Cluster Type (Local/Downstream): Local

User Information

• What is the role of the user logged in? Admin

Describe the bug
Unable to restore from UI incase user first click on An S3-compatible object store

To Reproduce

1. Install the rancher manager 2.11.3
2. Install the backup and restore chart
3. Take the backup
4. Now try to restore the backup created in step 3, but while doing through UI, just click on An S3-compatible object store and try restore mentioned in below video recording

Result
restore is failed with an error

Expected Result
restore should be successful

Recording

Restore_Error.mov

Additional context
this is only happens using UI and when user click on An S3-compatible object store radio button

[torchiaf]

Thanks @omkarkhatavkar . Could you please share the list of API calls from browser's Network tab after you click Create button?
It looks like the UI is displaying an error from an S3 creation request (Bucket name is empty), so we suspect that, even you select the Default Storage Target, the UI is handling the backup as it was S3.

[skanakal]

@torchiaf When toggling between the radio buttons, especially from S3 back to Default, the S3 config (this.s3 and spec.storageLocation.s3) is still retained, even though it's no longer needed. This causes the empty bucketName value to still set , resultin error....

The logic reapplies here even for the useDefault: meaning still injects the s3 object
https://github.com/rancher/dashboard/blob/master/shell/edit/resources.cattle.io.restore.vue#L172-L174

else {
  delete this.value.spec.backupFilename;
  this.value.spec.storageLocation = { s3: this.s3 };
}

Yaml:

apiVersion: resources.cattle.io/v1
kind: Restore
metadata:
  name: #string
  annotations:
    {}
    #  key: string
  generateName: restore-
  labels:
    {}
    #  key: string
spec:
  deleteTimeoutSeconds: 10
  prune: true
  storageLocation:
    s3:

[omkarkhatavkar]

@torchiaf I dont see any error network tab, this is mostly JS issue I believe mentioned earlier comment by @skanakal.