I'm now on the 4.11.0-10-generic kernel, and have not seen this failure
again. However, I'll leave it up to the kernel team to see if they want to
pursue this further. You can install this kernel on Xenial by
installing linux-generic-hwe-16.04-edge.
More information is available
Yakkety)
Assignee: Dave Chiluk (chiluk) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700373
Title:
intel-microcode is out of date, version 20170707 fixes errata on 6th
and
I have now killed my 4-simultaneous compilation loop tests after 20
hours. With the previous microcode, 2 of 3 loop threads died with a
segfault within 1 hour, so I consider this fixed.
@Others, Has anyone tested this with skylake/kabylake on zesty?
I have installed and boot tested using
Marking xenial-verification-done
I was able to reproduce the compilation crash as described on the ocaml
bug in about 30 minutes on my Skylake machine. After upgrading
firmware, I have been running for simultanous compilations loops for the
last 2 hours with no crash. I will let them continue
I have been running this on my kabylake laptop and skylake desktop under
X for quite some time now, and haven't hit any issues that I can
attribute to the microcode. I attempted to follow the reproducer here
https://caml.inria.fr/mantis/view.php?id=7452 , but some of the versions
of packages
@rbasak, The reason for the omission of "skylake" from the changelog
entry for zesty is because zesty already had 3.20170511.1~ubuntu17.04.0
in -updates which contained the fixes for the majority of Skylake
processors, but not Kaby Lake. So for zesty this release only fixes
kaby lake processors,
The changelog entry is there to match the artful changelog entry *(it
applies completely correctly for zesty).
As for the dat files. I guess my changelog entry would have been more
explicit had I said sync instead of backport.
" * Backport of new upstream microcode release to address Hyper
@bybeu, please do not post questions like this to ancient bugs.
Instead use askubuntu or ubuntuforums.
Back to your problem at hand though. You are free to manually add your
ssd's to the whitelist. Unfortunately the way you asked your question
makes it very unclear what you've done or what
** Tags added: dell
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702961
Title:
Intel wifi instability with 4.10 and Intel Device 24fd
To manage notifications about this bug go to:
@slashd beat me to the upload, but it looks good to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705054
Title:
Trusty kexec-tools suffer from upstream code regression. Fix not
included.
To
** Tags added: indeed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204
Title:
removing kernels should not require a restart afterward
To manage notifications about this bug go to:
@sil2100, I deployed this fix to my xenial based main mythtv frontend.
I have been using the frontend to watch hevc encoded OTA 1080p
recordings on my nvidia 1060 gpu with the . These recordings were
generated using ffmpeg with the nvenc hevc hardware offload.
I have also explicitly installed
Please try the latest hwe stack by. I'm using kabylake + the hwe stack
without issue at the moment.
sudo apt install --install-recommends linux-generic-hwe-16.04 xserver-
xorg-hwe-16.04
More info is available here.
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
I'm also closing the
Testing done.
X + 4.10 + Sandybridge-E + sig=0x206d6, pf=0x4, revision=0x619 => 0x619
X + 4.4 + Ivy + sig=0x306a9, pf=0x10, revision=0x1c => 0x1c
Y + 4.8 + Ivy + sig=0x306a9, pf=0x10, revision=0x1c => 0x1c
Z + 4.10 + Ivy + sig=0x306a9, pf=0x10, revision=0x1c => 0x1c
Z + 4.10 + Skylake +
** Tags added: indeed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1591669
Title:
duplicate touchpad reported and syndaemon/synclient does not work
To manage notifications about this bug go to:
.
I've also uploaded correctly versioned packages for x, y, z to their
appropriate queues.
** Changed in: intel-microcode (Ubuntu Zesty)
Status: Fix Released => Confirmed
** Changed in: intel-microcode (Ubuntu Zesty)
Assignee: (unassigned) => Dave Chiluk (chiluk)
** Tags r
@hmh, thanks for the heads up.
@rbasak, As the X and Y uploads haven't made it through the SRU yet. Do
you want me to repackage with 20170707?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700373
I have repackaged this again based on the discussion from the ubuntu-
release mailing list discussion. I have avoided any other changes that
didn't appear absolutely necessary. I have uploaded the resulting
packages to my ppa available here
https://launchpad.net/~chiluk/+archive/ubuntu/1700373
Public bug reported:
Wifi drops and has to reconnect regularly.
This is on a Dell Precision 5520.
Kernel warnings in log include.
[ cut here ]
WARNING: CPU: 4 PID: 1042 at
/build/linux-hwe-dbNd9L/linux-hwe-4.10.0/drivers/net/wireless/intel/iwlwifi/mvm/sta.c:1523
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673481
Title:
"Failed to initialize A/V Sync" error trying to play
I should also mention that we will be following Debian's lead and not
updating this for Trusty. Lack of early upload being one of the big
reasons for this.
** Description changed:
[Impact]
* A security fix has been made available as part of intel-microcode
* It is advisable to apply it
I just pushed uploads for this into the x, and y queues. I wanted to
hold off for a few days to give those on zesty/artful to sniff test this
before I pushed on the SRU.
I have tested this on X+skylake and X+sandy-bridge-e *(that was just to
make sure that we didn't break non skylake and
@Joe MC. What hardware do you have? I know this affects pascal
(feature set h), but I think it might affect vdpau feature sets e,f,and
g as well. Would you mind sharing what hardware you hit this with?
@else
Alright I've uploaded fixes for x+. I'm not uploading for T because if you
have new
** Tags added: verification-done-artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673481
Title:
"Failed to initialize A/V Sync" error trying to play HEVC h.265 with
vdpau that supports hevc
** Description changed:
When trying to play HEVC / h265 / x265 video, frontend fails and reports
"Failed to initialize A/V Sync" error when using vdpau.
This is identical to upstream
https://code.mythtv.org/trac/ticket/12992
[Impact]
* When trying to play HEVC / h265 / x265
** Changed in: intel-microcode (Ubuntu Yakkety)
Assignee: (unassigned) => Dave Chiluk (chiluk)
** Changed in: intel-microcode (Ubuntu Xenial)
Assignee: (unassigned) => Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@lordbaco, are you still hitting this? Also please post your entire
oops next time, as I can't do much with what you've posted.
Also you might want to try moving up to the 4.4 kernel by installing
linux-image-lts-xenial on trusty *(I think that's the package name).
Marking this as fixed
Tested
http://launchpadlibrarian.net/325879940/intel-microcode_3.20170511.1~ubuntu17.04.0_amd64.deb
into Xenial+rolling-hwe. So far seems ok.
[0.00] microcode: microcode updated early to revision 0xba, date =
2017-04-09
[0.00] Linux version 4.8.0-56-generic (buildd@lcy01-33)
For those of you that really want Trusty fixed, please be aware, that
the preferred way to resolve this kind of issue is to upgrade the EFI
Firmware on your machine.
Also I just checked the source code for initramfs-tools, Yingying Zhao
(yingying-zhao) was wrong in
*** This bug is a duplicate of bug 1700373 ***
https://bugs.launchpad.net/bugs/1700373
Please see https://bugs.launchpad.net/ubuntu/+source/intel-
microcode/+bug/1700373/comments/12
Unfortunately it looks like 14.04 will not receive any new intel-
microcode updates.
For 14.04 users instead
Closing this as it appears to have been fixed in newer versions of the
4.8 kernel.
** Changed in: intel-microcode (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes comment #46 shows it was pushed to xenial, and I checked that it is
currently in updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647389
Title:
Regression: Live migrations can still
@Marc
I reviewed your proposed changes, and I really feel you should log an
error in the negative case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647389
Title:
Regression: Live migrations can
Just so you know I'm waiting for zesty release before uploading this. I
don't want to risk causing issues on the release media. Additionally
policy is to only push high priority bug fixes for the few weeks leading
up to release.
--
You received this bug notification because you are a member of
I just tested removing CVE-2016-5403-3.patch, but that didn't seem to do
it. I still don't understand how upsteam qemu functions with the
calculation the way it is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So I tested Len's patch, and it does seem to work.
However, I can't seem to understand why the below line is necessary,
when upstream qemu has virtually identical code, and does not need this
line. It almost makes me wonder if CVE-2016-5403-3.patch is incorrectly
decrementing the inuse counter
** Changed in: qemu (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: qemu (Ubuntu Xenial)
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/1647389
Title:
@Len
Can you provide links to the Rhel sources that you based your patch on
in order to provide more context and provide appropriate attribution in
the Ubuntu patch.
Thanks,
Dave.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: qemu (Ubuntu Xenial)
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/1647389
Title:
Regression: Live migrations can still crash after
** Tags added: sts-sponsor-chiluk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674680
Title:
Deprecated rfcomm.conf still mentioned
To manage notifications about this bug go to:
@hopem
Can you please add dep3 headers to the patch? I know it will going into
an LTS release, but for the sake of future reviews it would be helpful
to have.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: corosync (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: corosync (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Kai-Heng have you been able to make any progress on this? I think Tim
is simply waiting on a git branch or git send-email submission to the
kernel-team mailing list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- "Failed to initialize A/V Sync" error trying to play HEVC h.265 with vdpau
+ "Failed to initialize A/V Sync" error trying to play HEVC h.265 with vdpau
that supports hevc
** Description changed:
-
- When trying to play HEVC / h265 / x265 video, frontend fails and reports
While testing zesty it appears that the patch does not resolve issues
there, and will have to be rewritten for it and newer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673481
Title:
"Failed to
** Also affects: bluez (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
unity-settings-[4857]: failed to turn the kbd backlight off:
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface
'org.freedesktop.UPower.KbdBacklight' on object at path
/org/freedesktop/UPower/KbdBacklight
polkit-gnome-au[7926]: cannot open display: :0
FYI Sponsors patch needs to be cleaned up *(DEP3) and upstream work TBD.
I'll handle that. I just wanted to document the bug here so that we can
begin to see how many people may be affected.
Those of you that are affected don't add a comment. Instead select
"This bug affects you" above on this
** Also affects: mythtv (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: mythtv (Ubuntu Zesty)
Importance: Undecided
Assignee: Dave Chiluk (chiluk)
Status: New
** Also affects: mythtv (Ubuntu Aa-series)
Importance: Undecided
Status: New
This patch solves the issue by disabling de-interlacing for hevc/h265
material. This is not the final solution, but just a hack to keep all
our wives happy while the real solution is developed.
** Patch added: "lp1673481.xenial.debdiff"
l)
** Affects: mythtv (Ubuntu)
Importance: Undecided
Assignee: Dave Chiluk (chiluk)
Status: New
** Tags: amd64 apport-bug third-party-packages xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
@gnanasekarkas. Not that we know of.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328088
Title:
Kernel network namespace performance regression during rcu development
on kernels above 3.8
To
@Tim, When I checked the backport it was not a clean cherry-pick. As
you mentioned earlier there was some prerequisite patches that git
pulled in. I did not continue investigating, but I guess there should
only be a few. Either way the patches seem nvme
@Kai-Heng Feng, please make sure you
I can confirm Francois experience with my 950 pro. Although I saved one
or two watts. It's a bit hard to tell. However my PC states were
already reaching PC8 before this patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636322
Title:
upstart: ceph-all service starts before networks up
To manage notifications about this bug go to:
Updated bug description with SRU template and test case so that the
testcase can be updated as need be.
** Description changed:
+ [Impact]
+
+ * Libvirt migrations using tunnelled libvirt cause a failure to migrate
+ on the destination with error VQ 2 size 0x80 < last_avail_idx 0x9 -
+
@Alehandro, are your redhat/centos installations on qemu 2.6+? They are
working because the fix 4eae2a6+ the CVE is already available in that
version of qemu. IMHO, redhat and centos got lucky with that version of
QEMU. It has nothing to do with quality of distribution, and everything
to do
I have been able to create a smaller recreation environment for this.
1. Create a VM on shared storage solution. In my case NFS.
2. set start_libvirtd="yes" in /etc/default/libvirt-bin
3. systemctl restart libvirt-bin
4. virsh -c qemu+ssh://${FROM}/system migrate --live --p2p --tunnelled ${VM}
@Alejandro.
When trying with the live_migration_tunnelled = false, what are you
seeing in the /var/log/libvirt/qemu/.log. You may be
seeing a different issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: ubiquity (Ubuntu)
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/1646585
Title:
oem-config replaces /etc/resolv.conf symlink with a hard
** Also affects: linux (Ubuntu)
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/1639299
Title:
acpi_pad consumes 100% of resources
To manage notifications
@djao, sorry for the slow response. I hit pc8 briefly, but that's with
most everything tuned, and running nothing. Lots of applications seem
to be pretty power hungry for me. That's going to have to get tackled
by each upstream project before we integrate solutions into the distro.
@fthx.
@paelzer
AFAIK it should still be in Fix Committed. Moving it back there.
@Rob
It seems as if you are new to launchpad. Welcome. Bugs move to fix committed
when the fix lands in the -proposed archives. This is essentially the testing
pocket where it gives everyone a chance to help test to
** Attachment added: "1655225.output"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1655225/+attachment/4815622/+files/1655225.output
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655225
As I'm not sure what other testing I might be able to do to exercise
this code, I'm marking this verification-done.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I ran fio 4k randread and 4k randwrite tests from within the vm against
a qcow2. I was expecting performance degradation, but in every way the
patch seems to have made things slightly faster.
pre1655225.output = 2.0.0+dfsg-2ubuntu1.31
16655225.output = 2.0.0+dfsg-2ubuntu1.32
** Attachment
This looks like an issue in the nvidia driver with decoding
HEVC_MAIN_10.
See
https://devtalk.nvidia.com/default/topic/918822/hevc-main-10-profile-decoding-using-vdpau-unsupported-on-gtx-950-361-28-/
https://devtalk.nvidia.com/default/topic/940228/linux/vdpau-expose-hevc-
Yes, I'm currently working through attempting to bisect this issue.
Unfortunately I'm running into lots of issues getting iterations and
bounds functioning in a manner that allows me to reliably reproduce the
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
We have found another workaround for this in openstack clouds. Somehow
this issue seems to be exacerbated by live_migration_tunnelled being on.
You may be able to work around this by setting
live_migration_tunnelled = false
In your nova.conf or nova-compute.conf.
This is set by default for
Debdiff with updated version string now that I'm comfortable with the
upload.
** Description changed:
[Impact]
* VM running in QEMU with this message in qemu log
qemu-system-x86_64: /build/qemu-_D3HGx/qemu-2.0.0+dfsg/block.c:3491:
bdrv_error_action: Assertion `error >= 0' failed.
Uploading jpg a second time so it's obvious, and not missed in the maas
of auto-uploaded logs.
** Attachment added: "Awesome example of decorator corruption."
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1660388/+attachment/4810973/+files/corruption.jpg
--
You
Public bug reported:
After switching back from another user or after lock screen I
occasionally get corruption. This usually takes a few weeks after a
restart to reproduce. Might be related to nvidia drivers or mesa, or
compiz, or something else. Experienced this before recent update to
mesa
** Patch added: "lp1660372.zesty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cifs-utils/+bug/1660372/+attachment/4810905/+files/lp1660372.zesty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Completed debdiff
** Patch added: "lp1660362.zesty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/clock-setup/+bug/1660362/+attachment/4810904/+files/lp1660362.zesty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
merge cifs-utils with debian 2:6.6-5
** Affects: cifs-utils (Ubuntu)
Importance: Undecided
Assignee: Dave Chiluk (chiluk)
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Public bug reported:
Merge clock-setup with debian 0.131.
** Affects: clock-setup (Ubuntu)
Importance: Undecided
Assignee: Dave Chiluk (chiluk)
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
So far the fix appears to be safe, and I'm comfortable proceeding with
the SRU.
** Description changed:
[Impact]
* VM running in QEMU with this message in qemu log
qemu-system-x86_64: /build/qemu-_D3HGx/qemu-2.0.0+dfsg/block.c:3491:
bdrv_error_action: Assertion `error >= 0' failed.
@jan-huebner
Please educate yourself about the stable release process and development process
https://wiki.ubuntu.com/StableReleaseUpdates
https://wiki.ubuntu.com/UbuntuDevelopment
A regression was discovered in another component. This is the reason
for the delay. This is very uncommon, but
@alejandro-f
You need to run the virsh commands on the compute hosts before doing the
migration, customers should not be running the virsh commands.
Unfortunately, this looks to still exist upstream according to
https://lists.gnu.org/archive/html/qemu-devel/2016-12/msg02066.html, and
is related
Here's the proposed debdiff. I'm currently waiting on confirmation from
the customer of resolution, but that may never come, as it is so
difficult to reproduce this issue.
Also need to double check if this applies to the cloud archives.
** Patch added: "lp1655225.trusty.debdiff"
cts: qemu (Ubuntu)
Importance: Undecided
Assignee: Dave Chiluk (chiluk)
Status: New
** Tags: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1655225
Title:
Under heavy load qemu h
I have confirmation that this can be worked around by turning off memory
statistics via virsh before the migration. After migration memory
statistics can be turned back on safely.
The command to turn off memory statistics is
virsh dommemstat --live --period 0
The command to turn on memory
Marc we came to a similar conclusion. My backport of 104e70cae included
a partial backport of 4eae2a657d1ff5ada56eb9b4966e.
The rest of 4eae2 didn't apply. I was curious if perhaps the
VirtQueueElement isn't being properly initailized or possibly has some
dirty data, but I haven't figured that
** Tags removed: verification-needed
** Tags added: verification-done-yakkety
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634304
Title:
Unable to complete
I have confirmation from a user that 104e70cae does not resolve the
issue.
** Attachment removed: "First attempt at backport for 104e70cae"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1647389/+attachment/4795470/+files/lp1647389.xenial.debdiff
--
You received this bug notification
@Lukasz
Looking good so far. Appears resolved with 1.10.6-1ubuntu3.2.
Thanks,
Dave.
** Tags removed: verification-needed
** Tags added: verification-done
** Tags removed: verification-done
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member
I have created a ppa with the above fix that is available
https://launchpad.net/~chiluk/+archive/ubuntu/lp1647389
ppa:chiluk/lp1647389
If someone on copy for this bug has a way reliable way to test this
issue please attempt using the qemu out of my ppa.
Thank you,
--
You received this bug
kport for 104e70cae"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1647389/+attachment/4795470/+files/lp1647389.xenial.debdiff
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubunt
Clearing cache did not help. Trying firefox did not help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651165
Title:
Unable to change disk name using maas gui
To manage notifications about this
Looks like I'm getting errors from javascript out of my browser. I
suspect something is cached that shouldn't be. I'll clear cache and try
again.
jquery.js?v=2.1.1+bzr5544-0ubuntu1(16.04.1):3 GET
http://192.168.1.5/MAAS/static/assets/img/backgrounds/image-background-paper.png
404 (Not Found)
Did you refresh the page after changing the name? Also this maas is on
my local lan.
I created a video showing exactly what I'm doing.
https://www.youtube.com/watch?v=cJbHoVR6FBc=youtu.be
I checked the logs and couldn't find anything related to my operation.
FYI. This machine has been upgraded
Public bug reported:
Under Available disks and partitions, click the edit button then modify
the name.
Click save.
The changes never happen.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: maas 2.1.1+bzr5544-0ubuntu1~16.04.1
ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
Uname:
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1647389
Title:
Regression: Live migrations can still crash after CVE-2016-5403 fix
To manage notifications about this bug go to:
@arges
Looks like the yakkety SRU has been forgotten.
** Tags removed: verification-needed
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634304
Title:
** Description changed:
[Impact]
- * On Xenial after installing lvm2, you must reboot before you are able to
run vgcreate.
- * The package installer should be starting lvmetad.service.
- * $ sudo vgcreate localvg
- /run/lvm/lvmetad.socket: connect failed: No such file or directory
-
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1634304
Title:
Unable to complete install: 'Couldn't find hvm kernel for Ubuntu tree
To manage notifications
** Changed in: initramfs-tools (Ubuntu)
Status: New => Invalid
** Changed in: maas-images
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639202
Title:
Cannot
Updated changelog, and renamed patch so it's obvious that this patch
applies to be yakkety and zesty.
** Patch added: "lp1634304.zesty+yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1634304/+attachment/4788762/+files/lp1634304.zesty+yakkety.debdiff
** Tags
Updated changelog entry for debdiffs.
** Patch removed: "lp1634304.xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1634304/+attachment/4784828/+files/lp1634304.xenial.debdiff
** Patch removed: "lp1634304.yakkety.debdiff"
It will be fixed as soon as I can get sponsorship for my debdiffs.
** Changed in: virt-manager (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: virt-manager (Ubuntu Yakkety)
Status: New => Incomplete
** Changed in: virt-manager (Ubuntu Yakkety)
Status: Incomplete =>
101 - 200 of 1003 matches
Mail list logo
