Bug 749804
Summary: | Updating an existent EAR/WAR to new location deploys properly but displays in UI incorrectly | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Robert Buck <rbuck> |
Component: | Plugins | Assignee: | RHQ Project Maintainer <rhq-maint> |
Status: | CLOSED NOTABUG | QA Contact: | Mike Foley <mfoley> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 3.0.0 | CC: | dsteigne, hrupp, ian.springer, rbuck, rsoares |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | 672240 | Environment: | |
Last Closed: | 2011-11-16 21:03:36 UTC | Type: | --- |
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: | 752918, 752919, 752920, 752921, 752925, 752926, 752928, 752929, 753761, 672240, 752761 | ||
Bug Blocks: | 745494 |
Description
Robert Buck
2011-10-28 13:38:50 UTC
The absolute path to the warfile is used as the Resource key for WAR Resources (see ApplicationDiscoveryComponent). So if you deploy a war to a new path, it will be rediscovered as a new Resource with the new path as the key. The old war Resource will remain in inventory until uninventoried by the user, but it will have an avail of DOWN if the war is no longer deployed to the original location. Resource keys generally do not change. The only exception is if a resource key is changed by the plugin due to a change in key format in a new version of the plugin (see ResourceUpgradeFacet in plugin API), but this is not the case here. I agree with Robert, that this is sort of annoying. There is the workaround of unimport/import for this scenario. Also as application servers could have multiple war files with same names in different directories, RHQ can't just if it sees one go away take the next and hope that this is a redeploy of the other. Also automatic unimport is not desirable, as for a longer existing resource there may be metrics or events that the user still wants to peek at before removing from inventory. I think the above describes sort of "works as designed" |