** No longer affects: cloud-init (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1485685
Title:
Users are prompted on upgrade of cloud images
To manage notifications about this bug go to:
I think this was fixed and then has regressed again. I filed bug 1747464
to track the regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1485685
Title:
Users are prompted on upgrade of cloud
In case it's relevant, I was using the new m5 instance type.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1485685
Title:
Users are prompted on upgrade of cloud images
To manage notifications
I think this is still an issue. At least, I made a new Xenial box from
ami-c1167eb8 (Amazon AWS, eu-west-1, xenial, 16.04, amd64, hvm-ssd, 20180205).
Is that a 'daily'? After 'apt update', amongst other packages, these grub
packages were available to update:
grub-common:amd64
The latest xenial daily no longer exhibits this issue.
** Changed in: cloud-images
Status: In Progress => 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/1485685
Title:
Users are
So the reason that this regressed in xenial is that we've changed the
way in which we build images, and the workaround for this was only being
applied to PV images. I'm now building test images with the workaround
applied to HVM and PV images, to confirm that my reasoning is sound.
** Changed
** Changed in: cloud-images
Status: New => Confirmed
** Changed in: cloud-images
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1485685
Title:
Users are
** Tags removed: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1485685
Title:
Users are prompted on upgrade of cloud images
To manage notifications about this bug go to:
** Also affects: cloud-images
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1485685
Title:
Users are prompted on upgrade of cloud images
To manage
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Medium
** Changed in: cloud-init (Ubuntu)
Assignee: Robert C Jennings (rcj) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Medium
** Changed in: cloud-init (Ubuntu)
Assignee: Robert C Jennings (rcj) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Note bug 1323772 (marked as duplicate) with more commentary, description
of other workarounds and links to other bugs which may all be the same
issue.
** Description changed:
Steps to reproduce (use case):
1. Fire up a Trusty cloud image.
2. Run: sudo apt-get update sudo apt-get -y
To add clarity, the debconf proposal in comment #5 is the long-term
solution. In the interim, the workaround in comment #4 to remove the
ucf registry entry is needed. For existing users, this will need to be
done by hand. For future cloud images the ufc entry will be removed
(in the short-term)
I spoke with racb and he thought that the right thing to do might be to
debconf-ize grub-legacy-ec2 so that you don't need to change the [grub's
menu.lst] manually. rather than changing things outside of packaging
within the cloud image build.
--
You received this bug notification because you
To add clarity, the debconf proposal in comment #5 is the long-term
solution. In the interim, the workaround in comment #4 to remove the
ucf registry entry is needed. For existing users, this will need to be
done by hand. For future cloud images the ufc entry will be removed
(in the short-term)
At the root of this issue is ucf. The ucfr command will store a path
that contains symlinks during insertion but will only match the symlink-
resolved path when attempting removal. Cloud image builds modify grub's
menu.lst but have attempted to purge the ufc registry entry. This bug
in ucf
rcj, can you take a look at this?
** Changed in: ubuntu
Assignee: (unassigned) = Robert C Jennings (rcj)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1485685
Title:
Users are prompted on
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: 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/1485685
Title:
Users are
18 matches
Mail list logo
