Some interesting observations. The customer deployed a pair of Centos7
machines and confirmed the vlan0 tag issue existed there as well. That
wasn't too surprising.
However, they deployed a pair of Centos6 machines and they do NOT have
the vlan0 tag issue.
This seems to confirm that the issue is
The Centos7 deployments were to other blades in the UCS chassis and
pings between the two Centos7 machines did not have vlan 0 tags.
I'll add your ppa and update to your ipxe and test pod VM booting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Sorry, I got that wrong. A deployment of a pair of Centos6 hosts to the
blades did not have vlan 0 tags. The Centos7 deployments did have vlan 0
tags.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805
I have not tried Centos6 VMs.
The customer reported that he deployed Centos7 to the baremetal blades
and saw, in ping traffic that incoming packets were vlan 0 tagged.
Then he deployed Centos6 to two baremetal blades and, in a ping test,
did not see any vlan tags.
If this is true, it suggests Ub
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
I can confirm, this is still broken.
In my output, I'm missing the leading and trailing square bracket. Also,
between some stanzas there are close and open curly braces (on the same
line) without a comma in between.
Since those are the only two syntactical errors in the output I'm working with,
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
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
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 tested Corey's fix (via ppa) side-by-side with a cinder unit with
version 2:15.4.0-0ubuntu1~cloud0 (from bionic-proposed/train).
I used a bionic qcow2 image with:
openstack volume create --image bionic --size 3 --type stable2-az2 vernvol
Again, glance is backended by the az1 ceph cluster so t
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
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
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
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
** Attachment added: "bundle where bug occurs"
https://bugs.launchpad.net/nova/+bug/1773449/+attachment/5146087/+files/bundle-25May18.yaml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773449
Tit
I've pinged the customer for the specific details of the failure.
>From my understanding, they pulled the power on the compute node -- but
I will get confirmation on that point.
There isn't anything out of the ordinary in the compute configuration so
it's likely the instances came up as SHUTDOWN
>From the customer:
1. This is a cold power off. The initial test was done by pulling the
plugs on the box. Subsequent tests are from iDRAC where I do a cold
power down.
2. The first test the vms did not boot automatically. After I realized
they were not going to start I asked Craig to help me wi
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https
s/Not/Note/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805920
Title:
iPXE ignores vlan 0 traffic
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1805920/+subs
In the meantime, we keep having to add a post-deployment cleanup step to
our deployment guides:
Delete node1 crm resources (LP#1874719):
$ juju run -m openstack --all -- sudo crm node delete node1
Which is overkill but works.
--
You received this bug notification because you are a member of
Just to clarify, this is fixed in impish but is still a problem on older
releases. Is that correct?
And since the problem is fixed/fixable in corosync, this bug is probably
invalid for charm-hacluster, right?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
21 matches
Mail list logo
