** Branch linked: lp:~ubuntu-server-dev/neutron/icehouse
--
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/1307208
Title:
neutron-vpn-agent should wait for neutron-ovs-cleanup to
@Serghey
Fix Released means fixed in the development release, so that the next
release will contain the fix. We only backport high impact bugfixes to
existing stable releases. See
https://wiki.ubuntu.com/StableReleaseUpdates for rationale, policy and
procedure.
--
You received this bug
You have been subscribed to a public bug:
non riesco ad installare negli Aggiornamenti: common files used by both
the samba server and client
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: nautilus-share 0.7.3-1ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6
Uname:
** Package changed: nautilus-share (Ubuntu) = samba (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1307104
Title:
package samba-common-bin 2:3.6.18-1ubuntu3.1 failed to
This also means, that unless the Ubuntu maintainer fixes it either way,
then php-json has a rather important change in behaviour between 12.04
LTS and 14.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php-json in Ubuntu.
So the upstream json-c developers don't consider this a bug:
Oh, I see. You want json-c to validate that the input being parsed actually is
UTF-8. While that might seem reasonable to do at first glance, json-c has
historically supported something closer to exact, uninterpreted bytes for
** Changed in: ubuntu-release-notes
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1278466
Title:
[FFe] ceph firefly stable release
To manage
Thank you for following this up.
14.04 is just round the corner now, so it seems unlikely that any
further changes can be made now.
It sounds like json-c upstream are willing to have the behaviour in the
presence of the flag. Does this mean that php-json could use the flag by
default, and thus
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Setting Importance to Critical as this is an expected harmless operation
that will render the system essentially unreachable (and thus unusable)
for remote users (eg. just about all server users).
It seems to me
(confirmed on Trusty 1:6.6p1-2)
** Changed in: openssh (Ubuntu)
Status: New = Triaged
** Changed in: openssh (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
** Changed in: openssh (Ubuntu)
Assignee: (unassigned) = Robie Basak (racb)
--
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/1306877
Title:
sshd stops accepting new connections
Public bug reported:
After running 14.04 LTS through beta etc. I updated to teh latest this
morning and all was well. I then went into a running container, changed
it's sources.list to pint to the trusty repos and upgraded (the
container itself was running 13.10).
All went well, I restart the
openssh in Saucy (1:6.2p2-6ubuntu0.1) doesn't have this issue. Looks
like its upstart job doesn't set SSH_SIGSTOP, use expect stop, and
doesn't have the patch.
So I think the bug is in the patch applied in Trusty. Fix attached. It
seems to work. I'd appreciate a review of what I've done, though.
Public bug reported:
With Ubuntu 12.04 Precise and Cloudarchive Icehouse libvirt
1.2.2-0ubuntu11~cloud0 is not able to spawn a VM instance due to
incompatible apparmor profile with apparmor 2.8.0 (precise's version):
2014-04-11 10:27:10.997+: 8616: error : virCommandWait:2399 :
internal
** Changed in: openssh (Ubuntu)
Status: Triaged = Fix Committed
--
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/1306877
Title:
sshd stops accepting new connections after
When teh container is hung and i execute an lxc-stop (from a different
terminal) I see a:
mount: cannot mount block device nfs server/export/lxc-lib/container
name/rootfs read-only
Might be connected?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
environment: jamespage
machines:
11:
agent-state: started
agent-version: 1.18.1
dns-name: 10.5.0.26
instance-id: 24271ee3-b31d-4b7c-85ff-d027c03bd976
instance-state: ACTIVE
series: trusty
hardware: arch=amd64 cpu-cores=1 mem=2048M root-disk=10240M
22:
| 24271ee3-b31d-4b7c-85ff-d027c03bd976 | juju-jamespage-machine-11 | ACTIVE | -
| Running | james-page_admin_net=10.5.0.26, 10.5.0.15|
| 7ecdd56a-0531-41c1-b997-c5ebd8864d69 | juju-jamespage-machine-22 | ACTIVE | -
| Running | james-page_admin_net=10.5.0.27,
Public bug reported:
Most normal users won't come across this in normal juju operation, but
we do some odd things to test openstack-on-openstack in the Ubuntu
Server QA lab; specifically we add additional network interfaces on the
same neutron network to some types of service - neutron allocates
This might be due to the order they are returned in in the Nova or
Neutron API's I guess.
In the above example the configured eth0's are on 10.5.0.15 and
10.5.0.27
--
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-core (Ubuntu)
Importance: Undecided = Low
** Changed in: juju-core (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
CVE requested: http://www.openwall.com/lists/oss-security/2014/04/14/5
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rsync in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdisk (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gdisk in Ubuntu.
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to gdisk in Ubuntu.
https://bugs.launchpad.net/bugs/1303903
Title:
sgdisk zap/clear doesn't wipe all GPT tables
To manage notifications about this bug go to:
Public bug reported:
I noticed on 2 different systems that after upgrade from precise to latest
trusty VMs are crashing:
- in case of Windows VMs I'm getting BSOD with error message: A clock
interrupt was not received on a secondary processor within the allocated time
interval.
- On linux
You have been subscribed to a public bug:
Otherwise you'll get an error
sudo lxc-start -n mycontainer
lxc: call to cgmanager_move_pid_abs_sync(blkio) failed: invalid request
lxc-start: Could not find writable mount point for cgroup hierarchy 11 while
trying to create cgroup.
lxc-start: Device
** Tags added: patch
--
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/1306877
Title:
sshd stops accepting new connections after configuration reload
To manage notifications about
Does not seem to be a kernel issue.
** Package changed: linux (Ubuntu) = lxc (Ubuntu)
--
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/1306916
Title:
cgroup-lite should be added as an
** Changed in: juju-core
Status: New = Triaged
** Tags added: addressability openstack-provider
** Changed in: juju-core
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
I'm in favor of the approach suggested in comment #12, whereby we prompt
the user during the first install of MAAS, as to whether they want to
allow the install of non-free drivers for such cases where there are no
free ones available, e.g. HP example here. Once they answer, we point
out that the
Some responses to Dave's comments:
* Yes, it was done quickly and isn't perfect. It's a minimum useful set
of functionality to address a real use case and that improvements can be
added iteratively with the benefit of getting feedback from users in the
meanwhile.
* fastpath can be added without
I've posted a branch now that inserts the key directly into the yaml instead
of retrieving it via http.
Still working on a way to securely retrieve the udeb. The repo has a sha1 on
the udeb; just need to
work out how to validate the repo's sha1 now.
The whole point of having the key is to
Public bug reported:
How reproducible:
Steps to Reproduce:
1.Install the Ubuntu Server 12.04.4
2.Install the Keystone
3.Install the Glance
4.type glance-manage db_sync commands.
Actual results:
2014-04-14 10:40:37.697 15295 CRITICAL glance [-] AttributeError: 'NoneType'
object has no attribute
cgroup-lite isn't necessary at all now that we have cgmanager. Adding a
cgmanager task to investigate what's causing it to fail for you.
Can you please attach /var/log/upstart/cgmanager.log ?
** Also affects: cgmanager (Ubuntu)
Importance: Undecided
Status: New
--
You received this
Fixed under bug 1296912
** Changed in: heat (Ubuntu Trusty)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to heat in Ubuntu.
https://bugs.launchpad.net/bugs/1300010
Title:
heat has broken
So the problem here, as is shown by your kernel log is that your
container even though the rootfs upgraded properly is still using an old
config...
That old config doesn't mount pstore which is then causing the hang at
boot time which you are seeing.
LXC 1.0 fixes that issue going forward
** Package changed: apparmor (Ubuntu) = lxc (Ubuntu)
** Changed in: lxc (Ubuntu)
Importance: Undecided = High
** Changed in: lxc (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in
So I was informed that prompting for non-free during installation would
break unmanned installs of MAAS, which causes problems for our cloud
install plans. I'm all for supporting our commitment to non-free, but
at the end of the day, we're also committed to ensuring our users have a
great
Would it be a better approach to simply display a notice in the MAAS Web UI
and maybe when we do the initial MAAS setup, notifying the user that this
setting is enabled by default?
On Mon, Apr 14, 2014 at 9:24 AM, Robbie Williamson
robbie.william...@canonical.com wrote:
I'm in favor of the
You have been subscribed to a public bug:
sudo apt-get install lxc -y
Setting up lxc (1.0.2-0ubuntu2) ...
AppArmor parser error for /etc/apparmor.d/lxc-containers in
/etc/apparmor.d/abstractions/lxc/container-base at line 6: syntax error,
unexpected TOK_END_OF_RULE, expecting TOK_MODE
AppArmor
Example after a recent security upgrade:
http://paste.ubuntu.com/7250004/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to net-snmp in Ubuntu.
https://bugs.launchpad.net/bugs/1307544
Title:
user and group is re-created on every
Thanks. Ideally we would be able to get to the bottom of why libvirt
became unkillable, however since it isn't doing that regularly, we'll
have to mark this invalid meaning 'unreproducible.' Please do reply to
this if you see it happening again.
** Changed in: libvirt (Ubuntu)
Status:
Public bug reported:
The 'snmp' user and group is deleted and re-added on every package
upgrade (of at least snmpd); this causes unnecessary churn to /etc and
net-snmp is one of the few (only?) packages I'm aware of which does
this.
** Affects: net-snmp (Ubuntu)
Importance: Undecided
On 04/14/2014 08:45 AM, Adam Conrad wrote:
The whole point of having the key is to give you a trusty path to the
(u)debs, surely?
Yes - we need it for the udebs, and for setting up the repository in the
installed system. I'm still trying to work out the details on how to
verify the udebs given
** Also affects: glance (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: cloud-archive
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to glance in Ubuntu.
Yes, that works!
Many thanks for your help.
--
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/1307431
Title:
LXC containers fail to start when upgraded to 14.04 LTS
To manage
Looks like ash can support hexadecimal escaped strings - so that's a way
forward for me.
--
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/1305839
Title:
FFe: Support for Third Party
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1304167
Title:
syntax error, trusty beta-2 cloud image
For context, here's the branch I'm working on. It handles the insecure
key retrieval problem. I plan on handling the udeb problem by inserting
the keyring into the preseed, retrieving Release/Release.gpg for the
repo, using the keyring to verify the Release file, then using the sha
sums to verify
** Also affects: glance (Ubuntu Trusty)
Importance: Undecided
Status: Confirmed
** Changed in: glance (Ubuntu Trusty)
Importance: Undecided = Critical
** Changed in: glance (Ubuntu Trusty)
Status: Confirmed = Triaged
** Changed in: glance (Ubuntu Trusty)
Assignee:
To Robbie's point - yes, it makes no sense to make the install break
mysteriously when we can get it to work, any more so on a server or a
phone. It does make sense to flag in the UI when we have used drivers
outside of the normal Ubuntu kernel set. We're not installing
proprietary applications, I
So I was informed that prompting for non-free during installation would
break unmanned installs of MAAS, which causes problems for our cloud
install plans.
I'm trying to sort out what this means. Do we actually care that the
maas *controller* be installable with zero intervention? Why is
Curiosity fueled a couple of tests on this. In checking 2 common
scenarios, at least one use case confirms.
Aside from this confirmation, a bigger-picture question could be: in
principle, how is 53 being open and interactive by default any different
than 80, 22, or 137-139 being open and
On Mon, Apr 14, 2014 at 03:02:44PM -, Ryan Beisner wrote:
Aside from this confirmation, a bigger-picture question could be: in
principle, how is 53 being open and interactive by default any different
than 80, 22, or 137-139 being open and interactive by default, when
dnsmasq is not
Yep, I'm with ya Robie.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1306646
Title:
dnsmasq provides recursive answers to the Internet by default
To manage notifications about
This bug was fixed in the package openssh - 1:6.6p1-2ubuntu1
---
openssh (1:6.6p1-2ubuntu1) trusty; urgency=medium
* Upload from Debian git repository to fix a release-critical bug.
* Debconf translations:
- French (thanks, Étienne Gilli; closes: #743242).
* Never signal
Equivalent fix pushed for libvirt
** Changed in: libvirt (Ubuntu)
Importance: Undecided = High
** Changed in: libvirt (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Changed in: juju-core
Importance: Critical = High
--
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/1299802
Title:
upgrade-juju 1.16.6 - 1.18 (tip) fails
To manage
** Changed in: juju-core
Importance: Critical = High
--
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/1303880
Title:
Juju 1.18.0, can not deploy local charms without series
To
** Changed in: juju-core
Importance: Critical = High
--
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/1303697
Title:
peer relation disappears during upgrade of juju
To manage
** Summary changed:
- MAAS Server install fails when network is disconnected
+ MAAS Server ISO install fails when network is disconnected
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
** Changed in: juju-core
Importance: Critical = High
--
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/1303735
Title:
public-address change to internal bridge post juju-upgrade
** Changed in: juju-core
Importance: Critical = High
--
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/1306208
Title:
juju scp no longer allows multiple extra arguments to pass
FYI - related bug regarding missing dependencies in a no-network
scenario: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1172566
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Issue confirmed on Trusty daily ISO.
** Tags added: trusty
--
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/1172566
Title:
MAAS Server ISO install fails when network is disconnected
** Branch linked: lp:~smoser/ubuntu/precise/juju-core/cloud-tools
--
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/1306296
Title:
juju cannot downgrade to same major.minor version
** Branch linked: lp:~smoser/ubuntu/precise/juju-core/cloud-tools
--
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/1303880
Title:
Juju 1.18.0, can not deploy local charms without
** Branch linked: lp:~smoser/ubuntu/precise/juju-core/cloud-tools
--
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/1299802
Title:
upgrade-juju 1.16.6 - 1.18 (tip) fails
To manage
** Branch linked: lp:~smoser/ubuntu/precise/juju-core/cloud-tools
--
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/1303735
Title:
public-address change to internal bridge post
** Branch linked: lp:~smoser/ubuntu/precise/juju-core/cloud-tools
--
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/1261628
Title:
remove-* aliases for destroy-service and
** Branch linked: lp:~smoser/ubuntu/precise/juju-core/cloud-tools
--
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/1303697
Title:
peer relation disappears during upgrade of juju
** Branch linked: lp:~smoser/ubuntu/precise/juju-core/cloud-tools
--
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/1299588
Title:
LXC permission denied issue with 1.17.7
To manage
** Branch linked: lp:~smoser/ubuntu/precise/juju-core/cloud-tools
--
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/1306208
Title:
juju scp no longer allows multiple extra arguments
** Branch linked: lp:~smoser/ubuntu/precise/juju-core/cloud-tools
--
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/1248283
Title:
juju userdata should not restart networking
To
It has to do with automating the installation of MAAS environments,
which includes automating the installation of MAAS itself. In particular
this is important to our Openstack cloud-installer and for bootstrapping
'other' environments.
--
You received this bug notification because you are a
This bug was fixed in the package glance - 1:2014.1~rc2-0ubuntu1
---
glance (1:2014.1~rc2-0ubuntu1) trusty; urgency=medium
[ Chuck Short ]
* New upstream release candidate (LP: #1299055).
* debian/patches/sql_conn.patch: Refreshed.
* debian/glance-api.install: Install
This bug was fixed in the package lxc-android-config - 0.161
---
lxc-android-config (0.161) trusty; urgency=medium
[ Stéphane Graber ]
* e-enable cgmanager support. (LP: #1302174)
-- Oliver Grawert o...@ubuntu.com Mon, 14 Apr 2014 13:23:45 +0200
** Changed in:
More detail, see also attached tarball:
Apr 14 17:26:05 in-target: dpkg: error processing package
maas-region-controller-min (--configure):
Apr 14 17:26:05 in-target: subprocess installed post-installation script
returned error exit status 255
Apr 14 17:26:05 in-target: dpkg: dependency
so the bug here is actually in 'get_default_route_ip' of the postinst
for maas-region-controller-min and maas-region-controller.
They run with 'set -e' (which i'm never a fan of), and then have:
get_default_route_ip() {
while read Iface Destination Gateway Flags RefCnt Use Metric Mask MTU
** Branch linked: lp:~smoser/ubuntu/trusty/maas/lp-1172566
--
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/1172566
Title:
MAAS Server ISO install fails when network is disconnected
To
fix in lp:~smoser/ubuntu/trusty/maas/lp-1172566.
** Changed in: maas (Ubuntu)
Status: Confirmed = Triaged
--
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/1172566
Title:
MAAS
I would target this to a 1.18.2 if it existed.
This is a change in behavior from 1.16 to 1.18. If you just do:
juju-1.18 bootstrap -e amazon
I end up getting a i386 target. I have to do:
juju-1.18 bootstrap -e amazon --constraints=arch=amd64
for it to pick a amd64 (which was always the default
Problem is that the old php-json package conforms to the json standard,
and the new one does not. If someone went through the effort (we do not
have the resources, unfortunately) to make json-c conform to the json
standard with said flag, then yes - you could simply compile the package
with that
This bug was fixed in the package lxc - 1.0.3-0ubuntu3
---
lxc (1.0.3-0ubuntu3) trusty; urgency=medium
* Add a dependency on the new apparmor to make sure we have the new
parser around before we attempt to load a profile requiring the new
stanza support. (LP: #1304167)
--
This bug was fixed in the package cgmanager - 0.24-0ubuntu5
---
cgmanager (0.24-0ubuntu5) trusty; urgency=medium
* Add a 'stop on' to the upstart jobs (LP: #1307008)
-- Serge Hallyn serge.hal...@ubuntu.com Mon, 14 Apr 2014 00:13:44 -0500
** Changed in: cgmanager (Ubuntu)
Thanks, Scott. Further confirmation:
In previous no-network MAAS tests, the environment had no default
gateway set.
So, the missing dependency claim is debunked. This is not a dependency,
nor an ISO issue. Dependencies are indeed met on the Trusty ISO.
I confirmed this by successful
Take note: the missing dependency claim is debunked. Dependencies are
indeed met on the Trusty ISO. I confirmed this by successful
installation of MAAS from ISO on a machine with a fully configured ip
interface, but with no internet access. There is however, a separate
MAAS installation
This bug was fixed in the package heat - 2014.1~rc2-0ubuntu3
---
heat (2014.1~rc2-0ubuntu3) trusty; urgency=medium
* debian/heat-common.postinst: Fix failing autopkg test.
-- Chuck Short zul...@ubuntu.com Mon, 14 Apr 2014 13:36:05 -0400
** Changed in: heat (Ubuntu)
** This bug is no longer a duplicate of bug 1304167
syntax error, trusty beta-2 cloud image
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1307436
Title:
cloudarchive-icehouse:
In that case either apparmor will need to be added to the archive, or
libvirt in the archive will need to carry a patch on top of the trusty
version, since the apparmor policy language does not yet support
versioning.
** Changed in: libvirt (Ubuntu)
Importance: Undecided = High
** Also
** Description changed:
A recent kernel update (Apr 2013) has made it's way to U12.04.2 LTS
(approx June-Aug 2013) and has stopped the (default) behaviour of
automatically forwarding multicast traffic over virbr#. Some updates
the bridge subsystem now, by default, disable multicast
openvswitch-ipsec Depends on racoon from ipsec-tools. This comes from
openvswitch-- I thought openvswitch needed packaging updates for
demoting openvswitch-ipsec, but it does not. openvswitch-ipsec is
demoted.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
ipsec-tools 1:0.8.0-14ubuntu4 in trusty: main/net - universe
ipsec-tools 1:0.8.0-14ubuntu4 in trusty amd64: main/net/extra/100% - universe
ipsec-tools 1:0.8.0-14ubuntu4 in trusty arm64: main/net/extra/100% - universe
ipsec-tools 1:0.8.0-14ubuntu4 in trusty armhf: main/net/extra/100% - universe
Release note added for strongswan official support and ipsec-tools
community support.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to unbound in Ubuntu.
https://bugs.launchpad.net/bugs/1266066
Title:
[MIR] strongSwan
To manage
Public bug reported:
When using force user in combination with full_audit, the %U audit marco
get replaced with the wrong (forced) username. This has been fixed
upstream two years ago, but is not yet in precise.
https://bugzilla.samba.org/show_bug.cgi?id=8882
You be great to apply this to
Here you are.
$ sudo cat /var/log/upstart/cgmanager.log
cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0)
cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0)
cgmanager:do_move_pid_main: victim's cgroup is not under proxy's (p.uid 0)
$ ./change-override -c main strongswan strongswan-ike strongswan-plugin-dhcp
strongswan-plugin-eap-md5 strongswan-plugin-eap-mschapv2
strongswan-plugin-eap-peap strongswan-plugin-eap-radius
strongswan-plugin-eap-tls strongswan-plugin-eap-tnc strongswan-plugin-eap-ttls
strongswan-plugin-gmp
$ ./change-override -c main host libunbound2 libstrongswan strongswan-starter
libldns1
Override component to main
host 1:9.9.5.dfsg-3 in trusty amd64: universe/net/optional/100% - main
host 1:9.9.5.dfsg-3 in trusty arm64: universe/net/optional/100% - main
host 1:9.9.5.dfsg-3 in trusty armhf:
Public bug reported:
Failed Install
ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: snmpd 5.7.2~dfsg-8ubuntu1.1
ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
Uname: Linux 3.11.0-19-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Mon Apr 14
** Changed in: nova (Ubuntu)
Status: New = Triaged
** Changed in: nova (Ubuntu)
Importance: Undecided = High
** Changed in: nova (Ubuntu)
Assignee: (unassigned) = Chuck Short (zulcss)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
1 - 100 of 123 matches
Mail list logo
