@olivierlambert hi, I wasn't up to date I think. it works on the latest version, thanks!
Best posts made by VGerris
-
RE: Kubernetes cluster recipe not working
Latest posts made by VGerris
-
RE: Kubernetes cluster recipe not working
@olivierlambert hi, will do. Not sure what happened, I used the source compiled versiom first, where it was missing. Think I had to register to get the updates and that version worked. Thank you!
-
RE: Kubernetes cluster recipe not working
@olivierlambert hi, I wasn't up to date I think. it works on the latest version, thanks!
-
RE: Kubernetes cluster recipe not working
Sorry that I cannot answer your question, but on the topic, I am wondering if the recipe source is available anywhere public?
I am interested because I would like to create a recipe for OKD, the upstream version of RedHat OpenShift.That way I could probably help troubleshoot this kind of issue.
I also have not found any documentation and when trying to use static IP it is unclear to me with 3 nodes and 3 control planes what the VIP should be set too for example.I will soon start with a manual install, but I am waiting for hardware at the moment because of the memory and CPU requirements for OKD.
When I pull it off manually I would love to use the recipe based automation of it. -
RE: Cannot join cluster after node upgrade
I didn't find a solution, it looked like a change of the host that affected network. Rerunning from USB with latest beta kept showing an upgrade.
Network reset did not fix it and the machine was laggy, like when I tried to join from XO ( via settings ).I just did a complete reinstall, disabled HA on the NFS SR, joined pool and it worked and re-enabled HA.
Seems ok now, thanks for the help.
By the way, is there a way to join a node to the main pool in XO ?
Thanks! -
RE: Cannot join cluster after node upgrade
attached two more log files that were made around the time of upgrade.
It looks like the USB was mounted and that it disturbs the XAPI somehow?
I restarted that also and it shows ok. Gonnna keep looking :).2023-08-19T23_42_06.565Z - XO.log.txt 2023-08-19T23_41_59.940Z - XO.log.txt -
RE: Cannot join cluster after node upgrade
@Danp sure, recommended. but this is not per se a result of a quorum issue? I basically wonder if the host can be brought back into the cluster - the issue and errors are unclear to me, I do not understand what the problem is and how to prevent it.
3rd host is underway, but I see no reason why it would not happen then. I thought to keep the issue to trace bugs. I was unable to join the host successfully from XO by the way - but I guess I should address that in another post? I am looking for operational troubleshooting knowledge I suppose.Thank you, then let's see who else knows something.
-
RE: Cannot join cluster after node upgrade
[16:47 xcp-ng-2 ~]# xe task-list
The coordinator reports that it cannot talk back to the supporter on the supplied management IP address.
ip: 192.168.68.54That is on the command line.
-
RE: Cannot join cluster after node upgrade
@Danp Thank you for the quick reply!
I upgraded the master first yes.- with cluster I mean two machines with shared NFS storage (HA enabled) that are joint in the same pool
- in XO - the node shows offline. When trying to start it, it shows the host is offline, I will attach the XO log
I think the solution is probably just to reinstall the node, but I have seen this multiple times reported and wanted to understand it and learn how to fix it ideally.
It looks to me the XAPI is somehow not working and I do not understand the storage shown in XO - when I type mount on the host is does not show.[2023-08-20T14_41_50.142Z - XO.log](Invalid file type. Allowed types are: .png, .jpg, .bmp, .txt, .jpeg) 2023-08-20T14_41_50.142Z - XO.log.txt -
Cannot join cluster after node upgrade
I have a simple home lab of two machines. I have had several issues running a cluster, mostly because I could not join a node properly with XO.
So I joined it via the command line and it went fine.Then I tested upgrading : latest beta via USB. For the non master it showed an upgrade which I can. In the end it shows offline.
When trying to join it I get :Host Failed to Join the Pool
("'NoneType' object has no attribute 'xenapi'",)
In XO it shows offline, although I can connect to the console.
Strangely, the local storage for that node shows a full partition:
location: /dev/xapi/block ( local, unshared , 3,7 GB ).What could have gone wrong here?
Thanks -
RE: Cloud-init success
@dj423 thank you, that is really helpful!
I also found : https://cloudinit.readthedocs.io/en/latest/reference/examples.htmlSome things are mentioned here :
https://xcp-ng.org/forum/topic/7177/cloud-config-success
that you did not seem to need ? I will try it out.I saw the Kubernetes recipe uses cloud config files and I am interested to use it for an OKD installation.
I really like XCP-ng so far, cheers!