Bug 782574 - conductor needs better messaging / errors if deltacloud goes down
Summary: conductor needs better messaging / errors if deltacloud goes down
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
Assignee: Tzu-Mainn Chen
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-17 18:37 UTC by wes hayutin
Modified: 2012-08-30 17:14 UTC (History)
6 users (show)

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


Attachments (Terms of Use)
ss (130.57 KB, image/png)
2012-02-24 04:56 UTC, wes hayutin
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 749376 0 unspecified CLOSED aeolus-image should gracefully handle Conductor being down 2021-02-22 00:41:40 UTC

Internal Links: 749376

Description wes hayutin 2012-01-17 18:37:58 UTC
Description of problem:

recreate:

1. stop the detacloud service
2. edit a realm's (cluster/datastore)

result: get a misrendered page


1. stop detacloud service
2. start an instance

result: get class:nill error


We should be able to detect and provide better messaging to the user


[root@qeblade31 ~]# rpm -qa | grep aeolus
aeolus-conductor-daemons-0.8.0-7.el6.noarch
aeolus-conductor-doc-0.8.0-7.el6.noarch
rubygem-aeolus-cli-0.3.0-3.el6.noarch
rubygem-aeolus-image-0.3.0-2.el6.noarch
aeolus-all-0.8.0-7.el6.noarch
aeolus-configure-2.5.0-4.el6.noarch
aeolus-conductor-0.8.0-7.el6.noarch
[root@qeblade31 ~]# rpm -qa | grep delta
deltacloud-core-ec2-0.5.0-1.rc1.el6.noarch
deltacloud-core-vsphere-0.5.0-1.rc1.el6.noarch
deltacloud-core-0.5.0-1.rc1.el6.noarch
rubygem-deltacloud-client-0.4.0-3.el6.noarch
deltacloud-core-rhevm-0.5.0-1.rc1.el6.noarch

Comment 1 Tzu-Mainn Chen 2012-02-03 19:49:33 UTC
Patch created; it should work every time we fail to connect to a provider account.  It also handles a few cases where iwhd is down:

https://fedorahosted.org/pipermail/aeolus-devel/2012-February/008630.html

Comment 2 Tzu-Mainn Chen 2012-02-09 16:02:43 UTC
Revised patch, smaller in scope, but also less likely to accidentally break something else.

https://fedorahosted.org/pipermail/aeolus-devel/2012-February/008765.html

Comment 3 Tzu-Mainn Chen 2012-02-10 14:32:27 UTC
Patch pushed to 1.0-staging:

commit 843b810748a2965f23474be27278119356ec04c9
BZ 782574 add error messages when unable to connect to provider account/iwhd

commit cb115528eaf4e761a6a3c5f731df33a414944732
BZ 782574 added exception if unable to connect to provider_account

Comment 4 Steve Linabery 2012-02-14 15:39:49 UTC
843b810  cb11552 in aeolus-conductor-0.8.0-26

Comment 5 wes hayutin 2012-02-24 04:56:58 UTC
Created attachment 565491 [details]
ss

no error received when editing a cloud resource cluster when dc is down

Comment 6 wes hayutin 2012-02-24 17:28:47 UTC
working in ...


[root@qeblade31 deltacloud-core]# rpm -qa | grep aeolus
aeolus-conductor-daemons-0.8.0-36.el6.noarch
aeolus-conductor-0.8.0-36.el6.noarch
rubygem-aeolus-cli-0.3.0-10.el6.noarch
aeolus-all-0.8.0-36.el6.noarch
aeolus-conductor-doc-0.8.0-36.el6.noarch
rubygem-aeolus-image-0.3.0-10.el6.noarch
aeolus-configure-2.5.0-15.el6.noarch


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