This bug was fixed in the package curtin - 0.1.0~bzr221-0ubuntu1~14.10.1
---
curtin (0.1.0~bzr221-0ubuntu1~14.10.1) vivid-proposed; urgency=medium
* New upstream snapshot.
- support installation to multipath devices. (LP: #1371634)
- know that kernel version 4.2.0 maps to
This bug was fixed in the package curtin - 0.1.0~bzr221-0ubuntu1~14.04.1
---
curtin (0.1.0~bzr221-0ubuntu1~14.04.1) trusty-proposed; urgency=medium
* New upstream snapshot.
- support installation to multipath devices. (LP: #1371634)
- know that kernel version 4.2.0 maps to
The system where we found these issues is happily deploying using newer
curtin.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
** Branch linked: lp:ubuntu/trusty-proposed/curtin
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1443542
Title:
curtin race on vivid when /dev/sda1 doesn't exist
To manage
** Branch linked: lp:ubuntu/vivid-proposed/curtin
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1443542
Title:
curtin race on vivid when /dev/sda1 doesn't exist
To manage
Hello Robie, or anyone else affected,
Accepted curtin into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/curtin/0.1.0~bzr221-0ubuntu1~14.10.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Robie, or anyone else affected,
Accepted curtin into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/curtin/0.1.0~bzr221-0ubuntu1~14.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
** Description changed:
+ === Begin SRU Template ===
+ [Description]
+ Installation fails, with log information showing:
+
+ Unexpected error while running command.
+ Command: ['mkfs.ext4', '-q', '-L', 'cloudimg-rootfs', '/dev/sda1']
+ Exit code: 1
+ Reason: -
+ Stdout: ''
+ Stderr:
** Branch linked: lp:~smoser/ubuntu/trusty/curtin/trusty-sru
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1443542
Title:
curtin race on vivid when /dev/sda1 doesn't exist
To
This is believed to be fix-committed. under commit 205.
I removed a 'wipefs' which always calls blockdev --rereadpt. That would
trigger deletion and recreation of partition devices.
We replaced it with 'wipe_partitions' which does not issue a rereadpt, but
instead just zeros the front of the
Marking fix-committed. if you see this issue again, please re-open and
ping me.
** Also affects: curtin
Importance: Undecided
Status: New
** Changed in: curtin
Status: New = Fix Committed
** Changed in: curtin
Importance: Undecided = Medium
** Changed in: curtin (Ubuntu)
Execution of blockdev --rereadpt simply issues a call to
ioctl(BLKRRPART) which forces kernel to re-initialize its metadata.
Kernel adds information about newly created partition here:
http://lxr.linux.no/#linux+v3.19.1/block/partition-generic.c#L269 You
can see a call to kobject_uevent() which
** Attachment added: hacktest: loop
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1443542/+attachment/4397511/+files/hacktest
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
** Attachment removed: hacktest: loop
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1443542/+attachment/4397511/+files/hacktest
** Attachment added: hacktest.sh: loop over create update expect
i'm looking at http://bazaar.launchpad.net/~curtin-
dev/curtin/trunk/view/head:/helpers/common#L330 (which admittedly i just
committed to, but did not change this general behavior).
and i'm not really sure how it can get there...
partition_main() line 374 calls wipedev. wipedev wipes start and
so 1 of 2 things seems like it must have happend:
a.) 'isblk' is not getting set (which would mean we dont run blockdev and
udevadm settle)
b.) my assumption that changing the partition table on a device, then running
'blockdev --rereadpt' and subsequently 'udevadm settle' would result in the
possible / likely explanation is that there is no guarantee that blockdev will
exit after kernel has put events into the udev queue.
so udevadm could have run and found an empty queue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: curtin (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
cloud-init[1226]: /var/lib/cloud/instance/scripts/user_data.sh: 18:
/var/lib/cloud/instance/scripts/user_data.sh: initctl: not found
ubuntu@phony-trick:/var/log$ cat /proc/partitions
major minor #blocks name
1101048575 sr0
80 488386584 sda
81 488385560
** Tags added: openstack uosci
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/1443542
Title:
curtin race on vivid when /dev/sda1 doesn't exist
To manage notifications about this
20 matches
Mail list logo
