Attached debdiff against trusty-proposed. Tested and confirmed it works.
** Description changed:
[SRU JUSTIFICATION]
[IMPACT] Cloud-init, as part of the first boot configures grub-pc to set
the device that grub should install to. However, in the case of HVM
instances, /dev/xvda and /de
** Patch added: "Debdiff against cloud-init_0.7.5-0ubuntu1.2 in trusty-proposed"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1336855/+attachment/4208139/+files/lp-1336855-14.04.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
In re: to comment #19
> Am I right in thinking that after review it will be released on precise and
> trusty and hit the cloud-images/AWS at the same time?
The update will be released to the update archive around the same time
for 12.04 and 14.04. The next batch of cloud-images released after thi
** Description changed:
- Cloud-init, as part of the first boot configures grub-pc to set the
- device that grub should install to. However, in the case of HVM
+ [SRU JUSTIFICATION]
+
+ [IMPACT] Cloud-init, as part of the first boot configures grub-pc to set
+ the device that grub should install
** Changed in: cloud-init (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Precise)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Precise)
Importance: Undecided => Critical
** Changed in: cloud-init (Ubuntu Trusty)
Importance: Undecided
Thanks for the reply... I'm still working out how the Ubuntu
daily/release dev process works :)
I just found the page that documents what SRU is :)
Am I right in thinking that after review it will be released on precise
and trusty and hit the cloud-images/AWS at the same time?
We're currently
Uploaded a new branch for SRU after chatting with Scott. Pending review.
** Branch linked: lp:~utlemming/ubuntu/precise/cloud-
init/lp1336855-1363260
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336
** Branch linked: lp:cloud-init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336855
Title:
[SRU] non-interactive grub updates for 12.04 break on AWS
To manage notifications about this bug go to:
** Also affects: cloud-init (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Utopic)
Importance: Critical
Status: Confirmed
--
You received this bug
Has there been any progress on getting this resolved in the released
cloud image builds?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336855
Title:
[SRU] non-interactive grub updates for 12.04 bre
This is also a problem in trusty using the latest release build
(20140813) with cloud-init 0.7.5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336855
Title:
[SRU] non-interactive grub updates for
I was able to workaround the issue by modifying /etc/default/grub and
issuing update-grub ( post apt-get upgrade ). I assume it has something
to do with the console settings?
- bad grub -
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full
That should have been "with the correct *boot* device"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336855
Title:
[SRU] non-interactive grub updates for 12.04 break on AWS
To manage notifications
I have reviewed the patch (lp:~utlemming/ubuntu/precise/cloud-
init/lp1336855 through r211) and tested it on EC2 and an OpenStack cloud
and it performed well. The upgrade of cloud-init forced a grub-install
and it ran with the correct root device.
--
You received this bug notification because yo
** Patch added: "Modified patch that is chroot safe"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1336855/+attachment/4144962/+files/precise.deb.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336855
Title:
[SRU] non-interactive grub updates for 12.04 break on AWS
To manage notifications about this bug go to:
https://bug
Worked out a postinst script that 1) detects if the root device and the
grub-pc install device is mismatched; 2) if so, re-sets the grub-pc
device and then installs grub to the device in question. The changes
should be safe, but I want a through to be safe.
** Branch linked: lp:~utlemming/ubuntu/p
** Patch added: "Patch to fix future and broken instances"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1336855/+attachment/4144896/+files/precise.deb.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
To clarify, the fixes tested only fix the cloud-init piece. Since the
cloud-init module in question only runs at first boot. So while the
patch does address the problem, it only fixes it for future instances.
Existing instances that upgrade grub will be broken. Meaning that if a
ABI changes takes p
** Summary changed:
- non-interactive grub updates for 12.04 break on AWS
+ [SRU] non-interactive grub updates for 12.04 break on AWS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1336855
Title:
[S
20 matches
Mail list logo
