Bug 771519 - creating a vsphere account produces a blank screen
Summary: creating a vsphere account produces a blank screen
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Jan Provaznik
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-03 23:29 UTC by dgao
Modified: 2012-08-30 17:12 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-30 17:12:49 UTC


Attachments (Terms of Use)
vsphere_account_create (212.33 KB, image/png)
2012-01-03 23:30 UTC, dgao
no flags Details
blank screen (26.27 KB, image/png)
2012-01-03 23:30 UTC, dgao
no flags Details
vsphere account (250.91 KB, image/png)
2012-01-19 09:05 UTC, Aziza Karol
no flags Details

Description dgao 2012-01-03 23:29:50 UTC
During the account creation process for vsphere, if the priority field is set to a number, hitting save would produce a blank screen.

Comment 1 dgao 2012-01-03 23:30:19 UTC
Created attachment 550575 [details]
vsphere_account_create

Comment 2 dgao 2012-01-03 23:30:43 UTC
Created attachment 550576 [details]
blank screen

Comment 3 Jan Provaznik 2012-01-10 14:19:22 UTC
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.

Comment 4 Jan Provaznik 2012-01-11 19:08:02 UTC
the patch is waiting for a review: https://fedorahosted.org/pipermail/aeolus-devel/2012-January/007936.html

Comment 5 Jan Provaznik 2012-01-18 08:33:48 UTC
pushed in commits:
e6e7d22a63edbce360fa277352d47e46df65da1c
12d9f554c54b92292ef5b74ba00582989ca0be23
37122116e6b54049cfd847e9d89c57f5074d2ff7

Comment 6 Steve Linabery 2012-01-18 20:41:00 UTC
aaabc4e7d2c30f3dad300fafb8353cbfe180e3f4
c092cb4ac7297d266eb129940da13a96c2f15ef1
e686cfb3511c7367008fccdb071f5f8ccfd9e202

in aeolus-conductor-0.8.0-8.el6.src.rpm

Comment 7 Aziza Karol 2012-01-19 09:02:57 UTC
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

Comment 8 Aziza Karol 2012-01-19 09:05:16 UTC
Created attachment 556218 [details]
vsphere account


Note You need to log in before you can comment on or make changes to this bug.