Thanks for providing these docs and tutorials. Much appreciated!
I followed through the instructions starting from the top. For the most part, all was clear and easy to work through. Things began to fall apart though once I got to the Build x86_64 Backend(s) section. That's where I left off and was not successfully able to continue. It seemed like the the main issue was that the PXE Boot files would not install correctly. I'm new to CoreOS and RPM syntax, but the past few years using Ubuntu are pretty similar which allowed me to try a few different install variations. I couldn't get any to stick that allowed me to proceed to the next step of copying the image files to the /tftpboot/pxelinux/ directory. These three were unable to be ran with a response of the source files not existing for the first two nor the entire /syslinux directory:
# cp /opt/stack/images/vmlinuz-4.0_20170414_c4aff2a-7.x-x86_64 /tftpboot/pxelinux/
# cp /opt/stack/images/initrd.img-4.0_20170414_c4aff2a-7.x-x86_64 /tftpboot/pxelinux/
# cp -r /usr/share/syslinux/* /tftpboot/pxelinux/
I do have a successful frontend machine up and running in a VM with a few backend hosts in VMs as well. Those are in Hyper-V on a Windows Server 2016 DC x86 system. That install and configuration was smooth and straight forward. To try and get past the above three steps, I found that both image files and the /syslinux directory were installed in the same locations that were suppose to be present on the Pi's drive. So, I copied them from that frontend machine to the Pi's Micro SD card.
I was not able to proceed with the following step either which is where I gave up for now. After copy/paste this step, I continued to get argument errors that didn't make sense at first until I found the host information was now missing.
[root@stacki ~]# stack add bootaction stacki action=install_x86 args="ip=bootif:dhcp inst.ks=https://10.10.10.1/install/sbin/profile.cgi inst.geoloc=0 inst.noverifyssl inst.ks.sendmac ramdisk_size=300000" kernel="vmlinuz-4.0_20170414_c4aff2a-7.x-x86_64" ramdisk="initrd.img-4.0_20170414_c4aff2a-7.x-x86_64"
error - "host" argument is required
{host ...} [action=string]
I found that "stack list host" was now returning blank/zero results. I also received this error for "stack list bootaction" when trying to see if I could pickup on anything:
[root@stacki ~]# stack list bootaction
File "/opt/stack/bin/stack", line 402, in run_command
rc = command.runWrapper(name, args[i:])
File "/opt/stack/lib/python2.6/site-packages/stack/commands/command.py", line 2324, in runWrapper
rc = self.run(self._params, self._args)
File "/opt/stack/lib/python2.6/site-packages/stack/commands/list/bootaction/__init__.py", line 106, in run
for row in self.db.fetchall():
stack.commands.list.bootaction: TypeError -- 'NoneType' object is not iterable
Prior to the x86_64 backend steps, the above commands would return results correctly when I had only the Pi 3 frontend machine and another Pi 3 as a backend machine.
Please let me know how I can best troubleshoot this to get things working. I'd like to have the Pi 3 frontend machine controlling a combination of my backend Pi 3s, VMs on different OSs, and physical machines.
Separate from above and minor, but did cause an error, I had to add "pallet" to the following step as it is currently published:
Add/enable the os pallet for the x86_64 box:
# stack add os-7.3_11122da-7.x.x86_64.disk1.iso
# stack enable pallet os arch=x86_64 box=x86_64
Thanks,
Keith
Thanks for providing these docs and tutorials. Much appreciated!
I followed through the instructions starting from the top. For the most part, all was clear and easy to work through. Things began to fall apart though once I got to the Build x86_64 Backend(s) section. That's where I left off and was not successfully able to continue. It seemed like the the main issue was that the PXE Boot files would not install correctly. I'm new to CoreOS and RPM syntax, but the past few years using Ubuntu are pretty similar which allowed me to try a few different install variations. I couldn't get any to stick that allowed me to proceed to the next step of copying the image files to the /tftpboot/pxelinux/ directory. These three were unable to be ran with a response of the source files not existing for the first two nor the entire /syslinux directory:
I do have a successful frontend machine up and running in a VM with a few backend hosts in VMs as well. Those are in Hyper-V on a Windows Server 2016 DC x86 system. That install and configuration was smooth and straight forward. To try and get past the above three steps, I found that both image files and the /syslinux directory were installed in the same locations that were suppose to be present on the Pi's drive. So, I copied them from that frontend machine to the Pi's Micro SD card.
I was not able to proceed with the following step either which is where I gave up for now. After copy/paste this step, I continued to get argument errors that didn't make sense at first until I found the host information was now missing.
I found that "stack list host" was now returning blank/zero results. I also received this error for "stack list bootaction" when trying to see if I could pickup on anything:
Prior to the x86_64 backend steps, the above commands would return results correctly when I had only the Pi 3 frontend machine and another Pi 3 as a backend machine.
Please let me know how I can best troubleshoot this to get things working. I'd like to have the Pi 3 frontend machine controlling a combination of my backend Pi 3s, VMs on different OSs, and physical machines.
Separate from above and minor, but did cause an error, I had to add "pallet" to the following step as it is currently published:
Thanks,
Keith