Awesome, thanks. Just knowing that a > 18.04 deployment should work as
expected is a good start. I'll double check paths, permissions, logs and
the curl test in the other reply and report back.
On 4/1/25 12:57, Jarrod Johnson via xCAT-user wrote:
The 'password not accepted' can happen if you reboot a deployment and
retry without doing a 'nodedeploy' again. In confluent you have to
explicitly say you want to deploy, as there's a security mechanism
that locks down after a node API token is claimed.
[root@r3u20 ~]# nodedeploy r3u24
r3u24: pending: ubuntu-22.04.5-x86_64-default (node authentication armed)
[root@r3u20 ~]#
Note 'node authentication armed'. This means it is configured to allow
a single more weakly authenticated request for a node token.
At some point during an install attempt, you get to:
[root@r3u20 ~]# nodedeploy r3u24
r3u24: pending: ubuntu-22.04.5-x86_64-default
[root@r3u20 ~]#
In this case, a new attempt must be accompanied by another nodedeploy,
a reboot without completing deployment will discard the node token
that was granted.
However, I assume at least the first attempt did fail for other
reasons and may need to know more about that. I just did a deployment
myself of 22.04.5 without issue and had no issues, so at least in
theory it should be workable, but will probably need to see some files
when you get to a manual interaciton point.
Files like /conf/param.conf, files in /custom-installation/confluent/..
------------------------------------------------------------------------
*From:* Brian Joiner <martinitime1...@gmail.com>
*Sent:* Tuesday, April 1, 2025 12:00 PM
*To:* xcat-user@lists.sourceforge.net <xcat-user@lists.sourceforge.net>
*Subject:* [External] [xcat-user] Confluent: Anyone get Ubuntu to deploy?
I have attempted to deploy an Ubuntu 22.04 server via Confluent, and
I've run into all kinds of issues. Either the process dies after trying
to mount the cd, I get the option to enter an emergency command prompt,
or I get sent into a non-interactive setup screen where I'm prompted to
enter account/network/disk info by hand. I've had the same experience
in my home lab and my office Confluent instance.
However, if I deploy Rocky 9.x to the same node (with no attribute
changes) it deploys as expected. Has anyone gotten Ubuntu server to
deploy without intervention? Have I missed some kind of setup step for
Ubuntu based installs?
My confluent server has all updated packages, and I didn't see anything
of interest in /var/log/confluent
Attached is one of the fail screen shots if that helps.
Thanks,
Brian Joiner
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
