** Changed in: maas (Ubuntu)
Status: Incomplete => Invalid
** Changed in: maas
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from
For reference, this is the libvirt page which covers bridge timeouts
affecting PXE booting:
http://wiki.libvirt.org/page/PXE_boot_%28or_dhcp%29_on_guest_failed#Long_Forward_Delay_Time_on_Bridge
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
I hit this problem today, and it turned out to be a non-MAAS bug.
I was trying to configure a Trusty host with VMware Workstation *and*
LXCs sharing the same network.
It turns out that the combination of VMware plus Linux bridge interfaces
have a bug: if I set up the VM network to be bridged to b
** Changed in: maas
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications about this b
** Changed in: maas
Milestone: 1.7.2 => 1.7.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications about this bug go to:
Okay, we did a lot of debugging and tracing attempting to find the
problem. In the end, it was hardware.
I upgraded manually to a newer version of syslinux and pxelinux which
/did/ appear to be working, albeit VERY slowly. It seems that the 6.x
syslinux network stack is more tolerant of errors, as
Static ARP did not help.
Setting the MTU to 1200 caused pxelinux.0 to fail transferring with
similar, but different behaviour:
12:12:50.699971 IP 10.0.0.12.2071 > 10.0.0.1.tftp: 32 RRQ "pxelinux.0" octet
blksize 1456
12:12:50.773393 IP 10.0.0.1.59263 > 10.0.0.12.2071: UDP, length 15
12:12:50.7
Oh, I'm mistaken -- it's exactly the same as before. I hadn't noticed
that the machine had replied once before going offline.
Gavin looked up the ARP issue and it turns out that pxelinux doesn't
respond to ARP when in the keyboard read loop and when in the tftp
send/recv loop, so that's why there'
I installed a newer version of pxelinux to see if that is the culprit.
It doesn't work, but /some/ traffic between the nodes now happens when
transferring the kernel:
11:54:03.181388 IP 10.0.0.12.49164 > 10.0.0.1.tftp: 77 RRQ
"ubuntu/amd64/generic/trusty/release/boot-kernel" octet tsize 0 blksiz
We're not on a bridged network (nor are there VMs) so we may be seeing a
different bug, or perhaps both situations trigger the same symptom. I'll
try playing with the timeout.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
> When we start transferring the kernel over, the machine on the other
side stops responding
This is indeed what seems to be causing the problem. Note that we're
seeing (a worrying number of) retries in some of the earlier (and
successful) transfers.
What kind of bridge is being used here? (virb
When we start transferring the kernel over, the machine on the other
side stops responding:
15:59:23.563014 IP 10.0.0.12.49164 > 10.0.0.1.tftp: 77 RRQ
"ubuntu/amd64/generic/trusty/release/boot-kernel" octet tsize 0 blksize 1408
15:59:23.578439 IP 10.0.0.1.59570 > 10.0.0.12.49164: UDP, length 29
Here's my tcpdump :)
** Attachment added: "tftp.cap"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1246236/+attachment/4310773/+files/tftp.cap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Um ok
On Feb 2, 2015 2:25 PM, "Christian Reis" wrote:
> ** Changed in: maas
> Assignee: zack (jnrflatwork) => (unassigned)
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1246236
>
> Title:
> pxe boot from maas fails due to time
This effects me :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications about this bug go to:
https://bugs.launchpad.net/maa
** Changed in: maas
Assignee: zack (jnrflatwork) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications a
** Changed in: maas
Assignee: (unassigned) => zack (jnrflatwork)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications a
** Changed in: maas
Milestone: 1.7.1 => 1.7.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications about this bug go to:
** Changed in: maas (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications about thi
Might want to also check it isn't bug 116.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications about this bug go to:
ht
See also bug 1398159
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications about this bug go to:
https://bugs.launchpad.net/m
** Changed in: maas
Milestone: None => 1.7.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications about this bug go to:
** Changed in: maas
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications about this bug go
** Changed in: maas
Status: Expired => New
** Changed in: maas (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from maas fails du
** Tags added: cts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications about this bug go to:
https://bugs.launchpad.net/maa
[Expired for maas (Ubuntu) because there has been no activity for 60
days.]
** Changed in: maas (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Tit
[Expired for MAAS because there has been no activity for 60 days.]
** Changed in: maas
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot fro
Was not able to reproduce after a reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications about this bug go to:
https:/
I'm seeing this error in the Garage MAAS today. As it happens, also have
two interfaces on the network on that machine. Will try reducing to one
and reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Huh, that timeout must have changed since I last looked at the code. Anyway,
7 seconds should be enough per datagram.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from maa
On 17 March 2014 00:39, Julian Edwards <1246...@bugs.launchpad.net>
wrote:
> On Friday 14 Mar 2014 09:37:18 you wrote:
> > I was adviced to try rebooting the MAAS server (region and cluster
> > controller on one box) which fixed the problem. But a subsequent reboot
> > brought it back :/
>
> The t
Going incomplete again since there's still no reliable way to reproduce
any bug in maas.
** Changed in: maas
Status: Confirmed => Incomplete
** Changed in: maas (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: maas
Milestone: 14.04 => None
--
You received this bug noti
On Friday 14 Mar 2014 15:06:17 Graham Binns wrote:
> On 14 March 2014 14:43, Adam Collard wrote:
> > So in my case, the problem was PEBKAC and networking. Specifically I had
> > two interfaces on my MAAS server that were connected to the same
> > network, both had equally weighted routes to the ga
On Friday 14 Mar 2014 09:37:18 you wrote:
> I was adviced to try rebooting the MAAS server (region and cluster
> controller on one box) which fixed the problem. But a subsequent reboot
> brought it back :/
I am pretty sure there's something wrong with some folks' networking setups
but I'm not sur
On 14 March 2014 14:43, Adam Collard wrote:
> So in my case, the problem was PEBKAC and networking. Specifically I had
> two interfaces on my MAAS server that were connected to the same
> network, both had equally weighted routes to the gateway. Only one of
> them was configured in MAAS for the cl
So in my case, the problem was PEBKAC and networking. Specifically I had
two interfaces on my MAAS server that were connected to the same
network, both had equally weighted routes to the gateway. Only one of
them was configured in MAAS for the cluster controller. It was
(seemingly) by chance that t
I was adviced to try rebooting the MAAS server (region and cluster
controller on one box) which fixed the problem. But a subsequent reboot
brought it back :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
> Are you still seeing this problem?
I'm seeing this problem now. For me it only started occurring after
upgrading MAAS from 1.5+bzr1977-0ubuntu3 to 1.5+bzr1977-0ubuntu4. MAAS
is no longer able to PXE boot.
To rule out any upgrade/configuration concerns I purged and reinstalled
MAAS (wiping out t
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications about this bug go to:
https://bugs.launchpad.n
Nobody has reported seeing this for a while. I looked at the code and it
has a whole second timeout per packet. You would think that this is more
than enough over a LAN segment.
I also discovered that the tftp client can set its own timeouts
(http://tools.ietf.org/html/rfc2349). Given that you se
> We probably just need a bigger timeout in the TFTP server code. Gavin?
Let's try it!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from maas fails due to time out
To mana
I've had a few people report this, and seen it myself on one occasion
when I mixed 100Mb/1Gb switches on my network.
We probably just need a bigger timeout in the TFTP server code. Gavin?
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Importance: Undecided => Critical
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: maas (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe b
** Also affects: maas
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246236
Title:
pxe boot from maas fails due to time out
To manage notifications about
44 matches
Mail list logo
