Start a Conversation

Unsolved

Closed

F

1 Rookie

 • 

48 Posts

760

April 13th, 2023 01:00

smtpmail is broken since 19.8.0.1

Dear Community,

since we updated from 19.7. to 19.8.0.1, the smtpmail function within actions notification is broken.
I would ask someone to confirm, that this happens for you also.

Issue:
When I set a notification "on failure" in a action or workflow and define the command smtpmail with parameters, it will reset as soon as I configure/save the action.

2023-04-13 09_36_09-Window.jpg

Setting is also visible on overview page before saving:

2023-04-13 09_36_58-Window.jpg

But after saving, it is set back to empty "smtpmail":

2023-04-13 09_35_02-Window.jpg

This applies on every policy we modify. No matter if you set it on the policy itself, workflow or action.
I can confirm that its not a visual issue. We receive no mail anymore.

I tried different ways of smtpmail command - no success.

Existing policies, which will not be modified, keep the correct settings and send mail.
Any modification of policy will clear the smtpmail command.

Any clue?

 

April 17th, 2023 04:00

What can you see and do from CLI, updating the notification? Does that stick? By going into nsradmin and updating "Notification action" to the command required for the type: NSR Protection Policy in question?

If indeed that is a nw19.8.0.1 issue, it only further confirms one might never want to go latest and greatest, regardless if Dell calls it the Target Code?

We remain rather a bit defense not going beyond latest-1, so will be going from nw19.5.0.6 to nw19.7.0.3 or up next, but will leave nw19.8 for what it is at the moment until at least nw19.9 is released.

You might miss out a bit on the newest features but then again the newest issues (from secretly added new features and "improvements") take precedence often alas...

1 Rookie

 • 

48 Posts

April 18th, 2023 02:00

Thanks for reply.

I tried to change the values with nsradmin:

nsradmin> print type: NSR Protection Policy action; policy name: Phys; workflow name: daten_1y; name: backup

         Notification action: smtpmail;
     Notification execute on: failure;

nsradmin> update Notification action: smtpmail -h 10.1.1.1 -s "NetWorker" example@gmail.com
         Notification action: \
smtpmail -h 10.1.1.1 -s NetWorker example@gmail.com;
Update? y
189037:nsradmin: Action 'Phys/daten_1y/backup' is updated successfully.

nsradmin> print type: NSR Protection Policy action; policy name: Phys; workflow name: daten_1y; name: backup

         Notification action: smtpmail;
     Notification execute on: failure;

Unfortunately, stays empty

I don't know if there is a way to report this to developer directly.

April 18th, 2023 12:00


I don't know if there is a way to report this to developer directly.

By creating a Service Request through  the proper channels (online or by phone referencing the softwareID of for example the Networker capacity license being used), assuming you have a Dell support contract?

Seems a bug. Don't have a test lab running nw19.8 yet to validate this myself however...

1 Rookie

 • 

48 Posts

April 27th, 2023 00:00

This Bug was just confirmed by Dell Technical Support.
Bug-ID: 338127

It will be fixed with version 19.8.0.2 (not public yet).

May 4th, 2023 13:00

Very neat of Dell always to remind us again and again not to go to the latest and greatest - even though 19.8 is the target code - until at least multiple hot-fixes have been released.

So I assume we won't be going past nw19.7 anytime soon...

Would also help if Dell would back-port security vulnerabilities from CVE's into somewhat lower, but still supported NW versions, at least nw19.5, 19.6 and 19.7 instead of the latest and greatest nw19.8.

Now alas it is choosing between the latest and greatest, not knowing which bugs&features they might hold, versus not having certain security issues resolved (for CVE's that are at times multiple years old already) but having a fairly stable NW version. We pretty much always choose for slightly older, but stable... but at times it tough.

BTW can't find anything (yet?) about the issue in the KB wrg to bug-id 338127.

No Events found!

Top