https://github.com/ManageIQ/manageiq-automation_engine/pull/404
New commit detected on ManageIQ/manageiq-automation_engine/master: https://github.com/ManageIQ/manageiq-automation_engine/commit/79d8c15fe9623eac44b550dd68f7304b94b9ebec commit 79d8c15fe9623eac44b550dd68f7304b94b9ebec Author: Lucy Fu <lufu> AuthorDate: Wed Dec 18 14:07:40 2019 -0500 Commit: Lucy Fu <lufu> CommitDate: Wed Dec 18 14:07:40 2019 -0500 Add cc and bcc into send_email's inputs fields. https://bugzilla.redhat.com/show_bug.cgi?id=1783511 app/models/miq_ae_datastore.rb | 4 +- 1 file changed, 3 insertions(+), 1 deletion(-)
New commit detected on ManageIQ/manageiq-automation_engine/ivanchuk: https://github.com/ManageIQ/manageiq-automation_engine/commit/8863c6111377ccc8e65f6b31f762515ef4d180ec commit 8863c6111377ccc8e65f6b31f762515ef4d180ec Author: Greg McCullough <gmccullo> AuthorDate: Thu Dec 19 13:12:40 2019 +0000 Commit: Greg McCullough <gmccullo> CommitDate: Thu Dec 19 13:12:40 2019 +0000 Merge pull request #404 from lfu/cc_send_email_1783511 Add cc and bcc into builtin method send_email's inputs fields. (cherry picked from commit fac05cd1493ed14b694d12a925faad15dc54832c) https://bugzilla.redhat.com/show_bug.cgi?id=1783511 app/models/miq_ae_datastore.rb | 4 +- 1 file changed, 3 insertions(+), 1 deletion(-)
I started modifying the SMTP server in our tests for me to be able to find out the Cc and Bcc emails should work. Then I tried to run the send_email automate function and it seems it is working fine. But it seems same procedure worked in pre-fixed-in version. Therefore I am sure I didn't test this properly yet.
Please follow Steps to Reproduce in description. 1.Include CC within email config 2.Provision VM 3.Email failure, does not send to CC address
Bcc and CC got sent after configuring SMTP server and setting default_recipient and Bcc and Cc in Configuration/Email. I think the `To` of the email for the Approver should be filled with Approver address from the Configuration/Email when it is set. This does not happen. Only the default_recipient seems to be in use. I am filling a BZ for this.
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. https://access.redhat.com/errata/RHSA-2020:2480