** Changed in: maas-images
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391354
Title:
Failure to boot ephemeral image for Utopic Fast Installer deployment:
Has the Utopic image from daily been promoted to releases to fix this
issue?
** Also affects: maas-images
Importance: Undecided
Status: New
** No longer affects: maas
** Changed in: maas-images
Status: New => Confirmed
--
You received this bug notification because you are a me
** 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/1391354
Title:
Failure to boot ephemeral image for Utopic Fast Installer deployment:
no ID_PATH for
This bug was fixed in the package systemd - 208-8ubuntu8.1
---
systemd (208-8ubuntu8.1) utopic-proposed; urgency=medium
* Fix path-id to correctly recognize supported devices. This brings back
/dev/disks/by-path/ symlinks for iSCSI devices. (LP: #1391354)
-- Martin PittThu,
I've verified this change fixes the issue with initramfs mounting iscsi targets
. I did this inside of maas.
* basically set up functional maas with some nodes, and daily images of utopic
imported.
from there
### repro
# get some tools
$ apt-get install cloud-image-utils --no-install-recommen
I tested this by installing systemd from Proposed onto image then doing
update-initramfs -u. I still saw the issue.
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/13
I investigated bug 1395813, it's not a regression. Tags updated.
** Tags removed: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391354
Title:
Failure to boot ephemeral image fo
I'm not involved with MAAS or image building, but I seriously doubt that
we build images with -proposed enabled regularly. What you could do is
one of the following:
* Boot an existing installation with "root=/dev/sda", enable -proposed,
dist-upgrade, and reboot (again with the default root=/dev/
Brian, will we be able to pull this fix from the daily images?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1391354
Title:
Failure to boot ephemeral image for Utopic Fast Installer deployment:
no
Hello Larry, or anyone else affected,
Accepted systemd into utopic-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/systemd/208-8ubuntu8.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wik
I uploaded 208-8ubuntu8.1 to the utopic SRU review queue. I tested it
with my "fake" MAAS setup from above. For SRU verification it would be
good if you could test it on a real MAAS setup, just to be sure.
** Changed in: systemd (Ubuntu Utopic)
Assignee: (unassigned) => Martin Pitt (pitti)
-
This is fixed by
http://cgit.freedesktop.org/systemd/systemd/commit/?id=cc821d02a37c8c76.
I'll prepare an SRU.
** Changed in: systemd (Ubuntu Utopic)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu Utopic)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received t
I confirm that this is fixed in vivid's udev. "sudo ./udevadm -d test-
builtin path_id /sys/block/sda" shows ID_PATH=ip-10.0.2.2:3260-iscsi-
utopic-daily-maas-amd64-lun-1 again, and replacing /lib/systemd/systemd-
udevd with 215-5's binary gets the by-path/ symlink again. So now off to
finding the
Notes for reproduction:
ipaddr=10.0.2.2
release=trusty # or utopic
kvm -m 512 -serial stdio -kernel ${release}-kernel -initrd ${release}-initrd
-append "nomodeset iscsi_target_name=${release}-daily-maas-amd64
iscsi_target_ip=$ipaddr iscsi_initiator=maas-enlist ip=maas-enlist:BOOTIF
BOOTIF=
14 matches
Mail list logo
