PXE Booting Ubuntu 16.04 with UEFI
by Traiano Welcome
Hi
I'm having trouble PXE booting Ubuntu 16.04 (Xenial) on a Dell r620
(with iDrac7).
The boot fails with these messages after contacting the cobbler server
successfully:
----
NBP filename is /pxelinux.0
NBP filesize is 16794 bytes
Downloading NBP file
Succeed to download NBP file
Downloading NBP file ...
Succeed to download NBP file
Boot failed: EFI Network 1
Boot Failed: ubuntu
No boot device available
Please ensure compatible bootable media is available.
----
Please could someone shed some light on what the reason for this might
be, or how I could troubleshoot it further?
Is there something special I have to do with PXE booting Ubuntu with
UEFI enabled when using cobbler?
Many thanks in advance for any help!
Traiano
6 years, 5 months
How to Change the boot Device order after a PXE installation of Virtualbox VM
by Traiano Welcome
Hi List
I'm using cobbler to install virtualbox vms, which requires the boot
order to be PXE -> Disk.
However I'm not sure how to get cobbler to reconfigure the boot order
so the VM boots off the disk after the install is complete (my VM
attempts to boot off pxe again but fails because this is disabled in
cobbler).
Is there a confguration option in cobbler / kickstart that
reconfigures the virtualbox device boot order once the install is
complete?
Thanks,
Traiano
6 years, 5 months
Cobbler on Ubuntu Xenial Xerus: "httpd does not appear to be running and proxying cobbler,"
by Traiano Welcome
Hi List
I'm struggling to get cobbler working on Ubuntu Xenial Xerus, however
it's just one issue after the other. So far, I'm blocked at this
failure when running cobbler check:
---
root@cobbler:~# cobbler import --name=ubuntu16.04-x86_64 --arch=x86_64
--path=/mnt
httpd does not appear to be running and proxying cobbler, or SELinux
is in the way. Original traceback:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/cobbler/cli.py", line 252, in
check_setup
s.ping()
File "/usr/lib/python2.7/xmlrpclib.py", line 1243, in __call__
return self.__send(self.__name, args)
File "/usr/lib/python2.7/xmlrpclib.py", line 1602, in __request
verbose=self.__verbose
File "/usr/lib/python2.7/xmlrpclib.py", line 1283, in request
return self.single_request(host, handler, request_body, verbose)
File "/usr/lib/python2.7/xmlrpclib.py", line 1311, in single_request
self.send_content(h, request_body)
File "/usr/lib/python2.7/xmlrpclib.py", line 1459, in send_content
connection.endheaders(request_body)
File "/usr/lib/python2.7/httplib.py", line 1053, in endheaders
self._send_output(message_body)
File "/usr/lib/python2.7/httplib.py", line 897, in _send_output
self.send(msg)
File "/usr/lib/python2.7/httplib.py", line 859, in send
self.connect()
File "/usr/lib/python2.7/httplib.py", line 836, in connect
self.timeout, self.source_address)
File "/usr/lib/python2.7/socket.py", line 575, in create_connection
raise err
error: [Errno 113] No route to host
---
I see the line "error: [Errno 113] No route to host" , however it's
not clear to me what host cobbler is trying to connect to? apache is
up, and so is cobblerd:
---
root@cobbler:~# service cobblerd status
● cobbler.service - LSB: Cobbler daemon
Loaded: loaded (/etc/init.d/cobbler; bad; vendor preset: enabled)
Active: active (running) since Sun 2017-10-29 00:04:51 CEST; 33min ago
---
---
root@cobbler:~# service apache2 status
● apache2.service - LSB: Apache2 web server
Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
---
How would I troubleshoot this further and hopefully fix it?
Thanks in advance,
Traiano
6 years, 5 months
preinstall via dhcp+PXE on one nic and then move to bonded static ip post install
by James Clendenan
Hi List,
I’ve got a physical system that we’re trying to cobbler build, on a management network and then pivot over to using a bonded interface pair for the production side.
Looking at the kickstart it should work correctly Post install on the bond (or at least will with some tuneing).
However the installer pre_install_networking_config snippet assumes that the boot env is identical to the final running environment.
Any suggestions on how we might adjust things to have a pre_boot config via dhcp and then a post install config?
Anyone else tried this? or am I just crazy to try this method?
Side note: this is for an ospf network segment, so I’m trying to avoid adding a dhcp server and default gateway to the running environment, hence the pivot.
Thanks,
James
6 years, 5 months
Test
by Michael C. Tiernan
Sorry for the test message. I'm trying to help the mailing list host system administrator.
Thanks in advance for your time.
6 years, 5 months