857042 – Attempted to update a stale object: Instance displayed while trying stop instance from a disabled pool.

Bug 857042 - Attempted to update a stale object: Instance displayed while trying stop instance from a disabled pool.

Summary: Attempted to update a stale object: Instance displayed while trying stop inst...

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	CloudForms Cloud Engine
Classification:	Retired
Component:	aeolus-conductor
Sub Component:
Version:	1.1.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	medium
Target Milestone:	beta2
Assignee:	Tzu-Mainn Chen
QA Contact:	Rehana
Docs Contact:
URL:
Whiteboard:
Duplicates (1):	857037 (view as bug list)
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2012-09-13 12:51 UTC by Aziza Karol
Modified:	2012-12-04 15:19 UTC (History)
CC List:	4 users (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Attempts to stop an application in a disabled pool resulted in an "Attempted to update a stale object" error. This fix restricts enabled pool validation to run only when creating applications. Users now stop applications in disabled pools without error.
Clone Of:
Environment:
Last Closed:	2012-12-04 15:19:02 UTC
Embargoed:

Attachments	(Terms of Use)
stale error (54.76 KB, image/png) 2012-09-13 12:53 UTC, Aziza Karol	no flags	Details
View All

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHEA-2012:1516	0	normal	SHIPPED_LIVE	CloudForms Cloud Engine 1.1 update	2012-12-04 19:51:45 UTC

Description Aziza Karol 2012-09-13 12:51:47 UTC

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.create a new pool aziza.
2.launched a mock or ec2 deployment.
3.disabled the pool aziza.
4.Navigate to monitor page,click on the deployment name and click on the stop button.
  
Actual results:
The Instance mock-aziza/f15 was not stopped because Attempted to update a stale object: Instance . see attached screenshot

Note:The above message is displayed only for the first attempt,the second time you try to  stop the same instance it displays "stop action was successfully queued"


Expected results:
Proper message should be displayed.

Additional info:
rpm -qa | grep aeolus
rubygem-aeolus-cli-0.7.0-0.20120912180029git8a46b3f.fc16.noarch
aeolus-conductor-daemons-0.13.0-0.20120912220011gite97ce9e.fc16.noarch
aeolus-configure-2.8.0-0.20120912180027git0b3dad6.fc16.noarch
aeolus-conductor-0.13.0-0.20120912220011gite97ce9e.fc16.noarch
aeolus-all-0.13.0-0.20120912220011gite97ce9e.fc16.noarch
rubygem-aeolus-image-0.6.0-0.20120912180033git902c81c.fc16.noarch
aeolus-conductor-doc-0.13.0-0.20120912220011gite97ce9e.fc16.noarch

Comment 1 Aziza Karol 2012-09-13 12:53:05 UTC

Created attachment 612429 [details]
stale error

Comment 3 Mike Orazi 2012-09-13 18:32:03 UTC

Bucketing for beta2

Comment 4 Tzu-Mainn Chen 2012-09-19 13:24:27 UTC

Patch created:

http://lists.fedorahosted.org/pipermail/aeolus-devel/2012-September/012615.html

Comment 5 Matt Wagner 2012-09-19 14:04:20 UTC

Pushed:

commit 8d2b3cda7daf25ad1d114e4d01d477f98851bca3
Author: Tzu-Mainn Chen <tzumainn>
Date:   Wed Sep 19 09:23:03 2012 -0400

    BZ857042 only validate pool_must_be_enabled on create
    
    Signed-off-by: Matt Wagner <matt.wagner>
    (cherry picked from commit 2351ad7d8f8d93be04bc9ab57608821b37de28d5)

Comment 7 Scott Seago 2012-09-19 19:01:40 UTC

*** Bug 857037 has been marked as a duplicate of this bug. ***

Comment 8 Aziza Karol 2012-09-25 06:57:03 UTC

stop action was successfully queued is displayed now.
Instance state is  updated for disabled pool.

verified:
rpm -qa | grep aeolus
rubygem-aeolus-image-0.3.0-12.el6.noarch
rubygem-aeolus-cli-0.7.2-1.el6cf.noarch
aeolus-conductor-doc-0.13.14-1.el6cf.noarch
aeolus-configure-2.8.7-1.el6cf.noarch
aeolus-all-0.13.14-1.el6cf.noarch
aeolus-conductor-0.13.14-1.el6cf.noarch
aeolus-conductor-daemons-0.13.14-1.el6cf.noarch

Comment 10 errata-xmlrpc 2012-12-04 15:19:02 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-1516.html

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