Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    5k Posts
    rzrR
    As this is my first time installing these update candidates, Actually we moved first batch of packages that landed in testing to candidates repo, to avoid mix up in the second batch that just landed in testing repo. Since nothing new appeared in candidate you should probably already had them before, home this is clarifying what is actually happening Next yum update should just pull the latest stable versions? Not if you already have installed then from testing (or candidate) repo, because versions are same, it's only the distribution channel that change, no impact for testers.

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    henri9813H
    Hello, Thanks for all !

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    itservicesI
    Quick Update: Was looking good with commit cf26d. After the transfer completed the VDI of that particular VM was still in use, according to XO. So still failure on the job. Regards, Marc

  • Our hyperconverged storage solution

    47 Topics
    755 Posts
    poddingueP
    Thanks for coming back to close it out. That's useful to know. So I was plenty wrong, as it was the XOSTOR licensing backend rather than the repo side I guessed at; those -32000 errors really don't give much away. For anyone landing here later: sounds like -32000 on XOSTOR creation can come from either end, a licensing/entitlement issue that support sorts, or a host not reaching the package repo, so both are worth checking. @alcoralcor, did support get yours sorted too, or is yours still the repodata / repo-reachability one? Glad you're unblocked either way.

  • Non-English speakers

    35 Topics
    113 Posts
    olivierlambertO
    Ah excellente nouvelle Je passe le sujet en résolu !