Bug 790860 - re-enable provider availaibility
Summary: re-enable provider availaibility
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: beta3
Assignee: Jan Provaznik
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-15 15:16 UTC by Jan Provaznik
Modified: 2012-05-15 22:37 UTC (History)
5 users (show)

Fixed In Version: v0.8.0-39
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-15 22:37:05 UTC


Attachments (Terms of Use)
unavailable (221.01 KB, image/png)
2012-02-22 07:07 UTC, Shveta
no flags Details
available (218.85 KB, image/png)
2012-02-22 07:09 UTC, Shveta
no flags Details
provider_avialable (227.99 KB, image/png)
2012-03-01 05:51 UTC, Shveta
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2012:0583 0 normal SHIPPED_LIVE new packages: aeolus-conductor 2012-05-15 22:31:59 UTC

Description Jan Provaznik 2012-02-15 15:16:15 UTC
When a provider is set as unavailable and then becomes available again, the state is not set in DB.

1. create a provider
2. stop dc core and wait until dbomatic sets the provider as unavailable
3. start dc core

the provider stays unavailable

app/models/provider.rb:populate_realms method doesn't set available state properly

Comment 2 Jan Provaznik 2012-02-21 15:07:08 UTC
commit 7df3f7f5a40a5985f4f64a715cf0cd86376673b4

Comment 3 Steve Linabery 2012-02-21 16:28:24 UTC
9c591c2 in aeolus-conductor-0.8.0-32

Comment 4 Shveta 2012-02-22 07:05:52 UTC
Steps followed :
1) Added provider ec2_us_east_1
2) service deltacloud-core stop
Shutting down deltacloud-core: [  OK  ]
3) Cloud-Resource Provider -- Test connection , Screenshot 1 , unavailable
4)service deltacloud-core restart
Shutting down deltacloud-core: [FAILED]
Starting deltacloud-core-mock: [  OK  ]
5) Test Connection , Succesfully connected to provider , Screenshot 2 , available


Issue is fixed .. Provider is available after restarting deltacloud-core 
but the message still shows "not available"

Flipping to assigned to fix the message ..

rpm -qa|grep aeolus
aeolus-conductor-daemons-0.8.0-33.el6.noarch
aeolus-configure-2.5.0-14.el6.noarch
rubygem-aeolus-image-0.3.0-8.el6.noarch
aeolus-conductor-0.8.0-33.el6.noarch
rubygem-aeolus-cli-0.3.0-9.el6.noarch
aeolus-conductor-doc-0.8.0-33.el6.noarch
aeolus-all-0.8.0-33.el6.noarch

Comment 5 Shveta 2012-02-22 07:07:57 UTC
Created attachment 564846 [details]
unavailable

Comment 6 Shveta 2012-02-22 07:09:08 UTC
Created attachment 564847 [details]
available

Comment 7 Jan Provaznik 2012-02-27 12:22:04 UTC
sent improved version: https://fedorahosted.org/pipermail/aeolus-devel/2012-February/009167.html

this version updates availability on 'test connection' and successful 'update' action, so a user doesn't have to wait for a couple of minutes when availability flag is set from dbomatic periodic refresh.

Comment 8 Jan Provaznik 2012-02-29 09:33:19 UTC
commit 3a3e5c96b7cb8781b0ef1001b6a476afa39d355d

Comment 9 Steve Linabery 2012-02-29 23:43:16 UTC
bec9399

Comment 10 Shveta 2012-03-01 05:50:20 UTC
Fixed.. 

Verified in 

rpm -qa|grep aeolus
aeolus-conductor-doc-0.8.0-39.el6.noarch
aeolus-configure-2.5.0-16.el6.noarch
rubygem-aeolus-image-0.3.0-10.el6.noarch
aeolus-conductor-0.8.0-39.el6.noarch
rubygem-aeolus-cli-0.3.0-12.el6.noarch
aeolus-all-0.8.0-39.el6.noarch
aeolus-conductor-daemons-0.8.0-39.el6.noarch

Comment 11 Shveta 2012-03-01 05:51:30 UTC
Created attachment 566753 [details]
provider_avialable

Comment 12 errata-xmlrpc 2012-05-15 22:37:05 UTC
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


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