No updates for more than a year. Closing as invalid.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Assignee: Stefan Bader (smb) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Tags added: openstack uosci
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1410363
Title:
partition table updates require a reboot
To manage notifications about this bug go to:
https://bugs.launc
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1410363
Title:
partition table updates require a reboot
To manage notifications about this bug
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1410363
Title:
partition table updates require a reboot
To manage notifications ab
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Stefan Bader (smb)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1410363
Title:
partition table updates require a reboot
To manage notif
Alternatively, if you can provide us with the baby steps approach to get a
*stack instance to the point of failure?
Or: Has one enough control to trigger a memory dump of an instance?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
As discussed on IRC this sounds like the re-appearance of the issue
where some data which is used by cloud-init was present on the second
disk. After boot and setup this ends up in a state where one succeeds in
running unmount but the jbd process related to the mount remains stuck.
Last time this
Do you happen to know if this was also the case with older kernels?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
