Forum wide moderators
@Bryanvh No problem 
The issue you encountered wasn't very clear. Therefore, I've proposed a change to the XAPI to make the error more explicit (this will likely be implemented in future XAPI releases).
So instead of SSL Certification failure the message will be: POOL_JOINING_MASTER_CERTIFICATE_NOT_IN_POOL_BUNDLE.
Thank you very much for your patience and for bringing this issue to our attention.
References:
https://github.com/xapi-project/xen-api/pull/7112
Thank you again for feedback we will try to address reported issues on next batch (to come soon).
Note that some issues are not related to this specific update batch, but might have been introduced on previous ones (TBC).
Not knowing myself what it meant, I asked Philippe: it's about the nslookup issue. And potentially the issue reported by @ph7 but it's not clear to me yet if there was a problem with XCP-ng or Xen Orchestra.
Anyway, basically this means that there's no known issue caused by this batch of updates, and that we'll keep addressing any relevant issue in the next updates if necessary, as usual.
@Andrew We'll publish a fix for bind-utils, indeed, even if it's not part of the officially supported additional packages for XCP-ng, as it can be useful and we don't have strong reasons not to fix it.
Regarding other packages affected by the openssl update, @rzr handled many of them as part of the OpenSSL update back then already, so now we'll mostly rely on reports such as yours in case we missed something which is actually used by the user community.
We are back on 0.21.0 (might need a Ctrl+Shift+R). We had issues with this month's version (0.22.0) so we'll have to postpone it to next week. Apologies for the confusion around 0.19.0.
