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

post.xcat.ng doesn't work on centos8.4 diskful installation. #7467

Open
ibmxianliqi opened this issue Aug 12, 2024 · 5 comments
Open

post.xcat.ng doesn't work on centos8.4 diskful installation. #7467

ibmxianliqi opened this issue Aug 12, 2024 · 5 comments

Comments

@ibmxianliqi
Copy link

ibmxianliqi commented Aug 12, 2024

When I want to provision centos8.4 diskful node, I used the post.xcat.ng in the compute.centos8.tmpl for node kickstart template as below:

%pre
{
echo "Running Kickstart Pre-Installation script..."
#INCLUDE:#ENV:XCATROOT#/share/xcat/install/scripts/pre.rhels8#
} &>>/tmp/pre-install.log

%end

%post
mkdir -p /var/log/xcat/
{
cat >> /var/log/xcat/xcat.log << "EOF"
%include /tmp/pre-install.log
EOF
echo "Running Kickstart Post-Installation script..."
#INCLUDE:#ENV:XCATROOT#/share/xcat/install/scripts/post.xcat.ng#
#INCLUDE:#ENV:XCATROOT#/share/xcat/install/scripts/post.rhels8#
} &>>/var/log/xcat/xcat.log

it will result in the node is always installing forever, because there is no update node status action triggered from xcat.post.ng script.

is there someone to know how to deal with this issue?

@Obihoernchen
Copy link
Member

Is your management node firewall disabled?

@ibmxianliqi
Copy link
Author

Is your management node firewall disabled?

yes, MN's firewall was disabled. And I found the post install section's code was not executed during node installation, as first step from post.xcat.ng goes to download /install/postscripts to node's /xcatpost through curl, but it doesn't enter into the curl download code logic. So node's status is always installing and there is no chance to be updated by post section code.

any idea or suggestion to help to resolve this issue?

@samveen
Copy link
Member

samveen commented Aug 22, 2024

An instantiated kickstart file containing the node's name will be generated from this template and stored in the /tftpboot or /install folder. Please check it;'s contents to see whether the generated kickstart contains the expected contents.

@ibmxianliqi
Copy link
Author

An instantiated kickstart file containing the node's name will be generated from this template and stored in the /tftpboot or /install folder. Please check it;'s contents to see whether the generated kickstart contains the expected contents.

yes, I'm sure the generated script under the /install/autoinstall directory contains the post section code lines, but the code's post install related code line is not executed during diskful installation.

@ibmxianliqi
Copy link
Author

is there any progress about this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants