I have two nodes, bionic and cosmic.
I enabled the proposed repo on each.
I installed ipxe:
apt install ipxe ipxe-qemu grub-ipxe
On bionic, this gave me:
# apt list --installed ipxe-qemu grub-ipxe ipxe
Listing... Done
grub-ipxe/bionic-proposed,bionic-proposed,now
1.0.0+git-20180124.fbe8c
As negative confirmation: I tested a PXE boot with
1.0.0+git-20180124.fbe8c52d-0ubuntu2.1 on bionic and
1.0.0+git-20180124.fbe8c52d-0ubuntu4 on cosmic.
As expected, the VMs failed to successfully PXE boot.
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Tags added: veri
s/Not/Note/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1805920
Title:
iPXE ignores vlan 0 traffic
Status in MAAS:
Invalid
Status in ipxe package in Ubuntu:
Fix Released
Status i
Yes, sorry. I will try to test tonight (in a few hours) when I'm back at
the hotel. Not that I only have bionic and xenial to test with. I can
try to upgrade one of those to cosmic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
After realizing there are packages in the ci build [1] I installed the
following version from there:
1.0.0+git-20180124.fbe8c52d-0ubuntu4.1
I redefined the testipxe vm from the above test, and it also
successfully pxe booted.
[1]: https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/
I have run a test on cosmic. The test involved MAAS 2.4.3 installed on
bionic on 3 of the blades of the UCS chassis in the customer's data
center. I installed cosmic, 18.10 on a 4th blade and installed libvirt
and qemu-kvm and defined a VM similar to how maas defines VMs. with this
xml: https://pas
I was able to verify the fix works for bionic using maas 2.4.3. Am about
to install cosmic on the customer hardware to verify the fix there too.
I have run into a maybe-related issue with maas 2.5.0 filed separately
here: https://bugs.launchpad.net/maas/+bug/1811021
--
You received this bug noti
It seems an important component to the failure scenario is the hardware.
The customer equipment is a Cisco UCS chassis and the MAAS nodes are
blades in that chassis. Even though we cannot find anything in
configuration that specifically adds the vlan-0 tag (or priority tag),
traffic between the bla
The customer has bionic installed on 3 of the blades and I have
installed MAAS 2.4.3 on them using the Foundation Cloud Engine. I don't
have access to do the OS install myself. I could request a pair of
blades installed with cosmic but I'm unsure if I need all 3 or if I can
get by with just 2. Easi
Success.
I installed ipxe-qemu from andreserl's ppa and was able to PXE boot a Pod VM
from the infra node that wasn't running dhcpd.
# add-apt-repository ppa:andreserl/maas
# apt update
# apt install ipxe-qemu
# virsh list --all
# virsh start elastic-3
I watched the console of the VM and it succ
10 matches
Mail list logo