I tried looking at kickstart documentation and confirmed that the user parameter in kickstart body is actually an optional parameter which means, if you don't provide it, kickstart body won't ask you to enter or won't stop.
In fact, the option to add a user isn't grayed out during kickstart in GUI if you don't have user param in kickstart. In case someone has access to the system physically, one can add any user and even make that user a part of the wheel group, so many actually create a test user with --lock option so that nobody could utilize adding a user during kickstart.
The best way to deal with this is to create a text file in %pre and utilize that file using the%include option in the kickstart body.
Thanks,
Pushpendra Chavan.
On Wed, Jun 30, 2021 at 8:19 AM Pushpendra Chavan <chavanpushpendra@xxxxxxxxx> wrote:
Hi,You can do it as well.Just create that file in %pre section and then instead of using it in %post, use the following line in ks%include /path/to/filePlease make sure you have the file /path/to/file written in appropriate Kickstart format.%pre section can be utilized to properly format it with user entered username and password.Regards,Pushpendra Chavan.On Tue, Jun 29, 2021, 7:27 PM Andrew Simpson <simpsonar77@xxxxxxxxx> wrote:Thank you for that. I have done something similar, but all in the %post. I was hoping that there was a way to force the user to use the UI to enter username and password, though.I suppose moving this to %pre would then allow me to "set" the user account in the main kickstart section using 'user ---name .....'_______________________________________________On Tue, Jun 29, 2021 at 1:15 AM Pushpendra Chavan <chavanpushpendra@xxxxxxxxx> wrote:Hi,You can write a %pre script which would force ask user to enter username and password or any other information and then write that information down in a /tmp/somefile.txtThen continue the installation, and in %post section, first %post would be with --nochroot where it will copy that text file to /mnt/sysimage/somelocationAnd then from that location, it would utilize that information and act accordingly.You can write the %pre section as follows. I have tested this on RHEL7%pre exec < /dev/tty7 > /dev/tty7 chvt 7 echo "Enter Manual Information in given format" read MYINFO echo $MYINFO >/tmp/test chvt 1%endKICKSTART BODY%post --nochrootmv /tmp/test /mnt/sysimage/tmp/test%end%post# Use /tmp/test to perform %post actions%endThanks,Pushpendra Chavan._______________________________________________On Tue, Jun 29, 2021 at 1:39 AM Andrew Simpson <simpsonar77@xxxxxxxxx> wrote:Is it possible to require/force a user to enter in their user account information before the install gets to the %post section via the graphical installer? I need everything else to be automated, except this step, and need to modify that user's groups in the "post" section. It appears that if nothing is entered via the GUI during install, that the install will complete without it. (root is setup as part of the ks)._______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/kickstart-list
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/kickstart-list
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/kickstart-list
_______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/kickstart-list
