Skip to content
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

Fail explicitly for MAS validation failure #15473

Merged
merged 1 commit into from
Jul 6, 2017

Conversation

moolitayer
Copy link

@moolitayer moolitayer commented Jun 29, 2017

During MiqAlert.evaluate when creating a new MiqAlertStatus, validation can fail[1].
In those cases we should fail the operation. Otherwise we can have a MiqAlert evaluated as true and silently not create a MAS.

[1] e.g mas.severity = 'unknown'

@moolitayer moolitayer changed the title Fail explicitly for MAS validation Fail explicitly for MAS validation failure Jun 29, 2017
@moolitayer
Copy link
Author

@cben @zgalor please review

@moolitayer
Copy link
Author

@gmcculloug can you take a look?

@gmcculloug
Copy link
Member

Looks good, just missing tests.

@chessbyte
Copy link
Member

@moolitayer is there a GitHub Issue or Bugzilla Case that this PR is addressing?

@moolitayer
Copy link
Author

No, just an issue I encountered during development.
it is explained in #15473 (comment)

@moolitayer
Copy link
Author

@gmcculloug done, please take a look

@miq-bot
Copy link
Member

miq-bot commented Jul 6, 2017

Checked commit moolitayer@01626ae with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
2 files checked, 0 offenses detected
Everything looks fine. 🍪

@gmcculloug gmcculloug merged commit 03ba893 into ManageIQ:master Jul 6, 2017
@gmcculloug gmcculloug added this to the Sprint 64 Ending Jul 10, 2017 milestone Jul 6, 2017
@moolitayer
Copy link
Author

🍻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants