Bug 701337
| Summary: | Add UPDATE_INTERVAL to base-db | ||
|---|---|---|---|
| Product: | Red Hat Enterprise MRG | Reporter: | Robert Rati <rrati> |
| Component: | condor-wallaby-base-db | Assignee: | Robert Rati <rrati> |
| Status: | CLOSED ERRATA | QA Contact: | Lubos Trilety <ltrilety> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | low | ||
| Version: | 2.0 | CC: | jneedle, ltrilety, matt, mkudlej, tstclair |
| Target Milestone: | 2.0.1 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | condor-wallaby-base-db-1.14-1 | Doc Type: | Bug Fix |
| Doc Text: |
This update adds the UPDATE_INTERVAL parameter to the default database of the remote configuration. The UPDATE_INTERVAL parameter defines the interval in which the startd daemon checks with the collector when using remote configuration.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-09-07 16:45:03 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: | 723887 | ||
|
Description
Robert Rati
2011-05-02 15:57:05 UTC
Added UPDATE_INTERVAL Fixed on master
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
C: A desire to reduce the time a startd checks in with the collector when using remote configuration
C: The user would have to manually add the UPDATE_INTERVAL parameter before it could be configured.
C: Added a new parameter to remote configuration's default database.
R: The user does not have to add the parameter before it can be used.
Tested on RHEL 5.7/6.1 x x86_64/i386 with condor-wallaby-base-db-1.14-1 and UPDATE_INTERVAL is in database but it is not bound with any subsystem. It is mentioned in #c1 that it should be set in some subsystems. Is this OK or not? Ideally UPDATE_INTERVAL should be attached to the startd subsystem, but no necessary. This is because the configd will sent a reconfig to master, which will send it to all daemons including the startd, whenever there is a new configuration if wallaby doesn't tell the configd to restart any subsystems. A reconfig is all that is needed for the startd to pick up the UPDATE_INTERVAL, so not having it attached to the startd won't affect functionality. For attaching UPDATE_INTERVAL to startd a new bug 727890 was created. Tested on: condor-wallaby-base-db-1.14-1.el5 condor-wallaby-base-db-1.14-1.el6 >>> VERIFIED
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,4 +1 @@
-C: A desire to reduce the time a startd checks in with the collector when using remote configuration
+This update adds the UPDATE_INTERVAL parameter to the default database of the remote configuration. The UPDATE_INTERVAL parameter defines the interval in which the startd daemon checks with the collector when using remote configuration.-C: The user would have to manually add the UPDATE_INTERVAL parameter before it could be configured.
-C: Added a new parameter to remote configuration's default database.
-R: The user does not have to add the parameter before it can be used.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-1249.html |