Bug 1658670
Summary: | Not able to select vmdb/log as an event driver | |||
---|---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Ryan Spagnola <rspagnol> | |
Component: | Appliance | Assignee: | Joe Rafaniello <jrafanie> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | John Dupuy <jdupuy> | |
Severity: | high | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> | |
Priority: | high | |||
Version: | 5.8.5 | CC: | abellott, bmidwood, dmetzger, jdupuy, jocarter, jrafanie, obarenbo, rspagnol | |
Target Milestone: | GA | Keywords: | TestOnly, ZStream | |
Target Release: | 5.11.0 | |||
Hardware: | All | |||
OS: | All | |||
Whiteboard: | ||||
Fixed In Version: | 5.11.0.1 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1672698 (view as bug list) | Environment: | ||
Last Closed: | 2019-12-13 15:16:54 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | CFME Core | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1705139, 1707871 | |||
Bug Blocks: | 1672698 |
Description
Ryan Spagnola
2018-12-12 16:09:22 UTC
I took a look at this and we don't have an event for the log disk. See [1]. In upstream, we don't have an external disk for the /var/www/miq/vmdb/log directory, see [2]. In downstream, we have a separate disk for this /var/www/miq/vmdb/log directory but don't add a new event definition. I don't believe we ever did have an event for this so I'm not sure how the documentation has it. Either way, in a test environment, if you add a line to the vmdb/db/fixtures/miq_event_definitions.csv for this new event and restart, you should be able to try it out and see if it works as you want. If so, this can become a RFE to add this feature. In other words ... evm_server_system_disk_high_usage,Server High System Disk Usage,Default,evm_operations evm_server_boot_disk_high_usage,Server High /boot Disk Usage,Default,evm_operations evm_server_home_disk_high_usage,Server High /home Disk Usage,Default,evm_operations evm_server_var_disk_high_usage,Server High /var Disk Usage,Default,evm_operations Add the following line: evm_server_vmdb_log_disk_high_usage,Server High vmdb/log Disk Usage,Default,evm_operations evm_server_var_log_disk_high_usage,Server High /var/log Disk Usage,Default,evm_operations evm_server_var_log_audit_disk_high_usage,Server High /var/log/audit Disk Usage,Default,evm_operations evm_server_miq_tmp_disk_high_usage,Server High Temp Storage Disk Usage,Default,evm_operations evm_server_tmp_disk_high_usage,Server High /tmp Disk Usage,Default,evm_operations ... [1] https://github.com/ManageIQ/manageiq/blob/602b4347e65f9091ac4ea02997d4d5dd3a1f2e2a/db/fixtures/miq_event_definitions.csv#L18-L25 [2] https://github.com/ManageIQ/manageiq-appliance-build/blob/e280b2b0cf73e9508d257a8d43bba49d174dd528/kickstarts/partials/main/disk_layout.ks.erb#L10-L15 Upstream PR https://github.com/ManageIQ/manageiq/pull/18340, merged With bug 1705139 and bug 1707871 both fixed, I was able to verify this BZ in CFME 5.11.0.4.20190514210444_0c91ee1. Steps of verification were the same as those of bug 1672698. This BZ has automated test coverage here: https://github.com/ManageIQ/integration_tests/blob/2ba0baca2a0ec7379f0e2ff3dadd5d3e171435bb/cfme/tests/control/test_bugs.py#L394-L452 |