xcp-ng / xcp

Entry point for issues and wiki. Also contains some scripts and sources.
https://xcp-ng.org
1.32k stars 74 forks source link

HTTPS SSL Key is missing from new/clean install of XCP-ng v8 #275

Closed LoVoltage closed 3 years ago

LoVoltage commented 5 years ago

Issue: After installing XCP-ng v8 new or clean, no HTTPS SSL cert is present

Screenshot from 2019-09-22 17-21-37

Confirming the Issue:

Screenshot from 2019-09-22 17-47-37

XCP-ng Center Errors: Windows 7 and Server 2008 R2

Windows 10

Screenshot from 2019-09-20 15-58-09

Workaround: Installed XCP-ng 7.6, applied latest updates, then upgraded to v8 and applied latest updates. HTTPS SSL is present on the XCP-ng server and no errors when using XCP-ng Center.

XCP-ng Server Installation:

Troubleshooting:

It seems the issue is with XCP-ng v8 when installing new or clean

agador commented 5 years ago

Did you update to the latest XCP-ng Center?

Did you disable the SSL Checks for your new XCP-ng 8 server? (I had a similar issue with XOA until I turned off SSL Certificate checking).

Just a couple of quick thoughts.

Jim

olivierlambert commented 5 years ago

Please open the issue in XCP-ng Center repo :wink:

https://github.com/xcp-ng/xenadmin/

LoVoltage commented 5 years ago

Did you update to the latest XCP-ng Center?

Did you disable the SSL Checks for your new XCP-ng 8 server? (I had a similar issue with XOA until I turned off SSL Certificate checking).

Just a couple of quick thoughts.

Jim

Yes, we updated to the latest version of XCP-ng Center.

Our troubleshooting began when with 4 XCP-ng servers

We believe the issue is not with XCP-ng Center but with XCP-ng itself, specifically tasks related to installation. The workaround of upgrading from v7.6 to v8 of an existing installation seems to support our theory.

olivierlambert commented 5 years ago

Does it work with Xen Orchestra?

LoVoltage commented 5 years ago

Does it work with Xen Orchestra?

Theses systems belong to clients that do not use XO. As a result we did not test with XO. We suspect the issue lies in XCP-ng and not Center and therefore assume XO would have issues connecting.

If time allows, we will try to test with XO.

olivierlambert commented 5 years ago

Please try with XO, which is the most (and only professionally) supported client for XCP-ng.

LoVoltage commented 5 years ago

Issue opened at https://github.com/xcp-ng/xenadmin/issues/175

LoVoltage commented 5 years ago

Confirmed this does not work from XOCE or XOA

LoVoltage commented 5 years ago

@olivierlambert the HTTPS SSL key is missing on the XCP server. Updated this post to reflect the issue. Thanks for looking into this.

Q: During install, what is the relationship between the generation of the SSL key generation and local machine time/NTP?

stormi commented 5 years ago

Can you try to find what happened in the installation logs? I don't know how to reproduce locally.

Location: /var/log/installer/

LoVoltage commented 5 years ago

@stormi Will drop the logs when workload allows. Any particular phrases or areas in the log that we should look for? We can parse for the usual stuff, but if we can focus the process, we could get meaningful info out faster.

stormi commented 5 years ago

I don't know, since it's the first time such an issue is reported. The most interesting (and bigger) file is /var/log/installer/install-log. It's got almost everything in it. I can send you my own from a nested test server if you want to compare.

ghost commented 4 years ago

It is not related to this issue but when I searched for my issue, I landed here. So I am linking this thread for people who will be in the same case as me when upgrading from 8.0 to 8.1 via yum (the ISO will be patched by the XCP-ng team soonish as I understood) https://xcp-ng.org/forum/topic/2797/xcp-ng-8-1-clean-install-missing-stunnel4/62

stormi commented 4 years ago

Hi @LoVoltage. Looks like you didn't find time for sharing logs, and I didn't give much attention to this issue either. If you can try with XCP-ng 8.1's installer, I'd like to know if the issue still occurs for you.

stormi commented 3 years ago

Closing due to the absence of needed feedback (logs), and since XCP-ng 8.0 is now EOL. Feel free to reopen with more elements from a supported release of XCP-ng.