Description of problem:
Publish to Template process fails with error 'Error: [EVM] VM [template-test] Step [EmailOwner] Status [Error Emailing Owner]'
This happens on fresh appliances where I haven't touched anything related to email in config. So there is no user error surrounding email.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Add VMware provider
2.Select any VM
3.Lifecycle-> publish to template
Request fails with error Emailing Owner
Request should succeed
Seems like this was never backported, fixed in the 5.11, under this BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1698542
and my BZ https://bugzilla.redhat.com/show_bug.cgi?id=1703592 was closed duplicate.
Hello, This bug is also present in 126.96.36.199.
New commit detected on ManageIQ/manageiq-content/hammer:
Author: tina <firstname.lastname@example.org>
AuthorDate: Fri May 10 14:10:43 2019 -0400
Commit: tina <email@example.com>
CommitDate: Fri May 10 14:10:43 2019 -0400
Merge pull request #529 from billfitzgerald0120/email_infra_template_complete2
Create Publish to Template email instance and method.
(cherry picked from commit b7bd3166ef3678d49b443298ff14d3e14c9bfb35)
content/automate/ManageIQ/Infrastructure/VM/Provisioning/StateMachines/VMProvision_Template.class/__class__.yaml | 2 +-
content/automate/ManageIQ/System/Notification/Email.class/__methods__/miq_provision_template_customize_body.rb | 69 +
content/automate/ManageIQ/System/Notification/Email.class/__methods__/miq_provision_template_customize_body.yaml | 12 +
content/automate/ManageIQ/System/Notification/Email.class/infrastructuremiqprovisiontemplatecomplete.yaml | 18 +
spec/content/automate/ManageIQ/System/Notification/Email.class/__methods__/miq_provision_template_customize_body_spec.rb | 108 +
5 files changed, 208 insertions(+), 1 deletion(-)
This error no longer exists in build 188.8.131.52
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.