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

    stunnel sdn cert error when adding host to pool

    Scheduled Pinned Locked Moved Management
    10 Posts 4 Posters 478 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.
    • C Offline
      CJ
      last edited by

      I'm trying to add a host to an existing pool but I keep getting the following error whenever I do so.

      INTERNAL_ERROR(Sys_error("/etc/stunnel/certs/sdn-controller-ca.pem: No such file or directory"))

      I had previously created a private network on the pool but I've long since deleted it. One host had files in the certs directory but not the pool master. I've tried deleting the SDN plugin config and telling it to override the existing certs but nothing ever shows up in the certs folder and I continue to get this error.

      1 Reply Last reply Reply Quote 0
      • DanpD Offline
        Danp Pro Support Team
        last edited by

        Have you tried disabling the plugin?

        C 1 Reply Last reply Reply Quote 0
        • C Offline
          CJ @Danp
          last edited by

          @Danp Yes, that was one of the steps I tried. Is there anyone I need to do besides unchecking it in XO?

          DanpD 1 Reply Last reply Reply Quote 0
          • DanpD Offline
            Danp Pro Support Team @CJ
            last edited by

            @CJ IDK. You could try restarting XO Server to see if that makes a difference.

            C 1 Reply Last reply Reply Quote 0
            • C Offline
              CJ @Danp
              last edited by

              @Danp No change. Still the same error.

              1 Reply Last reply Reply Quote 0
              • M Offline
                morehousef
                last edited by

                I followed this guide to get my SDN up and running, it may help you out.

                https://www.saasycloud.com/solutions/blog/xen-orchestra-sdn-controller-plugin-error-when-enabling-community-build

                HTH

                C 1 Reply Last reply Reply Quote 0
                • C Offline
                  CJ @morehousef
                  last edited by

                  @morehousef I'll take a look, thanks. The part that's most frustrating is that I have the SDN plugin turned off and I have no SDN defined but XCP-ng still wants some certs.

                  1 Reply Last reply Reply Quote 0
                  • C Offline
                    CJ
                    last edited by

                    This ended up causing xen to get stuck in a boot loop during an 8.3 update. During the troubleshooting of that, we determined that XO had never correctly deleted the reference to the SDN cert.

                    If you run into this problem or something similar, run this comment.

                    xe certificate-list
                    

                    You should see one of the certificates show with the following.

                    name ( RO): sdn-controller-ca.pem
                    host ( RO): <not in database>
                    

                    If the certificate file doesn't exist, you will have to recreate it before you can delete the cert reference.

                    touch /etc/stunnel/certs/sdn-controller-ca.pem
                    xe pool-certificate-uninstall name=sdn-controller-ca.pem
                    

                    This should fix the problem.

                    1 Reply Last reply Reply Quote 2
                    • olivierlambertO Offline
                      olivierlambert Vates 🪐 Co-Founder CEO
                      last edited by

                      @yann & @stormi for further feedback

                      C 1 Reply Last reply Reply Quote 0
                      • C Offline
                        CJ @olivierlambert
                        last edited by

                        @olivierlambert @stormi is the one who helped me find and fix the issue. I just wanted to update my old thread in case someone else happened across the problem until it gets fixed in XO.

                        1 Reply Last reply Reply Quote 2
                        • First post
                          Last post