Bug 835699
| Summary: | [as7] Warnings When Loading Resource Configuration | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | Stefan Negrea <snegrea> | ||||
| Component: | Plugins | Assignee: | Armine Hovsepyan <ahovsepy> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.4 | CC: | hrupp, mfoley | ||||
| Target Milestone: | --- | ||||||
| Target Release: | JON 3.1.1 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | 831369 | Environment: | |||||
| Last Closed: | 2013-09-03 15:08:09 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: | 831369 | ||||||
| Bug Blocks: | 707223 | ||||||
| Attachments: |
|
||||||
|
Description
Stefan Negrea
2012-06-26 20:58:50 UTC
release/jon3.1.x branch commit: http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=commit;h=a851500532e8e3b2559ebaffe515e7b68ab57e88 JON 3.1.1 ER1 build is available. Moving to ON_QA. https://brewweb.devel.redhat.com/buildinfo?buildID=226942 Created attachment 602528 [details]
agent.log
reopened.
the errors are still visible.
The log does not have any errors related to the name property. The log still contains typical discovery warnings because the server was started without some subsystems.
Please look again in the logs for errors of the following type:
12:14:09,940 WARN [ASConnection] Received 500 (Internal Server Error) response to Operation{operation='read-attribute', address=Address{path: subsystem=transactions,log-store=log-store}, additionalProperties={name=name}} - response body was [{"outcome" : "failed", "failure-description" : "JBAS014792: Unknown attribute name", "rolled-back" : true, "response-headers" : {"process-state" : "reload-required"}}].
Note the additionalProperties={name=name} part and the error related to it being an unknown attribute.
verified. No Internal Server error for read-attribute with name=name is visible in the logs. Bulk closing of old issues in VERIFIED state. |