No, this is still in the same state.
As best as I can tell DNS resolution is working, but it’s possible I’m
mistaken. No post scripts run so not much should be different once it boots a
second time (and I run a "nodeset boot” before it starts a 2nd install). It can
ping the xcat server’s hostname fine once it comes back up and I can examine
the node. I haven’t had much more time to work on this, but I do plan to keep
chipping away at it as time allows.
This is the xcat error I see for reference:
Oct 21 16:35:15 oss01 systemd: Starting LSB: xCATpost...
Oct 21 16:35:15 oss01 xcatpostinit1: /opt/xcat/xcatinstallpost: line 9:
/xcatpost/xcatlib.sh: No such file or directory
Oct 21 16:35:15 oss01 systemd: xcatpostinit1.service: control process exited,
code=exited status=1
Oct 21 16:35:15 oss01 systemd: Failed to start LSB: xCATpost.
Oct 21 16:35:15 oss01 systemd: Unit xcatpostinit1.service entered failed state.
Thanks,
-Nathan
From: Josh Nielsen <[email protected]<mailto:[email protected]>>
Date: Monday, November 23, 2015 at 3:43 PM
To: xCAT Users Mailing list
<[email protected]<mailto:[email protected]>>,
Nathan Heald <[email protected]<mailto:[email protected]>>
Cc: "[email protected]<mailto:[email protected]>"
<[email protected]<mailto:[email protected]>>
Subject: Re: [xcat-user] xCAT 2.9.1, problem kickstarting centos7
And did you ever figure out your problem Nathan?
-Josh
On Mon, Nov 23, 2015 at 2:34 PM, Josh Nielsen
<[email protected]<mailto:[email protected]>> wrote:
I was going to post a new thread about Centos 7 but thought I might piggy back
on this one since it is a similar topic. I have xCAT 2.8.3 currently and it
sounds like from the thread here that upgrading to 2.10 is part of the solution
for deploying Centos 7.1. Currently the issue I'm having is that during a PXE
boot it fetches the correct centos 7.1 image and begins trying to deploy but
after it shows "Mounted Configuration File System" and "Started Show Plymouth
Boot Screen" I get a message like this: "dracut-initqueue: Warning: Could not
boot" and hangs there.
This isn't a very explicit error, as to what caused it, and I didn't learn much
from removing "quiet" from the PXE kernel boot parameters. I also can't get the
ctrl+alt+F keys to work, at least in a VM, for showing different terminals like
you could in Centos 6 (which was very helpful for debugging).
Is this most likely because the kickstart file itself is not formatted
correctly (I'm reusing my Centos 6.4 kickstart - until I figure out how Centos
7.1 differs), or perhaps that the kickstart is not being properly fetched from
the gpxe configuration in /tftpboot/xcat/xnba/nodes? Currently the gpxe boot
configuration for the node I'm trying to deploy Centos7.1 to looks like this:
#!gpxe
#install centos7.1-x86_64-compute
imgfetch -n kernel
http://${next-server}/tftpboot/xcat/osimage/centos7.1-x86_64-install-compute/vmlinuz
imgload kernel
imgargs kernel repo=http://10.20.0.101:80/install/centos7.1/x86_64
ks=http://10.20.0.101:80/install/autoinst/node0067c ksdevice=bootif cmdline
console=tty0 console=ttyS0,115200n8r BOOTIF=01-${netX/machyp}
imgfetch
http://${next-server}/tftpboot/xcat/osimage/centos7.1-x86_64-install-compute/initrd.img
imgexec kernel
I manually changed ksdevice to "bootif" just to make sure it was using the
right interface (it was set to eth0 but Centos 7.1 got rid of "eth" for "em"
didn't it?). Nonetheless, I think my kickstart is being sucessfully fetched,
because I changed the disk formatting commands in the kickstart and when I
removed "quiet" from the boot I saw errors related to disk
formatting/partitioning. So I'm partial to thinking that the old Centos 6.4
kickstart configuration is not 100% compatible with Centos 7.1, but I want to
double check to see what xCAT 2.10 bring to the table that might be necessary
for Centos 7.1 deployment. Comments or thoughts?
Regards,
Josh
On Fri, Oct 23, 2015 at 1:44 PM, Russell Auld
<[email protected]<mailto:[email protected]>> wrote:
Looks like xcatdsklspost does get called even for stateful installs. Look at
the script header.
Usually in cases like this, the issue is that the node being imaged can't
resolve the name of the master node. Make sure your dns is working properly.
On Oct 23, 2015 12:52 PM, "Heald, Nathan T."
<[email protected]<mailto:[email protected]>> wrote:
>
> To follow up:
>
> I have resolved the pxe problem by upgrading further to xcat 2.10. Now it
> sets kickstart parameters that centos7 responds to.
>
> However I have a new problem, the rinstall is now looping. I’ve gotten as far
> as seeing that "/xcatpost” is never created on my stateful install. The xcat
> debugging page suggests networking problems as the first thing to check. So
> far I’ve not found anything on that front. I can’t find what specifically
> creates /xcatpost during the install. I see that /opt/xcat was created which
> contains the scripts xcatdsklspost and xcatinstallpost. Only the script
> xcatdsklspost has the line “mkdir /$xcatpost”, I would not expect this script
> to be executed since this is not a diskless install. “xcatinstallpost” starts
> trying to download stuff to /xcatpost but there’s nothing in this script that
> creates this directory.
>
> Suggestions?
>
> Thanks,
> -Nathan
>
>
> From: Nathan Heald <[email protected]<mailto:[email protected]>>
> Reply-To:
> "[email protected]<mailto:[email protected]>"
> <[email protected]<mailto:[email protected]>>
> Date: Tuesday, October 13, 2015 at 5:30 PM
> To: "[email protected]<mailto:[email protected]>"
> <[email protected]<mailto:[email protected]>>
> Subject: [xcat-user] xCAT 2.9.1, problem kickstarting centos7
>
> Greetings,
>
> I’m trying to get a working statefull install of centos7 on generic hardware.
> This management node started out with xCAT 2.8.4, I have upgraded it to 2.9.1
> to try to get this working. Of course the parameters of the RH/centos 7
> kickstart have changed necessitating the upgrade. I found this url indicating
> that as of 2.9 xcat should know know how to handle RH/centos7:
> http://sourceforge.net/p/xcat/bugs/4318/
>
> However, I’m not able to trick xcat into setting up my pxe file correctly
> when I run the nodeset for the host I want to install. I get this in my
> /tftpboot/pxelinux.cfg/host01 file:
> …
> APPEND initrd=xcat/osimage/centos7-x86_64-install-compute/initrd.img quiet
> repo=http://192.168.0.1:80/install/centos7/x86_64
> ks=http://192.168.0.1:80/install/autoinst/host01 ksdevice=2C:44:FD:00:00:00
> …
>
> But I’m expecting something more like this which should be supported by
> centos7:
> …
> APPEND initrd=xcat/osimage/centos7-x86_64-install-compute/initrd.img quiet
> inst.repo=http://192.168.0.1:80/install/centos7/x86_64
> ks=http://192.168.0.1:80/install/autoinst/host01 ksdevice=2C:44:FD:00:00:00
> …
>
> It looks like the updated xCAT code is trying to match “7.0" in $os for the
> host definition. It appears that $os was set to “centos7” at some point when
> I either ran copycds or ran a nodeset. I’ve tried a few different iterations
> to see if I can tickle this into working to no avail.
>
> Any suggestions would be appreciated.
>
> Thanks,
> -Nathan
>
------------------------------------------------------------------------------
_______________________________________________
xCAT-user mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
