XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Cannot import ISO file

    Scheduled Pinned Locked Moved Solved Management
    13 Posts 5 Posters 2.4k Views 3 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • stormiS Offline
      stormi Vates 🪐 XCP-ng Team
      last edited by

      Regarding the first disk import error, all I can say from the messages is that there's a network error. What are the logs for this specific error?

      1 Reply Last reply Reply Quote 0
      • stormiS stormi moved this topic from Storage on
      • DanpD Offline
        Danp Pro Support Team
        last edited by

        There have been several recent threads regarding issues related to self-signed certificates. This is likely caused by a recent commit to the XO source code. You could try reverting to an earlier commit to see if the issue goes away.

        A 1 Reply Last reply Reply Quote 1
        • A Offline
          abudef @Danp
          last edited by

          @Danp Yeah, that's exactly it! After downgrading to an older commit the import works just fine! Just like here: https://xcp-ng.org/forum/topic/8618/restoring-from-backup-error-self-signed-certificate/23

          D 1 Reply Last reply Reply Quote 1
          • D Offline
            DustinB @abudef
            last edited by

            @abudef said in Cannot import ISO file:

            @Danp Yeah, that's exactly it! After downgrading to an older commit the import works just fine! Just like here: https://xcp-ng.org/forum/topic/8618/restoring-from-backup-error-self-signed-certificate/23

            What version number were you at before (while it wasn't working) and when you downgraded what version were you at?

            A 1 Reply Last reply Reply Quote 0
            • A Offline
              abudef @DustinB
              last edited by

              @DustinB said in Cannot import ISO file:

              What version number were you at before (while it wasn't working) and when you downgraded what version were you at?

              Now I tried again and it still doesn't work in commit 1b5157e, but it works in 0ccfd4b. I didn't check which specific commit introduced the problem with the self signed certificate.

              1 Reply Last reply Reply Quote 1
              • Tristis OrisT Offline
                Tristis Oris Top contributor
                last edited by Tristis Oris

                lets talk with direct examples.
                https://download.rockylinux.org/pub/rocky/9/isos/x86_64/Rocky-9.3-x86_64-minimal.iso
                dcab2d2c-833c-4e46-a0cb-216b88b0691f-изображение.png

                and it stuck forever 90d34310-9846-4697-a102-391e955a336c-изображение.png

                not a self signed, import works a few weeks ago. Looks like yet one issue after last bad patch.

                A 1 Reply Last reply Reply Quote 1
                • A Offline
                  abudef @Tristis Oris
                  last edited by

                  @Tristis-Oris said in Cannot import ISO file:

                  not a self signed

                  I think the problem with the self signed certificate is the certificate on the XO side, not on the server side from where you download the ISO (❓).

                  Tristis OrisT 1 Reply Last reply Reply Quote 0
                  • Tristis OrisT Offline
                    Tristis Oris Top contributor @abudef
                    last edited by

                    @abudef my XO run http only, no certs.

                    A 1 Reply Last reply Reply Quote 0
                    • A Offline
                      abudef @Tristis Oris
                      last edited by

                      @Tristis-Oris said in Cannot import ISO file:

                      my XO run http only, no certs.

                      Sorry, I meant to write XCP-ng server; the IP address in the error stack above belongs to the hypervisor.

                      Tristis OrisT 1 Reply Last reply Reply Quote 0
                      • Tristis OrisT Offline
                        Tristis Oris Top contributor @abudef
                        last edited by

                        @abudef ah i see, you right.

                        1 Reply Last reply Reply Quote 0
                        • A Offline
                          abudef
                          last edited by

                          Solved by 583c728

                          1 Reply Last reply Reply Quote 0
                          • olivierlambertO olivierlambert marked this topic as a question on
                          • olivierlambertO olivierlambert has marked this topic as solved on

                          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                          With your input, this post could be even better 💗

                          Register Login
                          • First post
                            Last post