Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Comment 4Lukáš Hellebrandt
2018-09-21 14:58:57 UTC
Ori, were you able to reproduce this? I've hit the same issue as you in your comment from 20170503T15:43:45 . The template always has Thin Provisioning, even if the VM it was created from was Preallocated. I am using RHEV 3.6. That means I am not even able to do the given scenario in RHEV itself, let alone through Satellite.
I've updated the subject, as it better describes the reproducing steps, as well as the redmine issue it's connected to. Another reason is we don't have a compute resource available where we could successfully set the allocation policy of the disk in template to "Preallocated". It's always thin in setups available to us (perhaps related to https://access.redhat.com/solutions/3369061)
However, as the step 4. in the reproducer describes, it's still expected to check the 'preallocated' policy when creating the host, so it should not matter what type of the allocation policy the template actually has, in connection to this BZ or the cases attached to it.
Comment 7Lukáš Hellebrandt
2018-09-25 14:32:24 UTC
Verified with Sat 6.4 snap 22.
Used RHEV 4 because I wasn't able to use RHEV 3.6 due to different bug and RHEV 3 ELS ends in 5 days.
This BZ has been changed to only require allocation policy to propagate from Satellite to RHEV.
1) Have a RHEV, add it as a CR to Sat
2) Have a VM in RHEV, add it as Image to Sat
3) Host -> Create
4) OS -> Image Based, select the image
5) VM -> check Preallocated
6) Fill the rest, submit
7) Check in RHEV that the newly created VM has preallocated disk
Comment 8Lukáš Hellebrandt
2018-09-25 14:59:22 UTC
In the end and after some workarounds, I was also able to verify this on RHEV 3.6.
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-2018:2927