-
Notifications
You must be signed in to change notification settings - Fork 118
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
Fixes VM extend retirement #62
Conversation
@tinaafitz @mkanoor Please review. |
@tinaafitz Should this logic be changed to use the |
@psachin Thanks for the fixing the methods. We added an extend_retires_on method as mentioned by @gmcculloug. I created a PR to address the days issue there. Once that PR gets merged, can you change the 2 Automate methods to use the new method. |
@tinaafitz Sure |
The retires_on field was changed from a `:date` column to a `:datetime` which now requires the days(in seconds) be added to the time. - Depends on: ManageIQ/manageiq#14143 - This issue was introduced in PR ManageIQ/manageiq#11156 - https://bugzilla.redhat.com/show_bug.cgi?id=1427503 Signed-off-by: Sachin <psachin@redhat.com>
Checked commit psachin@81535b3 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
Merging to get fix in. @billfitzgerald0120 is working on refactoring and adding tests which will come in a followup PR. |
Euwe backport details:
|
The
retires_on
field was changed from a:date
column to a:datetime
which now requires the days (in seconds) be added to the time.https://bugzilla.redhat.com/show_bug.cgi?id=1427503
This issue was introduced in PR ManageIQ/manageiq#11156