Hi,
Could the people affected please explain what is not working? Using
'exec' is deprecated and should be replaced with 'extend'. Was this
option tried and you still failed to see results?
Also attaching some example configurations using the 'extend' feature
would be helpful in pinpointing this
** Description changed:
- On Karmic (alpha 4 plus updates), changing the nsswitch.conf 'passwd'
- field to anything with 'ldap' as the first item breaks the ability to
- become root using 'su' and 'sudo' as anyone but root.
+ SRU Request:
+
+ [Impact]
+ As heavily outlined in the amount of commen
** Description changed:
SRU Request:
[Impact]
As heavily outlined in the amount of comments in this bug the impact is
detrimental to both community and enterprise users alike.
[Development Fix]
- Howard Chu released a patch in #73 which was later confirmed in #106 & #108
as a resol
** Branch linked: lp:~adam-stokes/ubuntu/quantal/libgcrypt11/libgcrypt-
fix-423252
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/423252
Title:
NSS using LDAP+SSL breaks setuid
Precise debdiff for SRU
** Patch added: "libgcrypt11_1.5.0-3ubuntu1.precise.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/423252/+attachment/3149496/+files/libgcrypt11_1.5.0-3ubuntu1.precise.debdiff
--
You received this bug notification because you are a member of Ubuntu
Serve
** Patch added: "Oneiric-proposed debdiff"
https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/423252/+attachment/3150693/+files/libgcrypt11_1.5.0-1ubuntu0.1.oneiric.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lib
natty-proposed debdiff
** Patch added: "libgcrypt11_1.4.6-4ubuntu2.1.natty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/423252/+attachment/3150719/+files/libgcrypt11_1.4.6-4ubuntu2.1.natty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Lucid-proposed debiff
** Patch added: "libgcrypt11_1.4.4-5ubuntu2.1.lucid.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/423252/+attachment/3161716/+files/libgcrypt11_1.4.4-5ubuntu2.1.lucid.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server
I'm not able to reproduce your issue exactly, but here is information
which shows that the snmp extend functionality is available in latest
lucid.
zef@lucid:/tmp$ ps -ef |grep nfsd
root 1152 2 0 13:29 ?00:00:00 [nfsd4]
root 1156 2 0 13:29 ?00:00:00 [nfsd]
root
Michael,
Let me do some more investigating on this and I'll get back to you.
Thanks for testing
Adam
--
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/496922
Title:
Ubuntu snmpd pac
Michael,
You could alter your previous query to resemble something like the
following:
zef@lucid:/tmp$ snmpget -v1 -c stokescanonical localhost
'NET-SNMP-EXTEND-MIB::nsExtendResult."top_lists"'
NET-SNMP-EXTEND-MIB::nsExtendResult."top_lists" = INTEGER: 9
Thanks,
Adam
--
You received this bug
** Changed in: lsb (Ubuntu)
Milestone: None => ubuntu-12.04.1
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/683640
Title:
status_of_proc is returning incorrect error code
To man
** No longer affects: bind9 (Ubuntu Lucid)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/683640
Title:
status_of_proc is returning incorrect error code
To manage notifications about
** No longer affects: dovecot (Ubuntu Lucid)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/683640
Title:
status_of_proc is returning incorrect error code
To manage notifications abo
** No longer affects: bind9 (Ubuntu Natty)
** No longer affects: bind9 (Ubuntu Oneiric)
** No longer affects: bind9 (Ubuntu Precise)
** No longer affects: bind9 (Ubuntu Quantal)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 i
** No longer affects: dovecot (Ubuntu Natty)
** No longer affects: dovecot (Ubuntu Oneiric)
** No longer affects: dovecot (Ubuntu Precise)
** No longer affects: dovecot (Ubuntu Quantal)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** No longer affects: openbsd-inetd (Ubuntu Oneiric)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/683640
Title:
status_of_proc is returning incorrect error code
To manage notificat
** No longer affects: openbsd-inetd (Ubuntu Lucid)
** No longer affects: openbsd-inetd (Ubuntu Natty)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/683640
Title:
status_of_proc is r
** No longer affects: openbsd-inetd (Ubuntu Precise)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/683640
Title:
status_of_proc is returning incorrect error code
To manage notificat
** No longer affects: openbsd-inetd (Ubuntu Quantal)
** No longer affects: openvpn (Ubuntu Lucid)
** No longer affects: openvpn (Ubuntu Natty)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net
** No longer affects: spamassassin (Ubuntu Precise)
** No longer affects: openvpn (Ubuntu Oneiric)
** No longer affects: openvpn (Ubuntu Precise)
** No longer affects: openvpn (Ubuntu Quantal)
** No longer affects: rsync (Ubuntu Lucid)
** No longer affects: rsync (Ubuntu Natty)
** No longer a
This problem needs additional patches that can be found in my related
branch. My understanding is that testing with that patched autofs5 is
proven positive. I will have an SRU written up once I receive a final
confirmation today.
** Branch linked: lp:~adam-stokes/ubuntu/lucid/autofs5/null-cache
The merge proposal has been confirmed and verified on lucid.
** Description changed:
Binary package hint: autofs5
+
+ [Impact]
+ Running reload autofs on a release with this issue creates automount maps and
can cause the automounter to hang. This will prevent logins via ssh for users
(due to
It doesn't look like your OID is correct, below is the one used for NET-
SNMP-EXTEND-MIB:
zef@lucid:~$ snmpwalk -v1 -c stokescanonical localhost .1.3.6.1.4.1.8072.1.3.2
NET-SNMP-EXTEND-MIB::nsExtendNumEntries.0 = INTEGER: 1
NET-SNMP-EXTEND-MIB::nsExtendCommand."top_lists" = STRING: /bin/sh
NET-SNM
For now I'll set this to invalid as I've had no issues getting external
scripts to execute through NET-SNMP-EXTEND-MIB
** Changed in: net-snmp (Ubuntu)
Status: Confirmed => Fix Released
** Tags added: verification-done-lucid
--
You received this bug notification because you are a member
We are using juju-core package name now so there is no need for this
packaging request :)
** Changed in: juju-core (Ubuntu)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
ht
xnox, there is this bug: https://bugs.launchpad.net/juju-
core/+bug/1547665
--
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/1545913
Title:
[FFe] juju-core 2.0
To manage notificati
** Description changed:
The juju team is requesting an FFE for juju-core. Juju2 represents API
changes and new features and bugfixes for juju. We are NOT requesting a
place on any image for xenial. This FFE is intended to cover the
acceptance of the updated juju-core package, as well as t
After reviewing this bug again I've outlined a possible course of
action:
a) Revert global_init patch in all supported distro's
b) Lucid users continue to use the nscd workaround.
c) Precise, Quantal, etc - rebuild gnutls without --with-libgcrypt in order to
make use of nettle.
Unfortunately, t
Public bug reported:
1. Description of the problem:
On 12.04, for package 'puppet', the fix (contained in version
2.7.11-1ubuntu2.1) for CVE-2012-3867 [1] involves validating TLS
certificate CSR field (Common Name) for “weird” characters. However, the
check is too restrictive and is causing negot
Thanks Howard,
I'll get this reviewed and tested this week.
Adam
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/423252
Title:
NSS using LDAP+SSL breaks setuid applications lik
** No longer affects: eglibc (Ubuntu)
** No longer affects: libnss-ldap (Ubuntu)
** No longer affects: sudo (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/423252
Title:
** Patch added: "walinuxagent_1.2-0ubuntu1~12.04.2.precise.debdiff"
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1101371/+attachment/3507905/+files/walinuxagent_1.2-0ubuntu1%7E12.04.2.precise.debdiff
--
You received this bug notification because you are a member of Ubuntu
Serve
** Patch added: "walinuxagent_1.2-0ubuntu1~12.10.2.quantal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1101371/+attachment/3507909/+files/walinuxagent_1.2-0ubuntu1%7E12.10.2.quantal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Serve
** Patch added: "walinuxagent_1.3-0ubuntu1.raring.debdiff"
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1101371/+attachment/3507912/+files/walinuxagent_1.3-0ubuntu1.raring.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is sub
** Description changed:
Guys,
- During my new tests, I tried to create two nodes simultaneously (both
+ During my new tests, I tried to create two nodes simultaneously (both
via DHCP + PXE, not by clicking "+Add node") and I hit this problem:
- Same MAC Address, two different IPs:
+
** Patch added: "isc-dhcp_4.1.ESV-R4-0ubuntu5.6.1.precise.debdiff"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3631196/+files/isc-dhcp_4.1.ESV-R4-0ubuntu5.6.1.precise.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, whic
** Description changed:
- Guys,
-
- During my new tests, I tried to create two nodes simultaneously (both
- via DHCP + PXE, not by clicking "+Add node") and I hit this problem:
+ [Impact]
+ During my new tests, I tried to create two nodes simultaneously (both via
DHCP + PXE, not by clicking "
Looks like upstream has a pending release to fix this issue positive
testing results from community.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1068145
Title:
Fix for CVE-2012-38
** Patch removed: "isc-dhcp_4.1.ESV-R4-0ubuntu5.6.1.precise.debdiff"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3631196/+files/isc-dhcp_4.1.ESV-R4-0ubuntu5.6.1.precise.debdiff
** Patch removed: "isc-dhcp_4.2.4-1ubuntu10.1.quantal.debdiff"
https://bugs.launchpad
** Patch added: "isc-dhcp_4.2.4-1ubuntu10.3.quantal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3631785/+files/isc-dhcp_4.2.4-1ubuntu10.3.quantal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscri
Re: #6, what is the context of 'Resolved'? Anything you need from me to
make sure this issue is actively reviewed?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent in Ubuntu.
https://bugs.launchpad.net/bugs/1158465
Title:
** Changed in: maas (Ubuntu)
Status: Incomplete => Invalid
--
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/1069570
Title:
1 MAC Address, two IPs - DNS is "out of sync" with DHCP
This also contains a small change to 00List to fix previous changelog
entry and not have its patch reverted.
** Patch removed: "isc-dhcp_4.1.ESV-R4-0ubuntu5.8.precise.debdiff"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3631784/+files/isc-dhcp_4.1.ESV-R4-0ubuntu5.8.
** Patch removed: "isc-dhcp_4.1.ESV-R4-0ubuntu5.8.precise.debdiff"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3638900/+files/isc-dhcp_4.1.ESV-R4-0ubuntu5.8.precise.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
This also contains a fix from the previous changelog to modify an
apparmor profile. Patch was removed and applied directly to debian
/apparmor-profile.dhcpd
** Patch added: "isc-dhcp_4.1.ESV-R4-0ubuntu5.8.precise.debdiff"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/
Jeff,
I've been searching through the documentation on puppet labs wiki but I
am unable to find a tentative release date for 3.2.0. Do you have that
information and if the date is set do you mind sharing that with me?
Thank you,
Adam
--
You received this bug notification because you are a membe
Jeff,
Thanks for the quick response. I'll make sure to monitor the mailing
list.
Thanks again,
Adam
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1068145
Title:
Fix for CVE-2012-3
3.2.1 is out, once it makes it way into Debian and then Ubuntu archive
I'll work on getting a possible backport accepted for Precise, Quantal
and Raring.
Thanks
Adam
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
htt
** Description changed:
+ [Impact]
+
Example when using a key name 'my key':
Caught exception reading instance data:
http://169.254.169.254/2009-04-04/meta-data/mpi/my key
Is a boto issue, see https://github.com/boto/boto/issues/659
+
+
+ [Test Case]
+
+ #!/usr/bin/env python
+ f
** Description changed:
[Impact]
Example when using a key name 'my key':
Caught exception reading instance data:
http://169.254.169.254/2009-04-04/meta-data/mpi/my key
Is a boto issue, see https://github.com/boto/boto/issues/659
Patches provided for Precise, Quantal and Rar
Puppet 3.2.2 is in Saucy now. Will see how feasible it is to just do a
full backport into Precise.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1068145
Title:
Fix for CVE-2012-3867
I've started the backport process here: https://bugs.launchpad.net
/precise-backports/+bug/1194901
If anyone is interested in testing out the packages on either Precise,
Quantal, or Raring and provide feedback on that backport request it
would be greatly appreciated! This will also help speed up t
Friendly ping to see what the status is on this issue wrt comment #23
Thanks!
Adam
--
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/1004775
Title:
NetworkManager restarts dnsmasq and
Thanks Mathieu for the upload!
--
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/1004775
Title:
NetworkManager restarts dnsmasq and adds host route on every IPv6
route lookup
To man
Agreed, however, from previous discussions with the maintainers I was
under the impression this wouldn't be a trivial fix for 2.7.x.
Jeff,
Could you comment on that?
Thanks
Adam
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet
** Patch removed: "samba_3.6.3-2ubuntu2.7.debdiff"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1003296/+attachment/3729222/+files/samba_3.6.3-2ubuntu2.7.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubunt
** Changed in: python-eventlet (Ubuntu Raring)
Status: In Progress => Fix Committed
** Changed in: python-eventlet (Ubuntu Raring)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-
** Changed in: maas (Ubuntu)
Status: Invalid => In Progress
** Changed in: maas (Ubuntu)
Assignee: (unassigned) => Adam Stokes (adam-stokes)
** Changed in: maas (Ubuntu)
Importance: Undecided => Medium
** Changed in: maas (Ubuntu)
Importance: Medium => High
--
** Changed in: maas (Ubuntu)
Status: In Progress => Invalid
--
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/1069570
Title:
1 MAC Address, two IPs - DNS is "out of sync" with DHCP
** Patch added: "maas_1.4+bzr1539+dfsg-0ubuntu2.saucy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1069570/+attachment/3756388/+files/maas_1.4%2Bbzr1539%2Bdfsg-0ubuntu2.saucy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Patch added: "maas_1.4+bzr1539+dfsg-0ubuntu2.saucy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1207102/+attachment/3756460/+files/maas_1.4%2Bbzr1539%2Bdfsg-0ubuntu2.saucy.debdiff
** Description changed:
[impact]
MAAS is failing to add all enlisted machines to DNS.
Public bug reported:
[impact]
MAAS is failing to add all enlisted machines to DNS. There seems to be
a sync issue between dhcp and dns during enlishting.
[test case]
+ Have MaaS 1.3 running
+ Boot machines to be controlled by MaaS and get MaaS to enlist them.
+ Go on MaaS WebUI and change ipmi
** Changed in: maas (Ubuntu)
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas (Ubuntu)
Importance: Undecided => High
** Patch removed: "maas_1.4+bzr1539+dfsg-0ubuntu2.saucy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1207102/+attachment/37564
So the debdiff was uploaded and referenced bug 1069570 after I marked
that one invalid. So I guess we can dis-regard this one?
--
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/1207102
Titl
Hmm, so I marked this bug invalid b/c I created a new bug 1207102 with
the same changes. This got uploaded anyway and referenced this bug.
--
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/1
** Changed in: nova (Ubuntu)
Status: In Progress => Fix Released
--
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/1119248
Title:
[SRU] nova does not set container_format when snap
Thanks Brian,
Ed this should be good to go now and in process of being reviewed by SRU
team.
Adam
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-eventlet in Ubuntu.
https://bugs.launchpad.net/bugs/1199037
Title:
backport ev
** Patch added: "keepalived_1.2.7-1_keepalived_1.2.7-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1183300/+attachment/3770114/+files/keepalived_1.2.7-1_keepalived_1.2.7-1ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Ser
** Patch added: "keepalived_1.2.7-1ubuntu1.merge.debdiff"
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1183300/+attachment/3770115/+files/keepalived_1.2.7-1ubuntu1.merge.debdiff
** Changed in: keepalived (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notif
** Changed in: keepalived (Ubuntu)
Importance: Wishlist => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1183300
Title:
Please upgrade keepalived to the latest upstrea
Ah i was trying to research where those DEB* variables were used thanks
for clearing that up. I'll update the debdiffs today to fix the
indentation in the changelog
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keepalived in Ubuntu.
h
Updated from suggestions in reviewer's comments
** Patch removed: "keepalived_1.2.7-1_keepalived_1.2.7-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1183300/+attachment/3770114/+files/keepalived_1.2.7-1_keepalived_1.2.7-1ubuntu1.debdiff
** Patch removed: "keepali
Updated from suggestions in reviewer's comments
** Patch added: "keepalived_1.2.7-1ubuntu1.merge.debdiff"
https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1183300/+attachment/3771190/+files/keepalived_1.2.7-1ubuntu1.merge.debdiff
--
You received this bug notification because you are
** Summary changed:
- [Precise] keepalived reload buggy
+ keepalived reload buggy
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1211876
Title:
keepalived reload buggy
To manag
** Changed in: keepalived (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to keepalived in Ubuntu.
https://bugs.launchpad.net/bugs/1211876
Title:
keepalived reload buggy
To manage notifications
The precise version should contain this fix as well, could I get an eta
when the next maas releases are going to be done?
Thanks!
Adam
** Also affects: maas (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Serv
Martin,
Subscribed you to this bug in hopes you may have a better understanding
of why the dbg package isn't being built? This is an ongoing issue with
several packages and probably needs to be brought up at the next UDS.
Thanks
Adam
--
You received this bug notification because you are a membe
This patch puts all stripped executables and shared libraries into their
relevant -dbg packages.
** Patch added: "autofs5_5.0.6-0ubuntu3.unstable.debdiff"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/924002/+attachment/2728194/+files/autofs5_5.0.6-0ubuntu3.unstable.debdiff
--
You r
Output of autofs5-dbgsym
dpkg -L autofs5-dbgsym
/.
/usr
/usr/lib
/usr/lib/debug
/usr/lib/debug/usr
/usr/lib/debug/usr/sbin
>> /usr/lib/debug/usr/sbin/automount
/usr/lib/debug/usr/lib
/usr/lib/debug/usr/lib/autofs
/usr/lib/debug/usr/lib/autofs/mount_ext2.so
/usr/lib/debug/usr/lib/autofs/lookup_f
re #108 (cdmiller)
Is this fix still a workable solution for you and have you run into any
issues not yet experienced on this bug?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.ne
** Also affects: keepalived (Ubuntu Wily)
Importance: Undecided
Status: New
** Also affects: keepalived (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: keepalived (Ubuntu Vivid)
Importance: Undecided
Status: New
--
You received this bug notificat
Public bug reported:
Our installer attempts to load VM's within an lxc container. This worked
on trusty, however, with the latest releases from vivid and wily those
VM's are unable to start. This affects running juju-local within a
container as well.
We think it has something to do with cgmanager
I hit this too, I actually just had to run:
/usr/lib/x86_64-linux-gnu/lxc/lxc-net stop
And it seemed to put itself back into a state that systemd could work
with
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://b
** Tags added: cloud-installer
--
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/1509414
Title:
lxc postinst script checks available interfaces, can choose
To manage notifications about t
** Changed in: lxc (Ubuntu)
Importance: Undecided => Critical
--
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/1509414
Title:
lxc postinst script checks available interfaces, can choos
** Description changed:
- The released wily image preinstalls lxc, which breaks the assumption
- that lxc's preinst packaging script makes:
+ [Problem]
+ The released wily image preinstalls lxc, which breaks the assumption that
lxc's preinst packaging script makes:
It inspects the network to
** Description changed:
[Problem]
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
I've also tested manually and via our OpenStack installer and lxcbr0 is
assigned (10.0.4.1) and the network is able to reach out to the internet
as before.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.laun
** Tags added: cloud-installer
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/1547640
Title:
proxy tries ipv6 and gets 503 when no ipv6 routes
To manage notifications about this bug
For completeness this is the lintian output in all its glory:
E: juju2 changes: bad-distribution-in-changes-file xenial-amd64
N:
N:You've specified an unknown target distribution for your upload in the
N:debian/changelog file. It is possible that you are uploading for a
N:different di
With my latest changes here is the lintian report:
I: juju2 source: wildcard-matches-nothing-in-dep5-copyright
src/github.com/chai2010/gettext-go (paragraph at line 58)
N:
N:The wildcard that was specified matches no file in the source tree. This
N:either indicates that you should fix th
Ok I've gotten it down to some minor packaging issues:
I: juju2: spelling-error-in-binary usr/lib/juju-2.0-beta2/bin/juju ang and
N:
N:Lintian found a spelling error in the given binary. Lintian has a list
N:of common misspellings that it looks for. It does not have a dictionary
N:lik
** Description changed:
Juju 2.0 will be in xenial. We want to place juju 2.0-beta2 (or possibly
beta3) in xenial for Ubuntu users to test.
This branch introduces the juju2 package.
lp:~juju-qa/ubuntu/xenial/juju2/xenial-2.0-beta2
The juju team propose a new juju2 packages t
** Description changed:
Juju 2.0 will be in xenial. We want to place juju 2.0-beta2 (or possibly
beta3) in xenial for Ubuntu users to test.
This branch introduces the juju2 package.
lp:~juju-qa/ubuntu/xenial/juju2/xenial-2.0-beta2
The juju team propose a new juju2 packages t
** Changed in: juju-core (Ubuntu)
Status: Triaged => Fix Committed
--
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/1560315
Title:
[needs packaging] juju2 beta is not in xeni
Also want to mention the openstack package as well.
--
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/1545913
Title:
[FFe] juju-core 2.0
To manage notifications about this bug go to
** Tags added: conjure
--
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/1545913
Title:
[FFe] juju-core 2.0
To manage notifications about this bug go to:
https://bugs.launchpad.net/
James,
I looked into using this module in our cloud installer, one bug in
particular that exists in 0.7.10 but not in 0.7.13 is the use of
sys.maxint:
Traceback (most recent call last):
File "", line 1, in
File "/usr/share/openstack/cloudinstall/netutils.py", line 78, in get_ip_set
ips
Looks like a small typo
if size > _sys.maxint should be if size > _sys_maxint
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-netaddr in Ubuntu.
https://bugs.launchpad.net/bugs/1307733
Title:
python3-netaddr 0.7.10 with poor
1 - 100 of 134 matches
Mail list logo