Bug 1944674
| Summary: | Project field become to "All projects" and disabled in "Review and create virtual machine" step in devconsole | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Guohua Ouyang <gouyang> | ||||||
| Component: | Console Kubevirt Plugin | Assignee: | Gilad Lekner <glekner> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Guohua Ouyang <gouyang> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 4.8 | CC: | aos-bugs, glekner, gouyang, mcarleto, yzamir | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 4.8.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2021-07-27 22:56:34 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 1771323 [details]
can't reproduce bug
can you look at attachment Guohua works for me too, maybe fixed by other issue, moving to modified Just have a look at master, the name is not changing to "All projects" on master now. What about the project is disabled? why should we disable it? It is intended, the user is referred to this from the dev console only, where he pre-selects a namespace. you can talk to UX if you think this should change (In reply to Gilad Lekner from comment #5) > It is intended, the user is referred to this from the dev console only, > where he pre-selects a namespace. I don't see a reason to disable it because the behavior just reduce flexible here. There are lots of places in wizard without 'Project' disabled, why we just disable the 'Project' in this page? > you can talk to UX if you think this should change (In reply to Gilad Lekner from comment #5) > It is intended, the user is referred to this from the dev console only, > where he pre-selects a namespace. > you can talk to UX if you think this should change Do you think is it necessary to disable the 'Project' field on this single page? Gilad hi, How hard is it to implement change in the project ? - If it's actively disabled by us, and we can just remove this restriction, we should ** as part of this bug **. - If it require implementation that will support changing projects at that stage of the form, it's a new feature we need to implement ** but not part of this bug ** ? Assign this back until we get a clear answer whether the project field should be disabled. Project field is now enabled verified on master Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days |
Created attachment 1767676 [details] Project field become to "All projects" and disabled Description of problem: The project field become to "All projects" and disabled in last step when create VM in developer perspective. Version-Release number of selected component (if applicable): master How reproducible: 100% Steps to Reproduce: 1. have a common template with boot source available 2. go to developer perspective and create a vm 3. focus on the project field Actual results: The project field become to "All projects" and disabled in the last step. Expected results: Additional info: