-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spec test for excluding orphaned vms from quota. #132
Conversation
@miq-bot add_label enhancement |
@tinaafitz Please Review |
Checked commits billfitzgerald0120/manageiq-content@4543f41~...7c090fd with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
@miq-bot assign @gmcculloug |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@billfitzgerald0120 Looks good.
@gmcculloug Please review.
@billfitzgerald0120 @tinaafitz @gmcculloug I'm wondering if retired VMs should also be excluded from the count. The quota returned for the other objects do no include retired VMs. |
@branic Normally, retired VMs have no ems because they've been removed from the provider. They remain in our VMDB for reporting purposes. I know that customers have changed the retirement workflow to mark the VM as retired, but not remove it from the provider until some time in the future. Is your concern the customer modified retirement workflow? |
@tinaafitz The retired VMs being included in the count came up from a customer I was working with. They have a two stage retirement. In the first stage the VM is just powered off and marked as retired. In the second stage the VM is removed from the provider some number of days after the initial retirement. In the time between the two stages VMs that were retired from the first stage were being counted in the quota for Maximum VMs. As their retirement process was customized and is not what happens OOTB I don't think that the base MIQ code needs to be changed to support this. |
@billfitzgerald0120 Cannot apply the following label because they are not recognized: fine/yes. |
@simaishi I created a 5.8 BZ for this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1515979 |
Spec test for excluding orphaned vms from quota. (cherry picked from commit ee6a58c) https://bugzilla.redhat.com/show_bug.cgi?id=1518374
Fine backport details:
|
Modified spec test count to reflect change made by branic to exclude VMs with no EMS in the Quota used calculation.
I have included branic's change in this PR.
#129