Bug 1055033
Summary: | [RFE][horizon]: Preset the "Devize size" field in the "Launch Instance" form with the min_disk properties | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | RHOS Integration <rhos-integ> |
Component: | python-django-horizon | Assignee: | RHOS Maint <rhos-maint> |
Status: | CLOSED ERRATA | QA Contact: | Ami Jeain <ajeain> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | aberezin, aortega, eglynn, fpercoco, iovadia, jpichon, jruzicka, markmc, mrunge, yeylon |
Target Milestone: | Upstream M3 | Keywords: | FutureFeature |
Target Release: | 5.0 (RHEL 7) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | https://blueprints.launchpad.net/horizon/+spec/prefill-create-a-new-volume-device-size-min-requirements | ||
Whiteboard: | upstream_milestone_icehouse-3 upstream_status_implemented upstream_definition_approved | ||
Fixed In Version: | python-django-horizon-2014.1-5.el7ost | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-07-08 15:41:16 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
RHOS Integration
2014-01-18 05:04:58 UTC
There is a difference between RFE and launchpad blueprint. In my point of view the RFE is the accurate, but it behaves lake the lauchpad. Ido, in theory, there is no difference between an RFE and a blueprint. Or the rfe should be covered by a blueprint. But: we're tracking progress here with TWO systems, upstream deosn't care about Red Hat bugzilla. For Upstream, it's important what's covered by a blueprint in launchpad (and later in storyboard). I believe, there is a bug with the integration or sync job: the bz ticket is not changed, if the text of a blueprint was edited. 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. http://rhn.redhat.com/errata/RHEA-2014-0855.html |