Bug 592038
Summary: | RFE:Support updating resource keys (in particular apache) | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Lukas Krejci <lkrejci> |
Component: | Plugins | Assignee: | Lukas Krejci <lkrejci> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 3.0.0 | CC: | ccrouch, skondkar |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-09-02 07:16:19 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: | |||
Bug Blocks: | 536328, 577313, 625146 |
Description
Lukas Krejci
2010-05-13 18:07:32 UTC
Mazz, is looking at this currently. If we don't fix the upgrade process for changed keys, we'll rollback the original change to the apache resource key we're gonna back out the apache change and re-introduce in the next release. see 612189 Comment from Mazz: --- The new "resource upgrade" code performs all its work in the InventoryManager.initialize method, which is nice because its located in one spot (easy for maintenance), and doesn't affect the rest of the PC runtime (so it doesn't affect performance other than startup performance). However, I recommend we hold off on this for 2.4 and put it in the next release. This is because we don't know the ramifications of what the agent behavior will be IF the server is down or an error otherwise occurs during the ugprade. Remember one of our "golden rules" is that any registered agent should always be allowed to start and run, even if the server is down. If an agent is already registered, has its plugins and has persisted inventory (inventory.dat), even if the server is down (or the network is out), the agent will be able to start and can monitor its resources. When the server is back available, the agent can send its spooled messages. In this resource upgrade case, if the server is down, it will fail during inventory manager initialize - will that cause the agent to abort its startup - will it cause the startup to encounter other errors and cause the agent to fail to fully prepare itself? If the agent CAN still continue, is the inventory now corrupted because it no longer has updated resource keys (i.e. it has the old keys still). Will that cause problems when the agent starts to send messages up to the server? So my big question is - what happens to the agent when the agent starts and the server is not available. We need to answer that satisfactorily before we put the resource upgrade code in master. I updated the plugin to use the old-style resource key format for now (bug 612189) and reopened the original bug 536328 the required the resource key change. Reducing severity as this is no longer targeted for the JON2.4 release *** Bug 536297 has been marked as a duplicate of this bug. *** Verified on build#188 (Version: 4.1.0-SNAPSHOT Build Number: c45b0da) Installed jon240 build and Upgraded to latest master build#188. The autodiscovery queue does not display Apache server appearing again. The Apache server is up and the resource key is changed from '/etc/httpd' to '/etc/httpd||/etc/httpd/conf/httpd.conf'. The vhost resource key is changed from 'monitoring-test:8081' to 'monitoring-test:8081|127.0.0.1:8081'. Marking as verified. Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago. |