Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 688126

Summary: Errors are not handled properly
Product: [Retired] CloudForms Cloud Engine Reporter: Jan Provaznik <jprovazn>
Component: aeolus-conductorAssignee: Scott Seago <sseago>
Status: CLOSED CURRENTRELEASE QA Contact: wes hayutin <whayutin>
Severity: high Docs Contact:
Priority: unspecified    
Version: 0.3.1CC: cpelland, deltacloud-maint
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: 2011-03-16 14:23:15 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:
Bug Depends On:    
Bug Blocks: 684278    
Attachments:
Description Flags
ss1
none
ss2 none

Description Jan Provaznik 2011-03-16 12:06:42 UTC 
Description of problem:
When exception is raised somewhere in controller/model, only blank form is displayed. I guess error layout is broken.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Try to create new provider account and leave all fields blank.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 wes hayutin 2011-03-16 14:03:43 UTC 
Created attachment 485742 [details]
ss1

[root@dell-pe2900-01 ~]# rpm -qa | grep aeolus
aeolus-conductor-debuginfo-0.0.3-0.fc1420110311212550gitab7a7ba.x86_64
aeolus-conductor-doc-0.0.3-0.fc1420110311212550gitab7a7ba.x86_64
aeolus-conductor-daemons-0.0.3-0.fc1420110311212550gitab7a7ba.x86_64
aeolus-conductor-0.0.3-0.fc1420110311212550gitab7a7ba.x86_64
aeolus-configure-2.0.0-4.fc1420110311170652gite6ac5c7.noarch
Comment 2 wes hayutin 2011-03-16 14:04:07 UTC 
Created attachment 485744 [details]
ss2

ss after clicking add
Comment 3 wes hayutin 2011-03-16 14:23:15 UTC 

*** This bug has been marked as a duplicate of bug 678390 ***
Comment 4 wes hayutin 2011-12-08 14:15:17 UTC 
perm close