Bug 1581785
| Summary: | EC2 custom instance type is not displayed as an option in provisioning | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Matouš Mojžíš <mmojzis> |
| Component: | Documentation | Assignee: | Red Hat CloudForms Documentation <cloudforms-docs> |
| Status: | CLOSED WONTFIX | QA Contact: | Matouš Mojžíš <mmojzis> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.8.0 | CC: | cpelland, dajohnso, dmetzger, hhudgeon, jhardy, mmojzis, mshriver, obarenbo |
| Target Milestone: | GA | ||
| Target Release: | 5.8.5 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | ui:ec2:provisioning | ||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-12-19 15:46:50 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | Bug | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | Documentation | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Matouš Mojžíš
2018-05-23 15:43:46 UTC
Discussed with Bronagh, sending to her to review/assign. The instance type is also missing in MIQ provision dialogue (when provision from template/image). I'll take look into that as well Ok, I think it's much more a setup related stuff, which blocked myself as well. I also struggled to understand your description properly. My bad.
You're basically trying to say that when you have a custom flavor defined and you want to provision an instance you would expect this flavor to be listed as "Instance type" under the "Properties" tab. Is that correct?
So the exact steps to reproduce the "missing flavor" would be:
1. Have a EC2 provider
2. Define custom flavor in "Configuration -> Advanced"
3. Refresh the provider so the flavor gets propagated
4. Go to "EC2 Provider summary -> Instances" OR "Compute -> Cloud -> Instances"
5. Provision via "Lifecycle -> Provision Instances"
6. Select EC2 image and "Continue"
7. Under tab "Properties" in the "Instance type" dropdown should be the flavor available
Is that correct?
I found that Provision dialogue limits which flavors can be displayed based on the template (image) properties. So you need to have selected an image with fits the flavor capabilities. Like HVM images has to be deployed as flavor which supports HVM only etc. The same goes for architecture.
Please try a flavor definition like this:
```
...
:additional_instance_types:
:custom_type:
:virtualization_type:
- :hvm
:architecture:
- :i386
- :x86_64
:vcpu: 1
:ebs_only: false
:instance_store_size: 0
:instance_store_volumes: 0
:memory: 536870912
:description: Some description
:name: custom_type
...
```
And then try to provision an image. Does it show the flavor to you? It works for me.
I think you were missing the architecture definition or at least I was, when I tried for the first time.
Tomas, you are right. After adding architecture types custom instance types were displayed in provisioning. I think this needs documentation as both of us weren't able to make it work at the first time? Thanks Sure, that sounds good to me. It's not the most straightforward thing around and it would be nice to have this documented. To sum it up: If you want to add an Custom flavor for EC2, follow the workflow mentioned in [Comment 4]. You can't forget to specify the virtualization type and architecture since without these values it won't allow you to provision an instance with this flavor. Forwarding this bug to Documentation team. |