Bug 744081
| Summary: | monitor > instances blinks when instances stop | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | dgao | ||||||
| Component: | aeolus-conductor | Assignee: | Matt Wagner <matt.wagner> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | wes hayutin <whayutin> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 1.0.0 | CC: | akarol, athomas, dajohnso, deltacloud-maint, dgao, slinaber, ssachdev | ||||||
| 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: | 2012-05-15 22:14:56 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
dgao
2011-10-06 22:28:07 UTC
Created attachment 526813 [details]
Before
Attached screenshot demonstrates the behavior. The item in question is test_deployable_4/frontend
Created attachment 526814 [details]
After
Attached screenshot demonstrates the behavior. The item in question is test_deployable_4/frontend
adding ce-sprint-next bugs to ce-sprint I have verified that this is still occurring. What is actually happening here is this: the state goes to "stopped," and the filter selected on the page is "Non-stopped instances," so the instance correctly goes away. However, when instances are periodically reloaded on the page, that filter seems to be ignored, and the stopped instance(s) come back. It appears that the auto-update feature is just ignoring the filter -- if I select "Stopped instances," only stopped instances are shown, until the next refresh, in which case all instances are displayed again while the filter still indicates that it's selected. Pushed:
commit 6fa3ce38443d49b0f3a9ae075ea2d3313652744b
Author: Matt Wagner <matt.wagner>
Date: Thu Jan 5 14:26:17 2012 -0500
Backbone will always use preset_filter value if present
If the filter isn't changed, it won't be in the URL, so we need to
read the form element's value and use that.
This should resolve https://bugzilla.redhat.com/show_bug.cgi?id=744081
6fa3ce38443d49b0f3a9ae075ea2d3313652744b in aeolus-conductor-0.8.0-2.el6.src.rpm bugs in verified or on_qa moving off tracker Stopped instance from Vsphere Client . Instance was removed from "Non-stopped Instance " list It can be seen in "Stopped Instance" list. rpm -qa|grep aeolus aeolus-conductor-daemons-0.8.0-21.el6.noarch aeolus-configure-2.5.0-12.el6.noarch aeolus-conductor-doc-0.8.0-21.el6.noarch rubygem-aeolus-image-0.3.0-7.el6.noarch rubygem-aeolus-cli-0.3.0-8.el6.noarch aeolus-conductor-0.8.0-21.el6.noarch aeolus-all-0.8.0-21.el6.noarch 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 |