Bug 1313316
| Summary: | EAP7 - unable to update configuration of Distributed Cache | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Filip Brychta <fbrychta> |
| Component: | Plugin -- JBoss EAP 7 | Assignee: | Thomas Segismont <tsegismo> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Filip Brychta <fbrychta> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | JON 3.3.5 | CC: | hrupp, loleary, miburman, spinder |
| Target Milestone: | DR01 | Keywords: | Triaged |
| Target Release: | One-off release | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-06-06 18:57:28 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: | 1314853 | ||
Pull request sent https://github.com/rhq-project/rhq/pull/214 Updated all Infinispan subsystem resource types, many attributes have been drepecated, and while the management interface lets us write values, the server fails to restart because the attributes are no longer defined in the subsystem schema file. Little bonus: added common metrics to cache resource types. |
Description of problem: Update of Distributed Cache fails with {WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:={Operation step-13=WFLYCTL0201: Unknown attribute 'virtual-nodes'}}, rolled-back=true Version-Release number of selected component (if applicable): JON3.3.5 with eap plugin pack03-dr01 How reproducible: Always Steps to Reproduce: 1. create new Distributed Cache (infinispan->cache container->Create new child->Distributed Cache) 2. try update configuration of Distributed Cache Actual results: fails with {WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:={Operation step-13=WFLYCTL0201: Unknown attribute 'virtual-nodes'}}, rolled-back=true Expected results: Configuration is correctly updated Additional info: It's caused by different attributes in eap6 and eap7. EAP6: /subsystem=infinispan/cache-container=testik/distributed-cache=testdist:read-resource { "outcome" => "success", "result" => { "async-marshalling" => undefined, "batching" => false, "indexing" => "NONE", "indexing-properties" => undefined, "jndi-name" => undefined, "l1-lifespan" => 600000, "mode" => "SYNC", "module" => undefined, "owners" => 2, "queue-flush-interval" => 10L, "queue-size" => 0, "remote-timeout" => 17500L, "segments" => 80, "start" => "LAZY", "statistics-enabled" => undefined, "virtual-nodes" => 1, "binary-keyed-jdbc-store" => undefined, "eviction" => undefined, "expiration" => undefined, "file-store" => undefined, "locking" => undefined, "mixed-keyed-jdbc-store" => undefined, "remote-store" => undefined, "state-transfer" => undefined, "store" => undefined, "string-keyed-jdbc-store" => undefined, "transaction" => undefined } } EAP7: /subsystem=infinispan/cache-container=test/distributed-cache=testdist:read-resource { "outcome" => "success", "result" => { "async-marshalling" => false, "batching" => false, "capacity-factor" => 1.0, "consistent-hash-strategy" => "INTRA_CACHE", "indexing" => "NONE", "indexing-properties" => undefined, "jndi-name" => undefined, "l1-lifespan" => 600000L, "mode" => "SYNC", "module" => undefined, "owners" => 2, "queue-flush-interval" => 10L, "queue-size" => 0, "remote-timeout" => 17500L, "segments" => 80, "start" => "LAZY", "statistics-enabled" => false, "backup-for" => {"BACKUP_FOR" => undefined}, "component" => { "expiration" => undefined, "state-transfer" => undefined, "eviction" => undefined, "locking" => undefined, "backups" => undefined, "transaction" => undefined, "backup-for" => undefined, "partition-handling" => undefined }, "eviction" => {"EVICTION" => undefined}, "expiration" => {"EXPIRATION" => undefined}, "locking" => {"LOCKING" => undefined}, "state-transfer" => {"STATE_TRANSFER" => undefined}, "store" => {"none" => undefined}, "transaction" => {"TRANSACTION" => undefined} } } It will be necessary to check differences in other resource types as well.