Agreed, such a simple change to fix this would require very little regression testing from Dell thus should be easy to do quickly. It could even be a patch to the existing version without any new features.
On 14/12/2016, 22:27, "[email protected] on behalf of Kilian Cavalotti" <[email protected] on behalf of [email protected]> wrote: > From: Dominik Borkowski [mailto:[email protected]] > What’s the ETA on the new release? This issue is causing a problem for us, > where TSM/spectrum scale operation center is now generating alarms for the > systems with this failed mount, and consequently we can’t tell what backups > failed due to this /tmpSECUPD, or due to other grave issues. On Mon, Nov 14, 2016 at 10:59 PM, <[email protected]> wrote: > The fix will be released in March 2017. This must be a joke, right? This issue has been reported by dozens of users since early November, it's yet another illustration of the very very very poor quality of this piece of software, and now you're telling us you have a fix that you will sit on for 4 months? Is this your idea of quality assurance and user support? It's definitely not mine. So please provide a fix much sooner. Thanks, -- Kilian _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge
