Bug 1119870
Summary: | Launching an instance from image, insufficient flavors not filtered | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Tzach Shefi <tshefi> |
Component: | python-django-horizon | Assignee: | Matthias Runge <mrunge> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Ami Jeain <ajeain> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.0 (RHEL 6) | CC: | aortega, jpichon, mrunge, tshefi, yeylon |
Target Milestone: | --- | ||
Target Release: | 5.0 (RHEL 7) | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-08-22 14:54:42 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: |
Description
Tzach Shefi
2014-07-15 17:28:12 UTC
I wonder, if this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=906302 Could you please give more background information here? I can't reproduce this on master, I think if this was an issue in Icehouse (I haven't tried there) it will be fixed in J / 6.0. Yes it's probably a duplicate. On bz906302 step 2 "After the image is uploaded, try to Launch it", unsure about the work flow used. If reporter used launch button on image itself yes it's a duplicate, I'm guessing that's the case. However if he moved to instance's page and started an instance from there selecting an image this might be a none duplicate. I tried to reproduce following the steps in comment 0, setting the min disk 2GB and the "Launch" button by the image preselected m1.small as expected, greying out the other flavours that are too small (m1.tiny, which is selected by default for the other images). I'm using python-django-horizon-2014.1-6.el7ost.noarch and made sure to launch from the "Images" panel. The bug was also closed upstream because it cannot be reproduced on master so I'm closing for now, feel free to reopen with additional information if you're still seeing this though. Thank you. |