Hi!
**This is an automated message**
We believe this is no longer an issue in the latest MAAS releases. As
such, we are marking this bug report as invalid. If you believe this is
still an issue, please re-open this bug report.
Thanks
** Changed in: maas
Status: Triaged => Invalid
--
Yo
I dusted off an old [x86 32-bit] laptop with an e100 card and observed
this issue in conjunction with MAAS 1.9.
Oddly enough, when I auto-enlist the node for the first time, I see this
bug. But commissioning and deployment work perfectly.
--
You received this bug notification because you are a m
(Note: I saw this with each of the Trusty, Utopic, and Vivid kernels.)
** Also affects: partman-iscsi
Importance: Undecided
Status: New
** Project changed: partman-iscsi => maas
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Importance: Undecided => Medium
-
Hi,
I`m having the same issue. After manually (or via GRUB parameters)
setting up the IP, I need to run the iscsi script again to continue the
booting process.
Anyone have any luck dealing with it?
Regards,
NM
** Description changed:
--
You received this bug notification because you are a mem
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: partman-iscsi (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/1047998
Title
Moving to partman-iscsi for now as my initial guess is that the
configuration created by the installer is wrong, but it's also possible
that this needs to be fixed in open-iscsi.
** Package changed: debian-installer (Ubuntu) => partman-iscsi (Ubuntu)
--
You received this bug notification because
** Attachment added: "Config of VM I'm running this in."
https://bugs.launchpad.net/bugs/1047998/+attachment/3301942/+files/client1.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1047998
Title:
