Oh wow, IDK how or why. But if it works, then it's great!

@umbradark Nope but we'll be happy to do so.

Thanks @abudef !

FINALLY. Thanks Microsoft, and many thanks to you, @dinhngtu !

Excellent news! Thanks for the feedback

@florent what's the duration of the HTTP timeout on XO side in that case?

I don't think so, adding @Team-XAPI-Network in the loop

@Pilow Because the UUID of the object is preserved. Restoring a backup is different than rolling back a snap.

So you are trying to restore a VM that has been backup: when you do that, it's a brand new VM. It's an expected behavior. It doesn't mean it's a great one, but this is how it works now

Hi,

Yes it was. You need to be sure that your SAML provider used the signed SAML assertion.

Examples in Keycloak then Azure respectively:

ACLs and VM creators are XO only objects, not stored in XAPI.

Hi,

As the message said, please reach out to us, you can use the contact form https://vates.tech/contact

We'll be happy to discuss and assist in your evaluation

FYI, this NIC worked until recently. We suspect new hardware revision and/or a new firmware in it, that is causing a bug with the current XCP-ng driver.

Sadly, Backblaze is often having issues on S3 (timeout, not reliable etc). We are updating our doc to give a "tiering" support.

It is persistent but people usually want to modify it manually in some cases Thanks @andriy.sultanov !

Edited your post to use the right Markdown syntax, otherwise it's a pain to read

Hi,

To start, it's good to read: https://docs.vates.tech/security/

Especially https://docs.vates.tech/security/#contact--disclosure

Then, I can answer here directly: we are not affected since Redis is only listening locally, therefore it's not exposed outside XO. There's nothing interesting to do with that CVE, because in order to use it, you already must be a privileged user.

100% agree, "stacked" tags are great. @lsouai-vates can you pass the word because I think XO 6 team isn't aware of those "stacked" tags in XO 5

I never remember the exact option myself, we should document it @thomas-dkmt

In the meantime, @Team-XAPI-Network can give the answer

Thanks for your feedback, adding @lsouai-vates in the loop to tell XO team something might have been broken on master.