Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Backport v1.0] The project-owner user will see an additional alert #2350

Closed
WuJun2016 opened this issue Jun 6, 2022 · 3 comments
Closed
Assignees
Labels
area/multi-tenancy area/ui Harvester standalone UI or Rancher UI extension kind/bug Issues that are defects reported by users or that we know have reached a real release not-require/test-plan Skip to create a e2e automation test issue priority/0 Must be fixed in this release
Milestone

Comments

@WuJun2016
Copy link
Contributor

This is a backport issue for #2288.

@WuJun2016 WuJun2016 added the area/ui Harvester standalone UI or Rancher UI extension label Jun 6, 2022
@WuJun2016 WuJun2016 self-assigned this Jun 6, 2022
@WuJun2016 WuJun2016 added this to the v1.0.3 milestone Jun 6, 2022
@WuJun2016 WuJun2016 added area/multi-tenancy priority/0 Must be fixed in this release not-require/test-plan Skip to create a e2e automation test issue kind/bug Issues that are defects reported by users or that we know have reached a real release labels Jun 6, 2022
@harvesterhci-io-github-bot
Copy link

harvesterhci-io-github-bot commented Jun 10, 2022

Pre Ready-For-Testing Checklist

* [ ] Is there a workaround for the issue? If so, where is it documented?
The workaround is at:

* [ ] Does the PR include the explanation for the fix or the feature?

* [ ] 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:

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

* [ ] Which areas/issues this PR might have potential impacts on?
Area
Issues

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

* [ ] If labeled: require/doc Has the necessary document PR submitted or merged?
The documentation issue/PR is at

* [ ] If labeled: require/automation-e2e Has the end-to-end 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
The issue of automation test case implementation is at (bot will auto create one using the template)

* [ ] If labeled: require/integration-test Has the PR includes the integration test?
The integration test PR is at

* [ ] If labeled: require/manual-test-plan Has the manual test plan been documented?
The updated manual test plan 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

@TachunLin
Copy link

Move to ready for test and verify with #2394

@TachunLin
Copy link

Verified fixed on v1.0-ec0bb4be-head (6/10) with Rancher v2.6.5. Close this issue

Harvester ui-index: https://releases.rancher.com/harvester-ui/dashboard/release-harvester-v1.0/index.html
Rancher ui dashboard-index: https://releases.rancher.com/harvester-ui/dashboard/release-harvester-v1.0/dd7c9a1cbc6251cd5e0e.js
Rancher offline preferred: Remote

Result

Use rancher standard user test with project owner permission to access Harvester.
Now there is no error alert for VM created on vlan1
image

Test Information

  • Test Environment: 1 node harvester on local kvm machine
  • Harvester version: v1.0-ec0bb4be-head
  • Rancher version: v2.6.5

Verify Steps

Follow the issue description #2288 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/multi-tenancy area/ui Harvester standalone UI or Rancher UI extension kind/bug Issues that are defects reported by users or that we know have reached a real release not-require/test-plan Skip to create a e2e automation test issue priority/0 Must be fixed in this release
Projects
None yet
Development

No branches or pull requests

3 participants