Bug 1218897
Summary: | new launch instance does not work with webroot other than '/' | ||
---|---|---|---|
Product: | [Community] RDO | Reporter: | Matthias Runge <mrunge> |
Component: | openstack-horizon | Assignee: | Matthias Runge <mrunge> |
Status: | CLOSED UPSTREAM | QA Contact: | wes hayutin <whayutin> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | Kilo | CC: | apevec, mrunge |
Target Milestone: | --- | ||
Target Release: | trunk | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-09-10 07:24:09 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1218896 |
Description
Matthias Runge
2015-05-06 07:21:18 UTC
Matthias, there's WIP patch for Liberty, is it ready to backport or can you cook something for RDO Kilo GA? Alan, new launch instance is marked as "experimental" in Kilo and will eventually become more stable in liberty. Current state is: It uses hard coded paths all over. The new api is required to be accessed via /dashboard/api and not via /api (that would probably clash with keystone) Should we disable/remove "new launch instance" in RDO Kilo build then? Alan, it's disabled by default. If you know what you're doing, you can enable it, since it's upstream. I wouldn't change that. being tracked upstream, still not backported, but not enabled by default. |