| Summary: | Creating a component Outline under a new cloud w/o any zone under it launches a blank deployable detail page | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Shveta <ssachdev> | ||||||
| Component: | aeolus-conductor | Assignee: | Matt Wagner <matt.wagner> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | wes hayutin <whayutin> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 1.0.0 | CC: | akarol, athomas, deltacloud-maint, hbrock, slinaber, ssachdev | ||||||
| Target Milestone: | beta3 | Keywords: | Triaged | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | v0.8.0-39 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-05-15 22:40:21 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
OK .. it has nothing to do with zone . Error is coming with or without zone , both cases recreated w/o zone.. not w/ zone We need to disable the "new component outline" button if there is no zone available, and also disable the "details" view for the cloud. 87bd40b "New component outline" button is removed if there is no zone. Also "details" view for the cloud is disabled. see attached screenshot. verified: rpm -qa | grep aeolus aeolus-conductor-doc-0.8.0-39.el6.noarch rubygem-aeolus-image-0.3.0-10.el6.noarch aeolus-configure-2.5.0-16.el6.noarch aeolus-conductor-0.8.0-39.el6.noarch aeolus-conductor-daemons-0.8.0-39.el6.noarch aeolus-all-0.8.0-39.el6.noarch rubygem-aeolus-cli-0.3.0-12.el6.noarch Created attachment 566737 [details]
buttons
To link things together, https://bugzilla.redhat.com/show_bug.cgi?id=801089 somewhat contradicts part of this, at least in Hugh's comment. Scott has indicated that NOT allowing access to the permissions is a bug in that it prevents someone from granting access that might used to _permit_ people to create a pool. I'll keep further discussion there... Just wanted to drop a note here that it's not a regression as much as a changing-of-our-minds. 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-2012-0583.html |
Created attachment 565339 [details] no provider Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a new cloud named(new_Cloud) 2. Do not create a zone under it 3. New component outline , upload , save and continue See attached screenshot Actual results: Expected results: Additional info: rpm -qa|grep aeolus aeolus-conductor-0.8.0-35.el6.noarch rubygem-aeolus-cli-0.3.0-10.el6.noarch aeolus-conductor-doc-0.8.0-35.el6.noarch rubygem-aeolus-image-0.3.0-9.el6.noarch aeolus-all-0.8.0-35.el6.noarch aeolus-conductor-daemons-0.8.0-35.el6.noarch aeolus-configure-2.5.0-15.el6.noarch