Bug 1198702
Summary: | If EAP deployment is updated outside of JBoss ON, subdeployments are marked unavailable in ON | ||
---|---|---|---|
Product: | [JBoss] JBoss Operations Network | Reporter: | dsteigne |
Component: | Plugin -- JBoss EAP 6 | Assignee: | Thomas Segismont <tsegismo> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Mike Foley <mfoley> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | JON 3.3.0 | CC: | dmasirka, fbrychta, jshaughn, loleary, rhatlapa, theute |
Target Milestone: | --- | ||
Target Release: | One-off release | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-01-15 21:00:52 UTC | Type: | Support Patch |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
dsteigne
2015-03-04 16:37:23 UTC
Jay, does that ring a bell? (regarding versioned deployments) With the versioned deployments we should see an abc.ear resource with version 1.0.0. And then later, the same resource with version 1.2.0. The subdeployments should be the same way, resources with stripped names and versioning based on the subdeployment archive versions. After the redeploy the version for each subdeployment should have been updated, if necessary. If the subdeployments are not going green it would indicate the the path's are incorrect (in the plugin config). Of course that should not be the case. Have we reproduced? Jay, no I haven't replicated this locally. He is not deploying the new version via JBoss ON (that works) but via the EAP Admin Console. As there is no documented reproducer attached to this report and it is unclear how the sub-deployments changed from the previous version, this issue is being closed. If you are still experiencing this issue, please provide a complete test/use case that can be used to reproduce the issue. This should include: - version 1 of sample application; - steps used to deploy sample application version 1; - version 2 of sample application; - steps used to deploy sample application version 2; - expected results; - actual results; - any other information that is necessary to reproduce this in an isolated lab instance; |