Hide Forgot
*** Bug 1357085 has been marked as a duplicate of this bug. ***
Jeff said: It's the memory size in the flavors list. There off by 1024. The actual Azure VM size is correct. The VM details show the right values. The bug you reference if from 5.6 and was fixed and verified in 5.6.0.5. This is probably the clone of that for 5.5. As of 5.5.5.2, it still shows this under cloud\flavors. I'm afraid it's still open. Basic_A0 AzureDJ 1 1 768 Bytes Basic_A1 AzureDJ 1 1 1.8 KB Basic_A2 AzureDJ 2 2 3.5 KB Basic_A3 AzureDJ 4 4 7 KB Basic_A4 AzureDJ 8 8 14 KB Standard_A0 AzureDJ 1 1 768 Bytes Standard_A1 AzureDJ 1 1 1.8 KB Standard_A10 AzureDJ 8 8 56 KB Standard_A11 AzureDJ 16 16 112 KB Standard_A2 AzureDJ 2 2 3.5 KB Standard_A3 AzureDJ 4 4 7 KB Standard_A4 AzureDJ 8 8 14 KB Standard_A5 AzureDJ 2 2 14 KB Standard_A6 AzureDJ 4 4 28 KB Standard_A7 AzureDJ 8 8 56 KB Standard_A8 AzureDJ 8 8 56 KB Standard_A9 AzureDJ 16 16 112 KB Standard_D1 AzureDJ 1 1 3.5 KB Standard_D11 AzureDJ 2 2 14 KB Standard_D11_v2 AzureDJ 2 2 14 KB
Hi Jeff. I would like to give you a heads up; I was having trouble running a bundle update on my local 5.5.z branch, this means I could not test this fix myself. Thanks Bronagh
New commit detected on cfme/5.5.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=b35b0da84b71c283dcd3187d6f6bd557f31746d9 commit b35b0da84b71c283dcd3187d6f6bd557f31746d9 Author: Bronagh Sorota <bsorota@redhat.com> AuthorDate: Mon Apr 25 13:08:00 2016 -0400 Commit: Bronagh Sorota <bsorota@redhat.com> CommitDate: Tue Jul 19 09:28:09 2016 -0400 Flavor memory size needs to be stored in bytes to be displayed in the correct unit in the UI https://bugzilla.redhat.com/show_bug.cgi?id=1357086 app/models/manageiq/providers/azure/cloud_manager/refresh_parser.rb | 4 ++-- spec/models/manageiq/providers/azure/cloud_manager/refresher_spec.rb | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-)
Looks good on 5553, but since that build is DOA, I'll wait until 5554. Otherwise, it's going to be verified. Nice work.
This is fixed and verified using 5.5.5.4
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://rhn.redhat.com/errata/RHBA-2016-1488.html
Added test case to polarion. RHCF3-11609