Bug 1741152
| Summary: | [downstream clone - 4.3.6] [RFE] - Creating an NFS storage domain the engine should let the user specify exact NFS version v4.0 and not just v4 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | RHV bug bot <rhv-bugzilla-bot> |
| Component: | ovirt-engine | Assignee: | Fedor Gavrilov <fgavrilo> |
| Status: | CLOSED ERRATA | QA Contact: | Daniel <dmaaravi> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.3.0 | CC: | aefrat, bugs, fgavrilo, Rhev-m-bugs, sbonazzo, tnisan |
| Target Milestone: | ovirt-4.3.6 | Keywords: | FutureFeature, ZStream |
| Target Release: | 4.3.6 | Flags: | aefrat:
testing_plan_complete+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine-4.3.6.3 | Doc Type: | Enhancement |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1690026 | Environment: | |
| Last Closed: | 2019-10-10 15:36:58 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1690026 | ||
| Bug Blocks: | |||
|
Description
RHV bug bot
2019-08-14 11:30:25 UTC
Is this going to be fixed in 4.3.5? (Originally by Sandro Bonazzola) Please take under consideration that although this bug was opened on UI/webadmin. This should be tested and verified for both UI and restAPI as fixes are in both UI and in RESTAPI. I just verified this bug on ovirt-engine-4.3.6.2-0.1.el7.noarch The fix is included in 4.3.6-2 according to https://gerrit.ovirt.org/#/c/101864/ The NFS storage was created in V4.0 as expected. 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, 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/RHEA-2019:3010 |