Created attachment 1162229 [details] engine.log, vdsm.log Description of problem: Email is not sent when configuring the notification - after LV's already exceeded. Version-Release number of selected component: Engine: ovirt-engine-extension-aaa-jdbc-1.1.0-0.0.master.20160424162911.gitb7a9e39.el7.noarch ovirt-engine-tools-backup-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch ovirt-engine-tools-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch ovirt-iso-uploader-4.0.0-0.0.master.20160424162751.git98e29da.el7.centos.noarch ovirt-engine-cli-3.6.2.1-1.el7.centos.noarch ovirt-engine-dwh-4.0.0-0.0.master.20160518051036.git9c6a5cc.el7.centos.noarch ovirt-engine-dbscripts-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch ovirt-engine-setup-plugin-ovirt-engine-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch ovirt-log-collector-4.0.0-0.0.master.20160511153619.git3218ba1.el7.centos.noarch ovirt-host-deploy-1.5.0-0.4.master.20160520091409.git4da06da.el7.centos.noarch ovirt-engine-setup-plugin-websocket-proxy-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch ovirt-vmconsole-proxy-1.0.2-0.0.master.20160518125823.git547e1a7.el7.noarch ovirt-engine-userportal-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch ovirt-engine-setup-plugin-vmconsole-proxy-helper-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch ovirt-engine-extension-aaa-ldap-1.1.5-0.0.master.20160520084617.git4acb486.el7.noarch ovirt-setup-lib-1.0.2-0.0.master.20160502125738.gitf05af9e.el7.centos.noarch ovirt-engine-wildfly-10.0.0-1.el7.x86_64 ovirt-engine-lib-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch ovirt-engine-extensions-api-impl-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch ovirt-host-deploy-java-1.5.0-0.4.master.20160520091409.git4da06da.el7.centos.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch ovirt-engine-websocket-proxy-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch ovirt-engine-backend-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch ovirt-engine-restapi-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch ovirt-engine-setup-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch ovirt-engine-extension-aaa-misc-1.0.1-0.0.master.20160424162924.git1299e21.el7.noarch ovirt-engine-sdk-python-3.6.5.1-1.el7.centos.noarch ovirt-image-uploader-4.0.0-0.0.master.20160424163606.gita3e72cd.el7.centos.noarch ovirt-release-master-4.0.0-0.3.master.20160518074018.gitec2301a.noarch ovirt-engine-dwh-setup-4.0.0-0.0.master.20160518051036.git9c6a5cc.el7.centos.noarch ovirt-engine-webadmin-portal-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch ovirt-engine-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch ovirt-engine-sdk-java-3.6.5.1-0.1.20160425.gitefe1672.el7.noarch ovirt-engine-wildfly-overlay-10.0.0-1.el7.noarch python-ovirt-engine-sdk4-4.0.0-0.0.20160520git7286a65.el7.centos.x86_64 ovirt-vmconsole-1.0.2-0.0.master.20160518125823.git547e1a7.el7.noarch ovirt-engine-vmconsole-proxy-helper-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch ovirt-engine-extension-aaa-ldap-setup-1.1.5-0.0.master.20160520084617.git4acb486.el7.noarch ovirt-engine-setup-base-4.0.0-0.0.master.20160521171336.git2e1899b.el7.centos.noarch VDSM: vdsm-4.18.0-24.gitc9d65a5.el7.centos.x86_64 How reproducible: 100% Steps to Reproduce: 1. Change the value of: AlertOnNumberOfLVs, from 300 to 5 2. Create more than 5 LV's 3. Configure email notification to alert: Storage Domain's number of LVs exceeded threshold Actual results: No email is sent (only when creating additional LV) Expected results: Since there are already more LV's in the storage domain when configuring the alert, it should send an email right away, saying number of LVs in the domain exceeded..
Natalie, this behavior is by design, we don't monitor the total number of LVs in the system regularly for passing the maximum number, this check only occurs when running an operation which results in a creation of an additional LV. See the doctext in bug 1015186 for that matter
Tal, Copied the doctext from bug #1015186: When a block storage domain exceeds a certain number of logical volumes defined in a configuration value, each action that results in the creation of a new logical volume on the domain will add an audit log warning that the number of logical volumes on that domain has exceeded the defined number. The number of logical volumes is defined in the configuration value 'AlertOnNumberOfLVs' and it's default value is 300. What's the relevant part here? What your saying is, the design allows a situation of having like more than 300 lv's in the system, then configuring the notification, and getting this warning only when there are another 300 lv's in this sd.. right?
The relevant part here is "each action that results in the creation of a new logical volume on the domain will add an audit log warning" Meaning that if we exceeded the threshold in every action that will involve creating another LV on the domain that exceeded, this warning will be issued, a domain can contain more LVs than the threshold value and up to the point where we try to create another LV there will be no warning indeed
Hi Yaniv, you've opened RFE #1275182 (Email notification when the number of LVs in SD are reaching/more than 300). I want to make sure that this is indeed the design: Counting lv's in the storage domain starts once we configure the email notification. Meaning, we can have a lot more than 300 lv's in the storage domain, but get the following notification: "you are approaching the limit where performance may degrade." only after creating additional 300 lvs'. Example flow: 1. Create 300 lvs. 2. Configure notification. 3. Create another 300 lv's. 4. Get the notification (which was triggered only by the last lv). Is that true?
You need to get a email every interval of a few hours, due to flooding protraction, if you have more than 300 lvs.
Following comment #5, changing status of this issue.
(In reply to Yaniv Dary from comment #5) > You need to get a email every interval of a few hours, due to flooding > protraction, if you have more than 300 lvs. We check this when we perform a storage operation. There's no monitoring on it, and I doubt we'll ever bother implementing it. Reducing priority and changing to an RFE.
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.
I think we should CLOSE-DEFERRED this until we get customer requests for this.
(In reply to Yaniv Kaul from comment #12) > I think we should CLOSE-DEFERRED this until we get customer requests for > this. ack