*** This bug is a duplicate of bug 1013804 ***
https://bugs.launchpad.net/bugs/1013804
** This bug has been marked a duplicate of bug 1013804
package openvswitch-pki 1.4.0-1ubuntu1 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
--
This is still affecting Debian 7.2 as of today, is any workaround
available meantime?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat7 in Ubuntu.
https://bugs.launchpad.net/bugs/1031395
Title:
tomcat6 and tomcat7 are not
See CurrentDmesg.txt for lots of errors such as:
[ 1688.474887] Call Trace:
[ 1688.474914] [f8bae0f3] kvm_vcpu_ioctl+0x433/0x4d0 [kvm]
[ 1688.474924] [c108064f] ? wake_up_state+0xf/0x20
[ 1688.474931] [c10b9795] ? wake_futex+0x65/0x90
[ 1688.474937] [c10babed] ? futex_wake+0x13d/0x160
[
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1268906
Title:
cpu soft lockup running
Fixed upstream, thanks Eric! Marking as affecting Ubuntu, as even
trusty's qemu does not have that fix yet. For the record, lp:platform-
api uses posix timers for the sensor emulation, so running its tests
will reproduce this qemu problem (and verify its fix).
** Also affects: qemu (Ubuntu)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: juju-mongodb (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
** Changed in: juju-mongodb (Ubuntu)
Status: Confirmed = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
[MIR] juju-core, juju-mongodb
To manage
*** This bug is a duplicate of bug 1267393 ***
https://bugs.launchpad.net/bugs/1267393
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 13/01/14 23:26, Curtis Hovey wrote:
I think the status of juju-core is incorrect, or maybe we are
tracking the effort to put juju-core in main with bug
The attachment temp workaround to enable compilation and execution of
GHC and produced executables in foreign arch chroot seems to be a
patch. If it isn't, please remove the patch flag from the attachment,
remove the patch tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the
ubuntu-server team subscribed to bugmail.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-recaptcha in Ubuntu.
https://bugs.launchpad.net/bugs/1268909
Title:
[MIR] python-recaptcha and parsedatetime, b-d's of moin
To manage
ubuntu-server subscribed to bug-mail
** Changed in: python-scripttest (Ubuntu)
Assignee: Canonical Server Team (canonical-server) = James Page
(james-page)
** Description changed:
- python-scripttest, b-d of migrate
+ Rationale: b-d of migrate
+ Availability: In universe
+ Security: no
ubuntu-server subscribed to bug-mail
** Changed in: python-nine (Ubuntu)
Assignee: Canonical Server Team (canonical-server) = James Page
(james-page)
** Changed in: python-nine (Ubuntu)
Status: Incomplete = In Progress
** Description changed:
- python-nine, b-d of python-kajiki
+
Override component to main
python-scripttest 1.2-1 in trusty: universe/misc - main
python-scripttest 1.2-1 in trusty amd64: universe/python/optional/100% - main
python-scripttest 1.2-1 in trusty arm64: universe/python/optional/100% - main
python-scripttest 1.2-1 in trusty armhf:
Override component to main
python-nine 0.3.3-1 in trusty: universe/misc - main
python-nine 0.3.3-1 in trusty amd64: universe/python/extra/100% - main
python-nine 0.3.3-1 in trusty arm64: universe/python/extra/100% - main
python-nine 0.3.3-1 in trusty armhf: universe/python/extra/100% - main
Unfortunately it is still not working with these two patches. The
Unsupported syscall: 257 is gone, but now it fails on EINVAL. I attach
a little test C file which uses a timer. It works fine on x86 and a
real arm machine, but under QEMU I get:
$ gcc -o timer_test -Wall timer_test.c -lrt
$
I also see this behavior with byobu 5.60-0ubuntu1 on Ubuntu 13.10.
I can run byobu manually or automatically at login (using byobu-enable)
but the aliases and functions I have in a /etc/profile.d/lxc-helpers.sh
script aren't available to me.
Interestingly, when I run tmux it does have my profile
Verification failed; the upgrade does not remove the radosgw.conf
configuration so service still tries to use the obsolete upstart
configuration.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Had the same issue and a debugging session demonstrated that the problem occurs
while marshalling the environInfo management-certificate setting. It ended up I
was using the wrong path to the certificate (management-certificate-path
pointed to the cer file rather than the pem file).
I'd suggest
** No longer affects: cloud-utils (Ubuntu)
** Changed in: util-linux (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1244662
** Changed in: nss (Debian)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1024765
Title:
ipa-client-install fails at certutil stage because
** Changed in: juju-core
Status: Incomplete = Triaged
** Changed in: juju-core
Importance: Undecided = High
** Changed in: juju-core
Milestone: None = 1.17.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in
FYI Specifying the cipher with onopenssh-client 1:6.2p2-6ubuntu as:
ssh -c 3des-cbc targethost
works for me.
--
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/1254085
Title:
ssh
Public bug reported:
On my MAAS box running trusty:
In the MAAS UI, we created a node entry for a server, choosing IPMI and
passing the login credentials, IP for the BMC and the MAC address. On
saving the node, MAAS issued the IPMI command to turn the server on.
The server successfully powered
** Changed in: neutron (Ubuntu Trusty)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1257732
Title:
Wrong configuration file path in
Confirmed fixed in 3.13.0-2-generic, where in 3.13.0-1-generic it was
still failing.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/969299
Title:
apparmor prevents dpkg-divert and
** Changed in: maas (Ubuntu Trusty)
Status: Triaged = Fix Released
--
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/1255479
Title:
MaaS Internal Server Error 500 while parsing
Just noticed this in /var/log/tomcat7/
** Attachment added: localhost.2014-01-10.log
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1269073/+attachment/3948641/+files/localhost.2014-01-10.log
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
Public bug reported:
Starting from 20140109 onwards with the introduction of 3.13 kernel, we
are seeing test_tomcat_daemon failure in smoke testing.
Impacted jobs are:
http://ci.ubuntu.com/smokeng/trusty/server/amd64/20140114/6057/tomcat-server/666899/
and
http://ci.ubuntu.com/smokeng/trusty
I suspect that this points to some sort of problem with entropy
generation in /dev/random which is what gets used by default.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat7 in Ubuntu.
https://bugs.launchpad.net/bugs/1269073
SecureRandom generation is taking alot longer than normal, meaning that
the tomcat7 instance is not starting fully before the tests are run.
We saw this before but I can't remember what caused it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This was fixed in Debian 2.2.22-1. Since we're at 2.4.6-2ubuntu4 in
Trusty right now, I think it's more likely than not that this issues has
been fixed in a merge from Debian since, so I'm marking this bug as Fix
Released.
If I am wrong, please comment and reopen.
** Changed in: apache2 (Ubuntu)
So this might be an exceptional SRU. MRE was overshooting its purpose.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to iscsitarget in Ubuntu.
https://bugs.launchpad.net/bugs/1262712
Title:
[SRU] Backport iscsitarget 1.4.20.3+svn490
Actually, it seems that this bug no longer exists as of 2.4.6-2ubuntu4.
If I'm mistaken, please do comment and reopen.
** Changed in: apache2 (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Patch added: Updated the changelog with a reference to this bug report
https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1262712/+attachment/3948652/+files/iscsitarget-mre.debdiff
** Patch removed: iscsitarget-mre.debdiff
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ntp (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1268543
stderr actually is mapped to a pty. The problem seems to be that getty
can't set /dev/console as its controlling terminal because it's already
the controlling tty for init, which is in a different process group.
Thus getty ends up with no controlling tty, this is inherited by bash,
and thus bash
Quoting Seth Forshee (seth.forshee...@canonical.com):
stderr actually is mapped to a pty. The problem seems to be that getty
can't set /dev/console as its controlling terminal because it's already
the controlling tty for init, which is in a different process group.
Thus getty ends up with no
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.13 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
On Tue, Jan 14, 2014 at 08:42:06PM -, Serge Hallyn wrote:
Note that what you describe should also be the case if using a regular
container
sudo lxc-create -t ubuntu-cloud -n u1
sudo lxc-start -n u1
Is the process group of init somehow ending up different in the user
I've uploaded apache2 2.4.7-1ubuntu1. As
https://issues.apache.org/bugzilla/show_bug.cgi?id=54946#c14 suggests
that this was fixed in upstream 2.4.7, I'm marking this as Fix Released.
If this is incorrect, please explain and reopen.
For Saucy, I looked at reproducing the issue for a test case,
I think you should appoint the usb bus which according to your usb type, such
as:
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2
-device usb-ehci,id=usb1,bus=pci.0,addr=0x4
-device usb-hub,id=hub0,bus=usb.0,port=2
-device usb-tablet,id=input0,bus=usb.0,port=1
If the problem is a shortage of entropy in /dev/random, then I suggest
that tests replace /dev/random with a symlink to /dev/urandom instead.
urandom should be good enough for testing purposes, since we're not
testing the quality of entropy sources.
Does this resolve the issue?
--
You received
Thanks for the test case Martin. Problem confirmed.
The issue is that timer_create allows a number of different callback
mechanisms and I had only implemented the one I need.
Working on it now.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
devstack installation comes with openvswitch. Because openvswitch-datapath-dkms
won't work with current kernel from ubuntu 12.04.3.
http://javacruft.wordpress.com/2013/08/21/openvswitch-for-ubuntu-12-04-3-lts/
I log it as a bug. Devstack should use other packages.
** Also affects: devstack
** Changed in: qemu
Status: New = Confirmed
--
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/1256546
Title:
qemu-s390x-static: segmentation fault entering chroot
To manage
45 matches
Mail list logo
