root@juju-rack2:/var/log/maas# maas refresh
root@juju-rack2:/var/log/maas# netstat -untap | grep 3260
tcp0 0 0.0.0.0:32600.0.0.0:* LISTEN
26516/tgtd
tcp6 0 0 :::3260 :::*LISTEN
26516/tgtd
Image source: maas.io
Sync: completed
** Attachment added: "Maas GUI Capture"
https://bugs.launchpad.net/maas/+bug/1639202/+attachment/4815666/+files/Screen%20Shot%202017-02-08%20at%209.57.08%20PM.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
This is happening to me on an Intel NUC 5i5MYHE blade on PXE. The error
is an iSCSI destination error apparently. Same scenario...
Maas version: MAAS Version 2.1.3+bzr5573-0ubuntu1 (16.04.1)
On node PXE boot console output (sorry, but some of this is cut off on
this screen, typing what I can
** Changed in: initramfs-tools (Ubuntu)
Status: New => Invalid
** Changed in: maas-images
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
9c-eb-e8-3c-52-cc is the mac address of the USB C Network adapter.
Apologies that I hadn't already made this clear on this thread.
I'd already looked into the mac address pass-through issue before opening this
case. At the time, upgrading the BIOS from 1.2.10 to 1.2.14 didn't work. While
So apparently this is a feature of the dell-branded usb-c devices.
Please see the knowledge base.
http://www.dell.com/support/article/us/en/04/SLN301147
I've heard back from our contacts at dell, and the issue you are seeing
is apparently resolved via a firmware update.
--
You received this
Another thought is that the pxe firmware of the usb-c device was missed
in the rebranding process by dell. This is actually quite likely in my
opinion.
Either way we need to engage Dell in order to remedy this.
--
You received this bug notification because you are a member of Ubuntu
Touch
Do you know where the 9c-eb-e8-3c-52-cc originates from? There is
nothing we can do so long as the request to maas originates from the 9c-
eb-e8-3c-52-cc mac address. If the firmware is somehow masking the
actual mac address with the above then that needs to be fixed in the
firmware, or via a
additional info (as requested).
** Attachment added: "rackd log showing mac9c"
https://bugs.launchpad.net/maas/+bug/1639202/+attachment/4787537/+files/rackd-grep-mac9c.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
- disabled wireless in BIOS. booted from USB NIC. I get the same problem.
- It's booting via ip4. I've attached the log info from rackd.log showing the
entries during the dhcp process (ipv4.txt).
- Also, another txt file added showing the grep results from the
/var/log/maas/rackd.log for
Alright so the problem at present appears to be that the machine is pxe
booting off of a nic with a mac address that is not showing up after the
kernel boots.
The way the boot works is the bios/efi launches a pxe network stack.
This typically makes a dhcp request. The DHCP server responds with
1. 16.04 kernel version = 4.4.0-42-generic is the result of uname -r
from the 5510 that already had 16.04 installed.
2. 4.4.0-47-generic is the kernel version used during commissioning
(when it drops to shell, this is what uname -r provides)
3. In /sys/class/net I see: enx847beb55c195 ->
One of my collegues informed me that maas 2.1 is meant to use
https://images.maas.io/ephemeral-v3/daily/
Instead of the ephemeral-v2 images.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
1. So this indicates to me that the kernel is unable to control the usb
device. When you mentioned earlier that you were able to investigate
the usb-c device with a 16.04.1 machine, what exact kernel version was
that machine running. uname -a output should be sufficient.
2. Can you similarly
Hi Richard,
Thanks for updating the bug with Dave's latest suggestion in order to
isolate this particular situation.
We will come back to you soon with the next steps.
Regards,
Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
more info, as requested:
ls -la /sys/class/net/*
lrwxrwxrwx 1 0 /sys/class/net/lo ->
../../devices/virtual/net/lo
lrwxrwxrwx 1 0 /sys/class/net/enx847beb55c195 ->
>From the initramfs shell can you provide me the output for
ls -la /sys/class/net/*
and
cat /sys/class/net/*/address
I have a feeling you'll only see lo and enx847beb55c195. Specifially I'm
looking for the device name that matches your BOOTIF mac address. However if
it's showing up please
If the device is not being detected I have a feeling there may be
something going wrong with udev.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1639202
Title:
So from the best I can determine it looks like configure_networking out
of scripts/functions of the initramfs is failing to properly bring up
the network device. I'm going through the process now to figure out
what logic might actually be stopping it from functioning. I'll let you
know more when
Hi Dave,
The following output appears. I don't see an error relating to "no net-
BOOTIF.conf" now...just what's below...
ipconfig: BOOTIF: SIOCGIFINDEX: no such device
ipconfig: no devices to configure
/scripts/local-top/scsi: line 515: can't open '/run/net-BOOTIF.conf'
lvmetad is not active
@Richard Lovell
Can you please provide me the console log messages that exist above the "no
/run/net-bootif.conf"?
Additionally can I get the output of following commands from the laptop after
the message "Dropping to shell!"
- ip a # I'm not sure if this available, but ifconfig or similar
21 matches
Mail list logo
