| Summary: | creating a vsphere account produces a blank screen | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | dgao | ||||||||
| Component: | aeolus-conductor | Assignee: | Jan Provaznik <jprovazn> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | wes hayutin <whayutin> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 1.0.0 | CC: | akarol, deltacloud-maint, slinaber, ssachdev | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-08-30 17:12:49 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: |
|
||||||||||
|
Description
dgao
2012-01-03 23:29:50 UTC
Created attachment 550575 [details]
vsphere_account_create
Created attachment 550576 [details]
blank screen
this is result of 3 different bugs: 1) DC API returns invalid memory range: https://issues.apache.org/jira/browse/DTACLOUD-123 invalid range is returned only if almost all memory on vsphere server is used, IOW there is less than 128 MB free RAM. So it will be hard to reproduce/verify it's fixed. 2) when an account is added, hw profiles are fetched from DC API, but a hw profile save fails because 1) occurs. So neither hw profiles nor the account are saved. Because populate_hw_profiles is called in after_Create callback, account has not-nil id even if it wasn't saved. 3) new/edit provider account forms don't set explicitly form's url, in normal situation proper url is generated. But if 2) occurs (id is set but the accoutn is not saved), form's url points to 'update' action instead of 'create' action (rails thinks it's existing record), after submitting the form, rails raises exception 'not acceptable' to the rails log. the patch is waiting for a review: https://fedorahosted.org/pipermail/aeolus-devel/2012-January/007936.html pushed in commits: e6e7d22a63edbce360fa277352d47e46df65da1c 12d9f554c54b92292ef5b74ba00582989ca0be23 37122116e6b54049cfd847e9d89c57f5074d2ff7 aaabc4e7d2c30f3dad300fafb8353cbfe180e3f4 c092cb4ac7297d266eb129940da13a96c2f15ef1 e686cfb3511c7367008fccdb071f5f8ccfd9e202 in aeolus-conductor-0.8.0-8.el6.src.rpm creating a vsphere account does not produces a blank screen. vsphere account gets added. rpm -qa | grep aeolus aeolus-conductor-0.8.0-8.el6.noarch rubygem-aeolus-cli-0.3.0-4.el6.noarch aeolus-configure-2.5.0-5.el6.noarch aeolus-conductor-daemons-0.8.0-8.el6.noarch aeolus-configserver-0.4.5-2.el6.noarch rubygem-aeolus-image-0.3.0-3.el6.noarch aeolus-all-0.8.0-8.el6.noarch aeolus-conductor-doc-0.8.0-8.el6.noarch Created attachment 556218 [details]
vsphere account
|