[BUG] Cluster Member cannot see clusternetworks

[futuretea]

Describe the bug

To Reproduce
Steps to reproduce the behavior:

1. Imported Harvester into Rancher under Virtualization Management.
2. Created a new standard user into Rancher.
3. Under Virtualization Management, edit the Harvester configuration and add the new users as Cluster Members.
   
   
4. Using the new member users, log into the Rancher platform and open the Harvester management page.
5. Under Networks >> VM Networks >> Create, there is a field called ¨Cluster Network¨. When the user opens the dropdown, there is no network available, and the message ¨Sorry, no matching options¨
   

Expected behavior

Expect to see and select available cluster networks.

Support bundle

Environment

• Harvester ISO version: v1.1
• Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Additional context
Add any other context about the problem here.

[futuretea]

Workaround: apply the patched ClusterRole harvester-authenticated after host reboot or harvester-system/harvester pod restart

kubectl apply -f ./harvester-authenticated.yaml

The content of harvester-authenticated.yaml

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: harvester-authenticated
rules:
- apiGroups:
  - harvesterhci.io
  resources:
  - settings
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - network.harvesterhci.io
  resources:
  - clusternetworks
  verbs:
  - get
  - list
  - watch
- apiGroups:
  - ""
  resourceNames:
  - harvester-public
  resources:
  - namespaces
  verbs:
  - get
  - watch

and change verbs of network-attachment-definitions to "*" by

kubectl edit clusterRole harvesterhci.io:edit

[harvesterhci-io-github-bot]

Pre Ready-For-Testing Checklist

* [ ] If labeled: require/HEP Has the Harvester Enhancement Proposal PR submitted?
The HEP PR is at:

• Where is the reproduce steps/test steps documented?
  The reproduce steps/test steps are at:
  [BUG] Cluster Member cannot see clusternetworks #3300 (comment)

• Is there a workaround for the issue? If so, where is it documented?
  The workaround is at:
  [BUG] Cluster Member cannot see clusternetworks #3300 (comment)

* [ ] Have the backend code been merged (harvester, harvester-installer, etc) (including backport-needed/*)?
The PR is at:

• Does the PR include the explanation for the fix or the feature?
  Fix cluster member create VM network #3303

* [ ] Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart?
The PR for the YAML change is at:
The PR for the chart change is at:

* [ ] If labeled: area/ui Has the UI issue filed or ready to be merged?
The UI issue/PR is at:

* [ ] If labeled: require/doc, require/knowledge-base Has the necessary document PR submitted or merged?
The documentation/KB PR is at:

* [ ] If NOT labeled: not-require/test-plan Has the e2e test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue?
- The automation skeleton PR is at:
- The automation test case PR is at:

* [ ] If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility?
The compatibility issue is filed at:

[harvesterhci-io-github-bot]

added backport-needed/1.1.2 issue: #3334.

[TachunLin]

Verified fixed on master-14bbee2c-head (1/13) with Rancher v2.7.0. Close this issue.

Result

Create a normal user with cluster member role to access Harvester from virtualization management.
The user can see and select the clusternetworks item

vokoscreenNG-2023-01-18_19-52-56.mp4

Test Information

• Test Environment: 1 nodes harvester on local kvm machine
• Harvester version: master-14bbee2c-head (1/13)
• Rancher version: v2.7.0

Verify Steps

Steps to reproduce the behavior:

1. Imported Harvester into Rancher under Virtualization Management.
2. Created a new standard user into Rancher.
3. Under Virtualization Management, edit the Harvester configuration and add the new users as Cluster Members.
4. Using the new member users, log into the Rancher platform and open the Harvester management page.
5. Under Networks >> VM Networks >> Create, there is a field called ¨Cluster Network¨. When the user opens the dropdown, there is no network available, and the message ¨Sorry, no matching options¨