I have installed qemu-slof from trusty and ran again:
qemu-slof:
Installed: 20151103+dfsg-1ubuntu1
Candidate: 20151103+dfsg-1ubuntu1
Version table:
*** 20151103+dfsg-1ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports xenial/main ppc64el Packages
100 /var/lib/dpkg/status
Same issue with -m 2048
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
To manage notifications about this bug go
Same issue. Stopped on the exact same spot.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1563887
Title:
qemu-system-ppc64 freezes on starting image on ppc64le
To manage
Yes. I only mounted (a different file) to troubleshoot what was going
on. The issue was happening before and after mounting. I have since
unmounted it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
Public bug reported:
qemu-system-ppc64 running on Ubuntu 16.04 beta-2 fails to start an image
as part of the certification process. This on an IBM ppc64le in PowerVM
mode running Ubuntu 16.04 beta-2 deployed by MAAS 1.9.1. There is no
error output.
ubuntu@alpine01:~$ qemu-system-ppc64 -m 256
In Ubuntu 14.04.4 running on the same hardware, the fix was to update
qemu-system-ppc from cloud-archive:kilo. This repository is only
supported on trusty and contains an earlier version of qemu-system-ppc
than what is available on xenial.
** Description changed:
qemu-system-ppc64 running on
I agree with the concerns about documentation.
Currently, maas-proxy is an optional package which does not depend on
the MAAS region server (or any other MAAS component). It's analogous to
squid-deb-proxy.
The squid-deb-proxy approach to security is to ship (in an
autogenerated/ directory, which
I've seen users complain that when we change this file it gets
overwritten automatically. (I guess we should also move it to /var, if
we're going to be automatically generating the configuration.)
Should every network MAAS knows about be included in the allow list? Or
is finer control needed?
--
s/when we change this/when they change that/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1379567
Title:
maas-proxy is an open proxy with no ACLs; it should add networks
ases, but
not in 4.1. Is there any plan to port this bug fix into releases
available on Ubuntu 14.04 LTS?
Mike
** Affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to sa
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Importance: Undecided => High
** Also affects: maas/1.10
Importance: Undecided
Status: New
** Also affects: maas/1.9
Importance: Undecided
Status: New
** Changed in: maas/1.10
Status: New =>
Thanks so much Brian, I tested it out of wily-proposed and it works great for
me.
Regards
-mjd
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1503034
Title:
Autofs 5.1.1-1ubuntu2
Ah, I just realized that you are running Xenial.
The best-supported way to run MAAS at this time is to run it on Trusty.
We won't have a Xenial compatible MAAS release until Xenial itself
releases.
** Changed in: maas
Status: Incomplete => Invalid
** Changed in: maas (Ubuntu)
I found this in the dpkg terminal log:
8712 Configurando python-formencode (1.3.0-0ubuntu1) ...
8713 Configurando python-netifaces (0.10.4-0.1build2) ...
8714 Configurando python-crypto (2.6.1-6build1) ...
8715 Configurando python-ecdsa (0.13-2) ...
8716 Configurando python-paramiko (1.15.3-1)
It's strange that you would hit this error. We should be able to import
is_validator; I can see that formencode has been installed. Can you
paste the output of these commands into the bug (my example output shown
for comparison):
$ python -c "from formencode import validators"
$ python -c "import
It has been added:
http://packages.ubuntu.com/xenial/php/php7.0
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1522422
Title:
PHP5 branch and PHP7 branch
To manage notifications
Hi Serge,
On Mo 04 Jan 2016 21:26:05 CET, Serge Hallyn wrote:
> Quoting Mike Gabriel (mike.gabr...@das-netzwerkteam.de):
>> Hi Serge,
>>
>> sorry for getting back to this so late.
>>
>> On Di 08 Dez 2015 17:08:58 CET, Serge Hallyn wrote:
>>
>
Hi Serge,
sorry for getting back to this so late.
On Di 08 Dez 2015 17:08:58 CET, Serge Hallyn wrote:
> Quoting Mike Gabriel (mike.gabr...@das-netzwerkteam.de):
>> today I worked on backporting available fixes for CVE-2015-1335 to LXC
>> 0.7.x (as found in Debian squeeze-lts).
Related is bug #1513198.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1331214
Title:
MAAS (amttool) cannot control AMT version > 8
To manage notifications about this bug go to:
@Serge, A workaround for me is to use "hypervisor default" in virt-
manager. I'm not sure what the equivalent is in virt-install, but maybe
using --cpu=host-model-only would be a workaround?
>From the man page:
Expose the host CPUs configuration to the guest. This enables
the
On my Trusty VM with "[x] Copy host CPU configuration" checked in virt-
manager, running 'sudo modprobe -r raid6_pq && sudo modprobe raid6_pq'
is enough to reproduce the kernel exception in dmesg (though I didn't
see it print "Segmentation Fault", so that may be somewhat of a red
herring).
Here's
I just tried again with two logical CPUs and the core set to "Westmere"
(I think that was the default), and didn't see the bug. So this seems
related specifically to "[x] Copy host CPU configuration" being checked.
Here's the /proc/cpuinfo from the "virtual Westmere" where it works:
, as well?
Greets,
Mike (aka sunweaver at debian.org)
** Patch added: "Backport fix for CVE-2015-1335 to LXC 0.7.x (Ubuntu 12.04 /
Debian squeeze-lts)"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1476662/+attachment/4529631/+files/CVE-2015-1335.patch
--
You received this bug no
Getting closer:
http://paste.ubuntu.com/13595538/
I still don't know exactly why this is happening, but I think I can get
it fixed within a day.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
I can confirm that I have replicated the issue in my local MAAS test
bed.
I'm seeing behavior such as this:
$ maas admin device claim-sticky-ip-address
node-ad58adcc-980a-11e5-a692-525400130e6f
Success.
Machine-readable output follows:
{
"macaddress_set": [
{
** Also affects: maas/1.9
Importance: Undecided
Status: New
** Changed in: maas/1.9
Status: New => Won't Fix
** Changed in: maas/1.9
Importance: Undecided => Critical
** Changed in: maas/1.9
Importance: Critical => Wishlist
--
You received this bug notification because
Thanks to LaMont's recent work on this for MAAS-next, we have the
opportunity to backport this fix to 1.9.0 before the codebase diverges
too much.
** Changed in: maas
Milestone: None => 1.9.0
** Also affects: maas/1.9
Importance: Undecided
Status: New
** Also affects: maas/trunk
As Jeff said, I believe this is fixed in MAAS 1.7.
I worked on a related race condition having to do with migrating MAAS-
managed BIND variables to the MAAS database.
If you are installing MAAS on a machine which will *not* host the MAAS
database, there is still somewhat of a race condition, in
** Changed in: vlan (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vlan in Ubuntu.
https://bugs.launchpad.net/bugs/1510711
Title:
if-pre-up.d/vlan should support brN.X interfaces
To manage
Public bug reported:
The released wily image preinstalls lxc, which breaks the assumption
that lxc's preinst packaging script makes:
It inspects the network to try to pick a 10.0.N.0 network that isn't
being used, with N starting at 3, so this appears to have picked
10.0.3.0 when it was
Unfortunately I just rolled 20 servers to 15.10 and this bug bit me big time.
Is there a workaround or estimate when
complete or do I need to roll back to 15.04. Is it possible to just install the
autofs from the 15.04 distro ?
--
You received this bug notification because you are a member of
** Tags removed: verification-done
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1468897
Title:
multipath creates binding for
The following shows that the 0.4.9-3ubuntu7.6 version of multipath-tools
does in fact ignore USB when creating the bindings. Marking as
verification-done.
ubuntu@cameron:~$ cat /etc/multipath/bindings
# This file was created by curtin while installing the system.
mpath0 1IBM IPR-0
Verification failed:
ubuntu@cameron:~$ apt-cache policy multipath-tools
multipath-tools:
Installed: 0.4.9-3ubuntu7.6
Candidate: 0.4.9-3ubuntu7.6
Version table:
*** 0.4.9-3ubuntu7.6 0
500 http://ports.ubuntu.com/ubuntu-ports/ trusty-proposed/main ppc64el
Packages
100
Yes, that seems to be the argument. I would like to understand why it
seems to be that many environments are set up with a forwarder that does
not support DNSSEC. (is this by choice? is it a particular vendor, or
old DNS server which does not forward the queries properly?
misconfigured firewall
Adding the `bind` package. MAAS simply uses the value from the BIND
configuration files in order to determine what to configure in MAAS. So
this cannot change in MAAS unless a decision is made in BIND, or the
value is left out of the configuration file by default, allowing MAAS to
make its own
I think the bug here is that we display an unwieldy stack trace rather
than a nice error message.
Running "sudo maas " may cause this bug to occur, since the
~/.maascli.db will be created by the root user, rather than the
currently-logged-in user.
--
You received this bug notification because
Tested multipath-tools version Installed: 0.4.9-3ubuntu7.5 from the
proposed repository in Trusty. The test shows the problem resolved.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
a recent bug in the cloud-images service caused the metadata to have an
incorrect path, which meant that simplestreams got a 403 when requesting an
image. However it swallowed that error and apparently uploaded 384 bytes of
something, possibly an error HTML page, as the
Public bug reported:
package failed to install during do-release-upgrade from vivid to wily
happened immediately after https://bugs.launchpad.net/ubuntu/+source
/isc-dhcp/+bug/1485089
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: maas-dhcp 1.7.6+bzr3376-0ubuntu2~15.04.1
Updated information. It seems the issue only comes about with USB 3.0
devices. USB 2.0 devices do not get lumped in with multipath upon
detection.
dmesg output from inserting a USB 3.0 device and then a USB 3.0 device.
Both into USB 3.0 ports:
[ 223.050845] usb 4-4: new SuperSpeed USB device
I tested by installing bind9 on Trusty, then installing maas
1.7.6+bzr3376-0ubuntu2~14.04.1.
I verified that the forwarders were properly migrated to the MAAS
configuration, as long as at least one cluster interface was set to be
managing DNS.
The forwarders are migrated into the MAAS database,
OK, I hate to be so stupid, but I need some help and can't seem to
locate anyone knowledgeable so far:
In 10-ssl.conf I added: ssl_protocols = !SSLv2 !SSLv3 (to no avail so i
think I am not patched)
Would appreciate some helpful comments / guidance please...
I did a fresh install of 12.04.5 on
** Also affects: python-glance-store (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: python-glance-store (Ubuntu)
** Also affects: glance-store
Importance: Undecided
Status: New
** Changed in: glance-store
Assignee: (unassigned) = Mike Fedosin (mfedosin
I tested the fix; looks good! Thanks.
--
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/1462139
Title:
curtain fails with Device is busy error during unmount
To manage notifications
Public bug reported:
The package description is incorrect.
Precise's version of the package had check_linux_raid in it.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nagios-plugins-standard 1.5-3ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18
Uname: Linux
Public bug reported:
Release: Ubuntu 14.04.2 installed on IBM Power 8 (Tuleta)
kernel: 3.16.0-43-generic
Arch: ppc64le
When trying to run qemu-system-ppc64 to create a new VM, we get the
following error:
qemu: hardware error: qemu: could not load bios image 'ppc_rom.bin'
ppc_rom.bin is located
Nevermind, it was pilot error on my part. I redid the directions and can
both log in directly and ssh via port 8022. Good to see my track record
of finding every possible way of failing remains intact...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Does the image http://releases.ubuntu.com/15.04/ubuntu-15.04-snappy-
amd64-generic.img.xz have this fix? Still can't login after spinning up
the image using kvm. Is there a workaround to login based on the kvm
directions at https://developer.ubuntu.com/en/snappy/start/? Please
advise. Thanks.
--
Public bug reported:
Using a 14.04.2 host, running a 15.04 guest, uvt-kvm wait waits forever
because systemd goes straight to runlevel 5
This is fixed in uvtool upstream by
http://bazaar.launchpad.net/~uvtool-dev/uvtool/trunk/revision/94
and I'd like that fix to be SRU'd into Trusty.
**
Bug still exists. I encountered it just now attempting to generate a
trusty image on a trusty host. Adding addpkg = linux-image-generic to
my /etc/vmbuilder.cfg file allowed the process to complete.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
On a system with a multipath configuration, multipath bindings are being
created for removable(USB) drives rendering them inaccessible as normal
removable drives.
in this case, the usb drive is detected as /dev/sdi:
# lsblk|grep -A2 sdi
sdi8:128 1
After following this post: https://www.redhat.com/archives/dm-
devel/2008-September/msg00235.html
I have prepended the following to /lib/udev/rules.d/95-multipath.rules:
#Weed out the linear map.
KERNEL==dm-*, PROGRAM==/sbin/dmsetup table -j %M -m %m, RESULT==*linear*,
OPTIONS=last_rule
# And
I have tried the latest curtin-common and python-curtin from the wily
repositories running on 14.04.2:
#leftyfb@maaster[0]:~$ apt-cache policy curtin-common
curtin-common:
Installed: 0.1.0~bzr214-0ubuntu1
Candidate: 0.1.0~bzr214-0ubuntu1
Version table:
*** 0.1.0~bzr214-0ubuntu1 0
I have tried the latest curtin-common and python-curtin from the wily
repositories running on 14.04.2:
#leftyfb@maaster[0]:~$ apt-cache policy curtin-common
curtin-common:
Installed: 0.1.0~bzr214-0ubuntu1
Candidate: 0.1.0~bzr214-0ubuntu1
Version table:
*** 0.1.0~bzr214-0ubuntu1 0
Public bug reported:
[Issue]
ceilometer 1.0.13 displays same error message as bug 1421663.
root@controller-1:~# ceilometer-dbsync
2015-06-05 07:53:55.970 8367 CRITICAL ceilometer [-] AttributeError: 'NoneType'
object has no attribute 'find'
2015-06-05 07:53:55.970 8367 TRACE ceilometer
I tried following the above workaround on the IBM Power 8 twice on new
deployments. Attached is the log.
** Attachment added: multipath.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371634/+attachment/4409977/+files/multipath.log
--
You received this bug notification because you
Public bug reported:
This command fails:
root@controller-1:~# glance image-create --name cirros-0.3.4-x86_64 --file
/tmp/images/cirros-0.3.4-x86_64-disk.img --disk-format qcow2 --container-format
bare --visibility public --progress
usage: glance [--version] [-d] [-v] [--get-schema] [--timeout
** Changed in: tgt (Ubuntu)
Status: In Progress = Confirmed
** Changed in: tgt (Ubuntu)
Assignee: ubuntudotcom1 (ubuntudotcom1) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tgt in Ubuntu.
This should have been fixed with the following commit to the packaging
branch:
https://code.launchpad.net/~mpontillo/maas/packaging-python-apt-
fix/+merge/255265
** Branch linked: lp:~mpontillo/maas/packaging-python-apt-fix
** Changed in: maas (Ubuntu)
Status: New = Fix Committed
--
I thought we recently fixed this. Either the version under test doesn't
have the fix yet, or we missed the fix for some subset of MAAS packages.
I will check tomorrow.
** Changed in: maas (Ubuntu)
Assignee: (unassigned) = Mike Pontillo (mpontillo)
--
You received this bug notification
This also affects freeradius-postgresql
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeradius in Ubuntu.
https://bugs.launchpad.net/bugs/823096
Title:
package freeradius-mysql 2.1.8 dfsg-1ubuntu1 failed to
install/upgrade:
I hit this problem today, and it turned out to be a non-MAAS bug.
I was trying to configure a Trusty host with VMware Workstation *and*
LXCs sharing the same network.
It turns out that the combination of VMware plus Linux bridge interfaces
have a bug: if I set up the VM network to be bridged to
I attempted to fix this, but haven't gotten anywhere. I am seeing the
following errors:
Removing maas-region-controller (1.8.0~beta2+bzr3777-0ubuntu1) ...
* Stopping web server apache2
*
I think this is a bug with dbconfig-common. It looks like Zbbix is still
having this issue:
https://support.zabbix.com/browse/ZBXNEXT-2587
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Branch linked: lp:~mpontillo/maas/packaging-fix-db-purge
** Changed in: maas
Importance: Medium = High
** Changed in: maas
Assignee: (unassigned) = Mike Pontillo (mpontillo)
** Changed in: maas
Milestone: None = 1.8.0
** Changed in: maas
Status: New = Triaged
--
You
I just saw this one again. I found a relevant discussion here:
https://lists.alioth.debian.org/pipermail/dbconfig-common-
devel/2006-September/000627.html
Here's the relevant quote from Sean Finney (the maintainer of dbconfig-
common):
i can reproduce your problem... looking in my postgres
*** This bug is a duplicate of bug 1044559 ***
https://bugs.launchpad.net/bugs/1044559
Note: If you try to purge the database, it actually fails in this case,
and the database is left intact.
See comments on bug #1044559.
** Also affects: maas
Importance: Undecided
Status: New
**
Thank you for the suggestions Gary. I realized that my problem is caused
by the router firmware. Basically, they introduced loopback blocking and
I couldn't connect from the same network even using the external IP.
--
You received this bug notification because you are a member of Ubuntu
Server
I just saw this exact behavior while using a 1.8.0 development package
on Trusty. Not sure what the correct process to reopen a bug is, but I
think this either wasn't fully fixed, or there has been a regression.
** Also affects: maas
Importance: Undecided
Status: New
--
You received
Public bug reported:
got this error while installing packages through software updater
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: cinder-volume 1:2014.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion:
*** This bug is a duplicate of bug 1428647 ***
https://bugs.launchpad.net/bugs/1428647
** This bug has been marked a duplicate of bug 1428647
regiond service crashes with the database system is starting up
--
You received this bug notification because you are a member of Ubuntu
Server
** Tags removed: canonistack rbd volume
** Tags added: drivers
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1028718
Title:
nova volumes are inappropriately clingy for ceph and
** Changed in: maas
Assignee: (unassigned) = Mike Pontillo (mpontillo)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1423613
Title:
maas needs to support systemd for Ubuntu
Hello,
Not sure it is the same problem here, but I cannot connect to my machine if go
through NAT.
If I connect directly from LAN everything works, but if I use the external IP,
then I get connection reset after debug1: SSH2_MSG_KEXINIT sent.
Client and server is the same machine. I tried to
February 2015 at 19:07, Mike smart...@gmail.com wrote:
Hello,
Not sure it is the same problem here, but I cannot connect to my machine
if go through NAT.
...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https
Public bug reported:
This is using the MAAS 1.8 experimental branch.
A race condition is possible in which a persistent exception is thrown
when hitting http://server/MAAS, if maas-regiond starts before
postgresql. (that is, even if you start postgresql, the MAAS web
interface never recovers.)
** Description changed:
This is using the MAAS 1.8 experimental branch.
A race condition is possible in which a persistent exception is thrown
when hitting http://server/MAAS, if maas-regiond starts before
postgresql. (that is, even if you start postgresql, the MAAS web
interface
** Changed in: cinder
Status: In Progress = Triaged
** Changed in: cinder
Assignee: Tony Breeds (o-tony) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
** Changed in: cinder
Milestone: kilo-2 = None
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1313935
Title:
tenant is required for quota-update but not for quota-show
To manage
** Tags added: low-hanging-fruit
** Changed in: cinder
Assignee: Thang Pham (thang-pham) = (unassigned)
** Changed in: cinder
Milestone: kilo-1 = kilo-2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
The above patch is what I'm running locally against Icehouse. It does
not seem that complicated, unless I am missing something major. I did
briefly look at the cherry-pick, and that is quite a bit different. The
the above is working well for us.
--
You received this bug notification because
** Changed in: cinder
Milestone: None = kilo-1
** Changed in: cinder
Status: New = Triaged
** Changed in: cinder
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
Either running the cron job as root or allowing www-data to read the
apache log files are bad ideas. Instead you want to create a new user
and add it to the www-data and adm groups and make the cron job execute
as that user. I called mine awstats:
useradd awstats usermod -a -G www-data awstats
This bug still remains 6 months later. I just wasted 2 days trying to
figure out why this package I was using wasn't working. Please fix this
for 32-bit users.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
+1 on would like this backported to Icehouse.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keystone in Ubuntu.
https://bugs.launchpad.net/bugs/1381768
Title:
AttributeError: 'module' object has no attribute
Public bug reported:
line 9 of maas-region-controller.postrm tests for the existence of '/etc
/dbconfig-common/maas.conf', which will not exist. the file that gets
created is instead maas-region-controller.conf. since that test is never
true, the call to dbc_go to do the postrm.pgsql stuff never
Same error here, seemed to be fine on -69, but doesn't build on -70.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1379201
Title:
openvswitch-datapath-dkms
he signature of ip_select_ident changed from -69 to -70.
It went from (struct sk_buff *skb, struct dst_entry *dst, struct sock
*sk) to (struct sk_buff *skb, struct sock *sk, int segs).
Unfortunately I don't know enough about openvswitch internals to change
the call, but the calls are made in
The backported patch that caused this was
https://lkml.org/lkml/2014/8/8/861
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1379201
Title:
openvswitch-datapath-dkms
Public bug reported:
Our configuration files may be obsolete.
Also there is a warning about file permissions in /var/lib/spamassassin (?)
that I haven't checked yet.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: spamassassin 3.4.0-1ubuntu1
ProcVersionSignature: Ubuntu
FWIW, this happened again just now with an earlier (non PPA I guess)
version of maas-dhcp:
Setting up isc-dhcp-server (4.2.4-7ubuntu12) ...
isc-dhcp-server start/running, process 11190
isc-dhcp-server6 stop/pre-start, process 11233
Setting up maas-dhcp (1.5.2+bzr2282-0ubuntu0.2) ...
stop: Unknown
I need to amend comment #39, moving from 3.13.0-30 to 3.13.0-27 did not
eliminate the problem. It would seem that it takes a couple of hours
following a reboot for the symptoms to manifest with 3.13.0-27.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
I believe I have the same problem, place a guest under any amount of
load, let's say 'yum upgrade' and the network stack goes out to lunch
for 1-5 seconds. Here is a sample of the ping statistics (host to
guest) from doing such an operation on a 3.13.0-30.55 kernel:
213 packets transmitted, 213
I can confirm that rolling back to 3.13.0-27 from 3.13.0-30 alleviated
my symptoms.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1307473
Title:
guest hang due to missing clock
Public bug reported:
The GlanceMirror class has no callback to provide progress updates on
image downloads. OS images are often large enough (and you may be
syncing several images) that this presents a serious UX problem during
which a user (or client program) of simplestreams will not be able
Public bug reported:
The GlanceMirror class has a hard-coded filter for items to be
downloaded.
Anyone using it directly or via the script in
tools/sstream-mirror-glance to load images into an openstack cloud
will end up with a large number of images, at least one for each of
the available
Update: it works if I change the cipher (to blowfish, in this instance).
Doesn't work using aes128.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/281882
Title:
ssh hangs in
I'm seeing this same issue on Ubuntu 14.04 LTS using OpenSSH 1.0.1f.
mab@source:~$ ssh -v mtaxxx
OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to mtaxxx [ip address
Thanks for testing. I had thought I'd used purge via a separate script,
but now that I look back I'm not sure.
My apologies for the bug spam
** Changed in: maas (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team,
1 - 100 of 322 matches
Mail list logo
