Bug 1535256
Summary: | MaxBlockDiskSize is honoured only on AddDiskCommand and not on Extend | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Andrea Perotti <aperotti> |
Component: | ovirt-engine | Assignee: | Benny Zlotnik <bzlotnik> |
Status: | CLOSED ERRATA | QA Contact: | Avihai <aefrat> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.9 | CC: | amarchuk, apinnick, bzlotnik, dfodor, eedri, lsurette, lveyde, obockows, ratamir, rbalakri, Rhev-m-bugs, srevivo, tnisan, ykaul, ylavi |
Target Milestone: | ovirt-4.2.2 | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ovirt-engine-4.2.2 | Doc Type: | Bug Fix |
Doc Text: |
In the current release, MaxBlockSize is checked when extending a disk, to ensure that its size does not exceed the MaxBlockSize value.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-15 17:47:24 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andrea Perotti
2018-01-17 00:15:34 UTC
Benny, a customer encountered this bug, and the fix is a visible change. Please add some doctext explaining it. Thanks! Fix is not in latest downstream 4.2.2.2 -> Moved back to MODIFIED. Please move it back to 'ON QA' when its available in latest downstream. See gitweb link on latest downstream 4.2.2.2 commits: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=bd519ad7adc2e71603d0b2a4cfa710d608b61b70 (In reply to Avihai from comment #2) > Fix is not in latest downstream 4.2.2.2 -> Moved back to MODIFIED. > Please move it back to 'ON QA' when its available in latest downstream. > > See gitweb link on latest downstream 4.2.2.2 commits: > https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog; > h=bd519ad7adc2e71603d0b2a4cfa710d608b61b70 Sure it is, it was just pushed to the next page since it's been there for so long :-) You can verify this manually: amureini@mureinik ~/src/git/ovirt-engine [master] $ git tag --contains fbf4c769764b30ab2957f78b99ec35cfc8f955e2 ovirt-engine-4.2.2 ovirt-engine-4.2.2.1 ovirt-engine-4.2.2.2 (In reply to Allon Mureinik from comment #3) > (In reply to Avihai from comment #2) > > Fix is not in latest downstream 4.2.2.2 -> Moved back to MODIFIED. > > Please move it back to 'ON QA' when its available in latest downstream. > > > > See gitweb link on latest downstream 4.2.2.2 commits: > > https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog; > > h=bd519ad7adc2e71603d0b2a4cfa710d608b61b70 > > Sure it is, it was just pushed to the next page since it's been there for so > long :-) > > You can verify this manually: > > amureini@mureinik ~/src/git/ovirt-engine [master] $ git tag --contains > fbf4c769764b30ab2957f78b99ec35cfc8f955e2 > ovirt-engine-4.2.2 > ovirt-engine-4.2.2.1 > ovirt-engine-4.2.2.2 My bad, it was indeed in the next webgit page & pushed to ovirt-engine-4.2.2. Will check it shortly. verified on engine 4.2.2.2 INFO: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Tag 'ovirt-engine-4.2.2.4' doesn't contain patch 'https://gerrit.ovirt.org/86743'] gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.2.2.4 For more info please contact: rhv-devops (In reply to RHV Bugzilla Automation and Verification Bot from comment #6) > INFO: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: > > [Tag 'ovirt-engine-4.2.2.4' doesn't contain patch > 'https://gerrit.ovirt.org/86743'] > gitweb: > https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ > ovirt-engine-4.2.2.4 > > For more info please contact: rhv-devops It most certainly does: amureini@mureinik ~/src/git/ovirt-engine [master] $ git tag --contains fbf4c769764b30ab2957f78b99ec35cfc8f955e2 ovirt-engine-4.2.2 ovirt-engine-4.2.2.1 ovirt-engine-4.2.2.2 ovirt-engine-4.2.2.3 ovirt-engine-4.2.2.4 Thanks for reporting this, we do have known issues in the bug moving logic we're trying to resolve, this will help in debugging. Anton,Dusan - can you investigate why this but wasn't included in the build? 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-2018:1488 BZ<2>Jira Resync |