Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Systemd does not get notified with READY state in etcd only nodes #1483

Closed
galal-hussein opened this issue Jul 29, 2021 · 2 comments
Closed
Assignees
Labels
kind/bug Something isn't working

Comments

@galal-hussein
Copy link
Contributor

Environmental Info:
RKE2 Version:

rke2 version v1.21.3-rc1+rke2r1 (cd52869.dirty)
go version go1.16.3

Node(s) CPU architecture, OS, and Version:
Linux ip-172-31-14-237 5.4.0-1045-aws #47-Ubuntu SMP Tue Apr 13 07:02:25 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Cluster Configuration:
1 node (etcd only node)

Describe the bug:
ETCD only node gets stuck with systemd since the recent changes of changing the notify for systemd in agent logic and not in server logic

Steps To Reproduce:
Install rke2 server with disabling api, controller, and scheduler
restart rke2

Expected behavior:
systemctl restart rke2-server restarts rke2 normally

Actual behavior:
systemctl restart command gets stuck

Additional context / logs:

@Jono-SUSE-Rancher
Copy link

Just putting a note here that this issue is currently a blocker for rancher/rancher#32362 on the Rancher side.

@rancher-max
Copy link
Member

This is fixed in v1.21.3-rc2+rke2r2. I am able to bring up individual role clusters in rancher:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants