The template gets disabled, because the image in the operating system takes precedence over the template selection. Setting as low, as it shouldn't influence the core behaviour.

Created redmine issue http://projects.theforeman.org/issues/20938 from this bug

3 clients I worked at just this year (GDIT, GA, and BKFS) all VMware and all image provisioners. They LOVED the hybrid method of using Sat6 to create images but wanted Sat6 image provisioning and I could not shot it to them.

Can we increate the priority on this?  If this affects AWS and VMware like it does RHV this is a MASSIVE issue!

Priority bumped. Marek, thoughts on this?

Steven, I don't understand how this is related to vmware image based provisioning? Honestly I don't understand what exactly is the issue for ovirt but I suppose Ivan does. So could you please describe your use case, what exactly does not work and how you expect it to change? Thanks you.

This is a Sat6 issue from what I am told so that would suggest it not only affects RHV but also VMware so I can not point out provisioning via images to VMware clients or RHV clients.  While it does not seem to be  much of an issue for RHV clients it is a BIG deal to many of the VMware shops I visit who love to use images for provisioning.

If someone who have VMware/VSphere could test and if then find out this does NOT affect VMware like it does in RHV then that helps and I can let VMware shops I go to know about how Satellite can do the image provisioning they do now and more.

If I could figure out how to set up AWS I could test with that but as yet I have not gotten into AWS but so far only saw one client who has Sat6 and uses AWS to date.

Ultimately I need to have image based provisioning for any compute resource to work with > 1 image per provider.  It breaks right now if I add > 1 image per provider.  Unfortunately RHV is all I have so I can't test with any other provider.

The large majority of clients I work with are VMware shops and over half use image based provisioning in/with VMware and have multiple images based on the type of system then need to build.

I am going to be building a capsule in AWS so I will see if this affects the ability to use more than 1 image in AWS in the next week or two.

Has anyone tried using >1 image in AWS via a capsule in AWS before?

Steven: could you describe exactly your usage and the issue you're seeing and check if that's in sync of description of this BZ?

Ivan/Marek,

I'm running 6.2.11 right now so I first should update to 6.2.12 then verify and will post exact ereproduce procedure and I want to re-verify as I am now on RHV-M 4.1 (using older v3 api which I understand is still the only "fix" which itself is not good.

As far as use case I only have RHV and soon AWS to test with but MANY clients use image based provisioning and are Sat6 shops.  They should be able to use the image provisioning functionality to provision VMs using Sat6 compute resources with an array of many different images.  The issues with trying to do that are:

1. You can not specify a default compute resource and compute profile so that must be done manually at provision time.

2. There could be >1 image that has the exact same OS (RH 7.4) and each of the 2+ images are for different purposes and you need to be able to pick the one you need irrespective of the OS.  For exampe 1 STIG'd RHEL 7.4 vs a PCI compliant RHEL 7.4 Vs a default security RHEL 7.4.

If you think this works better in Sat6.3 snap 19 or other 6.3 let me know and I can get my Sat6.2.12 to build a configured Sat6.3.x snap y system to test with once I pull the repos for that Sat6.3 into my Sat6.2.12 to build with.

1. afaik you can specify thye compute profile already in 6.2 on hostgroup basis. The compute resource is being added in http://projects.theforeman.org/issues/5790/ and will be available in 6.4

2. the compute profile allows selecting the image that should be used for image-based provisioning. What we don't allow is setting choosing image provisioning by default in compute profile

Anyway, I think that's something else than this BZ describes and therefore I suggest separate BZ describing more precisely what the missing functionality is. Otherwise, we risk misunderstanding of the request in the future.

I have FULLY tested this in AWS and I can easily change the image back and fourth including after changing the compute profile.

So this is NOT an issue and works AS EXPECTED in AWS.

I select profilea then if I want before submitting the new host form I can change the image to any one I want.  I can also after doing that change the profile to profileB and again change the image if I want.  NOTHING gets greyed out or does not allow me to change anything.

This is how I  expect it to with with ANY compute resource.

I am currently running Sat6.2.13 with an 6.2.13 capsule in AWS to test this with.

The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.

Wrond closure reason.