https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# elemental
a
This message was deleted.
w
Hey @creamy-finland-31714! What is the issue you are seeing? That log might just indicate that the resource is not ready yet and will be retried..
c
when trying to create a cluster against an elemental node , it stays stuck on 'waiting for agent to register'
the machine itself shows up in the inventory though.
w
Hmm, is the 
elemental-system-agent
unit active? and 
rancher-system-agent
inactive?
c
i'm rebuliding it now - will get back to u in 5 min
👍 1
@witty-table-40840 i dont see a rancher-system-agent on the system.
Copy code
rancher-27557:~ # systemctl | grep agent
  elemental-system-agent.service                                                                   loaded active running   Elemental System Agent
rancher-27557:~ #
w
Hmm, can you post the logs from elemental-system-agent? All it does is install rancher-system-agent.
c
Copy code
rancher-27557:~ # journalctl -u elemental-system-agent.service
Oct 11 08:34:03 rancher-27557 systemd[1]: Started Elemental System Agent.
Oct 11 08:34:03 rancher-27557 elemental-system-agent[1614]: time="2023-10-11T08:34:03Z" level=info msg="Rancher System Agent version dev (HEAD) is starting"
Oct 11 08:34:03 rancher-27557 elemental-system-agent[1614]: time="2023-10-11T08:34:03Z" level=info msg="Using directory /var/lib/elemental/agent/work for work"
Oct 11 08:34:03 rancher-27557 elemental-system-agent[1614]: time="2023-10-11T08:34:03Z" level=info msg="Starting remote watch of plans"
Oct 11 08:34:03 rancher-27557 elemental-system-agent[1614]: time="2023-10-11T08:34:03Z" level=info msg="Starting local watch of plans in /var/lib/elemental/agent/plans"
Oct 11 08:34:03 rancher-27557 elemental-system-agent[1614]: E1011 08:34:03.621581    1614 memcache.go:206] couldn't get resource list for <http://management.cattle.io/v3|management.cattle.io/v3>:
Oct 11 08:34:03 rancher-27557 elemental-system-agent[1614]: time="2023-10-11T08:34:03Z" level=info msg="Starting /v1, Kind=Secret controller"
Oct 11 08:34:03 rancher-27557 elemental-system-agent[1614]: time="2023-10-11T08:34:03Z" level=info msg="Detected first start, force-applying one-time instruction set"
Oct 11 08:34:03 rancher-27557 elemental-system-agent[1614]: time="2023-10-11T08:34:03Z" level=info msg="[Applyinator] Applying one-time instructions for plan with checksum 44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a"
rancher-27557:~
Very short log file.
When i try to create a k3s cluster on the node it gets stuck here :
I do see this one thign that stands out :
w
aha, nice find! what versions of rancher and elemental are you using?
c
rancher 2.7.8
elemental operator 1.2.4
w
I'm getting the same behavior with 2.7.8.. worked okay with 2.7.6
c
ah..
w
Could you register an issue on github.com/rancher/elemental-operator and I will start looking at a fix!
c
should i try and upgrade to 1.3.4 elemental operator first ?
I see that is the latest according to github
w
Sure!
c
ok let me try it today, and get back.
👍 1
hopefully get some time.
w
Nice, I will also give it a spin!
c
yes 1.3.4 elemental oeprator works.
looks liek that was the issue.
w
phew! good catch!
Open in Slack
PreviousNext
Powered by