Bug 860231
Summary: | [eap6] newly deployed war through JON CLI is not discovered | |||
---|---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | bkramer <bkramer> | |
Component: | Plugin -- JBoss EAP 6 | Assignee: | Heiko W. Rupp <hrupp> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | JON 3.1.0 | CC: | ahovsepy, myarboro | |
Target Milestone: | --- | |||
Target Release: | JON 3.1.2 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | 860233 | |||
: | 860233 (view as bug list) | Environment: | ||
Last Closed: | 2013-09-11 10:59:45 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: |
Description
bkramer
2012-09-25 11:05:17 UTC
This is independent of the CLI. Promotion is an operation and does not trigger a discovery scan in JON. Having said that, as the promote operation runs on the domain controller and this would also be the root resource for a discovery, it may be possible to implement a feature in the plugin container to trigger that scan. The plugin descriptor would need a new flag to indicate the scan required (and on which resource), as we do not want a discovery scan to happen after each operation that is executed. Biljana, can you confirm that this is with JBoss ON 3.1.0 ? I think this was already fixed in 3.1.1 on Aug 14th by Stefan Negrea ( 9d66cddac5b2f0d4c , Bug 829329, master commit: 06a05b1371c1 ) , so that it made it into the 3.1.1 release which was tagged Sept 20th. (In reply to comment #4) > Biljana, can you confirm that this is with JBoss ON 3.1.0 ? > I think this was already fixed in 3.1.1 on Aug 14th by Stefan Negrea > ( 9d66cddac5b2f0d4c , Bug 829329, master commit: 06a05b1371c1 ) , so that it > made it into the 3.1.1 release which was tagged Sept 20th. Yes, it seems ok - I have just tested this with JON 3.1.1 and it worked fine - deployment was immediately discovered. QA: can be closed, as the fix was already done by Stefan in JON 3.1.1 -- see previous comments. Moving to ON_QA as available for testing in ER3 or greater: https://brewweb.devel.redhat.com/buildinfo?buildID=246689 verified on 3.1.2 CR2 (even it was fixed in 3.1.1 - just for making sure) |