Bug 1720643
| Summary: | Discrepancy in default memory size for virtual machine while provisioning vm from Satellite 6 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | vkaushik | ||||
| Component: | Compute Resources - libvirt | Assignee: | Ondřej Ezr <oezr> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Lukáš Hellebrandt <lhellebr> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.6.0 | CC: | chrobert, mhulan | ||||
| Target Milestone: | 6.6.0 | Keywords: | Regression, Triaged | ||||
| Target Release: | Unused | ||||||
| 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: | 2019-10-22 19:49:21 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: |
|
||||||
|
Description
vkaushik
2019-06-14 12:36:55 UTC
Created attachment 1580666 [details]
Satellite 6- WebUI screenshot
Created redmine issue https://projects.theforeman.org/issues/27391 from this bug From description and the image assuming this is a libvirt compute resource. I was able to reproduce it on libvirt, but it is not happening for vmware, as it has memory in MB. As vkaushik is not active, can't wait for his info, proceeding with fix for libvirt. *** Bug 1742547 has been marked as a duplicate of this bug. *** Verified with Sat 6.6 snap 20. Filled "3 GB", "3" and left default "2 GB", all led to correct size of the VM's memory and it got correctly shown in the host's VM tab. Also, information icon works, saying "When specifying custom value, add 'MB' or 'GB' at the end. Field is not case sensitive and MB is default if unspecified." which is correct. 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/RHSA-2019:3172 |