Bug 815899
Summary: | Resource configuration unavailable using remote API after import | |||
---|---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Lukas Krejci <lkrejci> | |
Component: | Configuration | Assignee: | Lukas Krejci <lkrejci> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | |
Severity: | urgent | Docs Contact: | ||
Priority: | high | |||
Version: | 4.4 | CC: | hrupp, lzoubek | |
Target Milestone: | --- | |||
Target Release: | JON 3.1.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 822880 (view as bug list) | Environment: | ||
Last Closed: | 2013-09-03 15:17:38 UTC | Type: | Bug | |
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: | 782579, 822880 |
Description
Lukas Krejci
2012-04-24 18:34:53 UTC
per BZ triage ccrouch, loleary, mfoley Check if this is a regression from JON3.0.1, if not, push to JON3.1.1 Not a regression from JON3.0.1, but I've run into this BZ when verifying bug 801638. Anyone trying to use add-as7-standalone-server-to-cluster.js sample right after importing one of AS7 servers will fail running this script. per Libor's comment, this needs to be in 3.1 to allow 801638 to work. changing target release to 3.1 release/jon3.1.x http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commitdiff;h=85f7920eb79ad999623beda1fc5408e39f96d29c Author: Lukas Krejci <lkrejci> Date: Fri May 18 13:43:21 2012 +0200 [BZ 822880] - Make sure to NOT discard any pending DB changes before masking the configuration. (cherry picked from commit 43770f14dd308618f47b4d2940366cb86082aef0) Note that the change only specifically fixes the errorneous state where the configuration would NEVER be attached to the resource if the user viewed the resource's configuration in the GUI prior to agent sending the first configuration report. It DOES NOT make sure that the resource's configuration is available instantly after import using the standard remote API calls. The resource configuration attached to the resource represents the "last known" configuration and we make no guarantees about it being available - the "raw" remote API therefore shouldn't be changed in any way for that. The ProxyFactory, though, being our convenience wrapper around resource, could be enhanced to overcome that limitation (and use the same method calls as the GUI does to fetch the live config from the agent if no last known config has been fetched yet). I created a separate RFE bug 822968 for that. Bulk closing of old issues in VERIFIED state. |