this is a set of logs collected by
https://gist.github.com/smoser/e0cd7fafef8f52c24571
I'm posting them here to show that this seems pretty functional and reliable at
the moment. It installed trusty-hwe-u, trusty-hwe-v, vivid, wily in a loop 15
times each. It did fail on runs 16-20, but I believe the ipmi serial died, and
since check for success was based on that, it marked them as failed and I did
not get logs.
** Changed in: curtin (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: curtin (Ubuntu Vivid)
Status: New => Confirmed
** Changed in: curtin (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: curtin (Ubuntu Vivid)
Importance: Undecided => High
** Attachment added: "console logs from a deploy loop"
https://bugs.launchpad.net/curtin/+bug/1371634/+attachment/4418544/+files/deploy-loop-logs.tar.xz
** No longer affects: linux (Ubuntu Vivid)
** No longer affects: multipath-tools (Ubuntu)
** Description changed:
$ sudo blkid
/dev/sr0: LABEL="Ubuntu-Server 14.04 LTS ppc64el" TYPE="iso9660"
/dev/sda2: UUID="795a6e14-ea4e-4718-9e98-c6df3696920c" TYPE="ext4"
/dev/sda3: UUID="0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4" TYPE="swap"
/dev/sdb2: UUID="1d14c1f3-716f-4fb8-9070-d321b39ffcb3" TYPE="ext4"
/dev/sdb3: UUID="9c228177-d65c-4d19-a462-db1891e9781e" TYPE="swap"
/dev/sdg2: UUID="795a6e14-ea4e-4718-9e98-c6df3696920c" TYPE="ext4"
/dev/sdg3: UUID="0a91d81f-6a16-4b96-a92c-11ca8bdc4bf4" TYPE="swap"
/dev/sdh2: UUID="1d14c1f3-716f-4fb8-9070-d321b39ffcb3" TYPE="ext4"
/dev/sdh3: UUID="9c228177-d65c-4d19-a462-db1891e9781e" TYPE="swap"
I'm not sure what exactly those block devices are (as in if they're
raided in hardware or they actually represent physical spinning disks).
But I do know that writing data to sda causes that data to be readable
from sdg.
The same is true:
sda -> sdg
sdb -> sdh
That is what causes those UUIDs to be similar. Everything is
functional, you just have to know that if your root device is /dev/sdg
that you should probably not write data to /dev/sda thinking you can use
it as a disk.
Related bugs:
- * bug 1432062: multipath-tools-boot: support booting without
user_friendly_names on devices with spaces in identifiers
- * bug 1463043 : some SM15K systems fail to boot after deployment - drop into
initramfs shell
- * bug 1462530 : multipath errors on vivid, wily kernel
- * bug 1463046: installation of multipath-tools-boot can break boot
+ * bug 1432062 : multipath-tools-boot: support booting without
user_friendly_names on devices with spaces in identifiers
+ * bug 1463043 : some SM15K systems fail to boot after deployment - drop into
initramfs shell
+ * bug 1462530 : multipath errors on vivid, wily kernel
+ * bug 1463046: installation of multipath-tools-boot can break boot
+ * bug 1447167: multipath-install: Installing with multipath enabled does not
install multipath-tools
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-35-generic 3.13.0-35.62
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic ppc64le
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: [Errno 2] No such file or directory: 'iw'
CurrentDmesg: [ 88.736220] init: plymouth-upstart-bridge main process
ended, respawning
Date: Fri Sep 19 14:31:20 2014
HibernationDevice: RESUME=UUID=9c228177-d65c-4d19-a462-db1891e9781e
Lsusb:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcEnviron:
TERM=screen
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: root=UUID=1d14c1f3-716f-4fb8-9070-d321b39ffcb3 ro
console=hvc0 BOOTIF=01-6c-ae-8b-6a-a0-88 quiet
RelatedPackageVersions:
linux-restricted-modules-3.13.0-35-generic N/A
linux-backports-modules-3.13.0-35-generic N/A
linux-firmware 1.127.6
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
** Also affects: curtin (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed in: curtin (Ubuntu Utopic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1371634
Title:
block devices appear twice [install does not use multipath]
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1371634/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
