[Bug 1605976] Re: [2.0] bump mongod to 3.2.9
** Changed in: juju Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605976 Title: [2.0] bump mongod to 3.2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1605976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602192] Re: when starting many LXD containers, they start failing to boot with "Too many open files"
** Changed in: juju Milestone: 2.0.0 => 2.1.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602192 Title: when starting many LXD containers, they start failing to boot with "Too many open files" To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1602192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612645] Re: New EC2 region in India (ap-south-1 - Mumbai)
** Changed in: juju Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612645 Title: New EC2 region in India (ap-south-1 - Mumbai) To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1612645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564157] Re: juju list-credentials fails to display
** Tags added: ateam -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564157 Title: juju list-credentials fails to display To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1564157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612645] Re: New EC2 region in India (ap-south-1 - Mumbai)
** Tags added: ateam -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612645 Title: New EC2 region in India (ap-south-1 - Mumbai) To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1612645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605976] Re: [2.0] bump mongod to 3.2.9
** Changed in: juju Assignee: (unassigned) => Alexis Bruemmer (alexis-bruemmer) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605976 Title: [2.0] bump mongod to 3.2.9 To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1605976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612645] Re: New EC2 region in India (ap-south-1 - Mumbai)
** Changed in: juju Assignee: (unassigned) => Alexis Bruemmer (alexis-bruemmer) ** Changed in: juju Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612645 Title: New EC2 region in India (ap-south-1 - Mumbai) To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1612645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1602192] Re: when starting many LXD containers, they start failing to boot with "Too many open files"
** Changed in: juju-core Assignee: Christian Muirhead (2-xtian) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1602192 Title: when starting many LXD containers, they start failing to boot with "Too many open files" To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1602192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564157] Re: juju list-credentials fails to display
** Changed in: juju Assignee: (unassigned) => Alexis Bruemmer (alexis-bruemmer) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564157 Title: juju list-credentials fails to display To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1564157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1570650] Re: Use juju-mongodb2.6 for 1.25 on xenial
mongo 2.4 is working with juju 1.25 and there very few fixes in 2.6 that is worth the effort of updating. If a field issue hit that would addressed by updating to 2.6 I would be happy to revisit this discussion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1570650 Title: Use juju-mongodb2.6 for 1.25 on xenial To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1570650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296066] Re: [Lenovo ThinkPad X1 Carbon 20A7] suspend/resume failure
I confirmed this is still an issue on 16.04 (Xenial); disabling USB3 allows suspend/resume to work correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296066 Title: [Lenovo ThinkPad X1 Carbon 20A7] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577930] [NEW] Failed to upgrade from Trusty to Xenial when using "sudo update-manager -d"
Public bug reported: from terminal: sudo update-manager -d software updater runs and gives the option to upgrade, when I hit the upgrade button it exits and this is the only thing that is on terminal: alexisb@alexisb-ThinkPad-X1-Carbon-2nd:~$ sudo update-manager -d [sudo] password for alexisb: Hangup alexisb@alexisb-ThinkPad-X1-Carbon-2nd:~$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.8 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 Uname: Linux 3.13.0-85-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Tue May 3 13:32:28 2016 InstallationDate: Installed on 2014-06-20 (682 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to trusty on 2016-05-03 (0 days ago) VarLogDistupgradeAptlog: Log time: 2016-05-03 12:30:23.112657 Log time: 2016-05-03 12:30:39.457615 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade trusty uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577930 Title: Failed to upgrade from Trusty to Xenial when using "sudo update- manager -d" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1577930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang
Response to James' inquiries in comment #67: * juju team: can you comment on the package breakdown? For items requiring further discussion, it might be worthwhile understanding how often you are updating the embedded package (useful for the SRU question, below) On average 50% of the package dependencies change between minor release (for example there were 14 package dependency changes from 1.24 to 1.25) * SRU team: juju-core already has a release exception. For packages that are being broken out that were formerly part of the juju-core package and that the juju team will now maintain, can those just be given a release exception? Yes, those should also be given a release exception. Many of these are central to keeping ubuntu current with existing clouds. For Juju to actually work, if the dependent packages are being split out, every single one of them will need to be included in the release exception. * Ubuntu Archive team: juju-core will likely need a PPU for members of the juju team when it goes to main. Can we extend the acl to include the packages that are being broken out that they are going to maintain? Yes, to deliver a fix to juju core, we need to fix the dependencies at the same time. This will be done by the same person, so yes to extending the acls to those packages. * MIR team: for the packages that are being broken out, I propose that they don't get extended MIR review, but rather simply the packaging review to make sure they are following the Go standards as outlined in the MIRteam document Yes, agreed. * juju team (/security team): the juju team has said that they would like coordination of security updates for juju-core and golang-*-dev packages for which they maintain. I propose the security team maintains a list of packages and when we triage a CVE against a package in that list, we file a bug for the juju team to fix, and sponsor their uploads (like for other Canonical upstreams). juju team-- does that address your concerns? Yes, we will own fixing security bugs for juju, and dependent libraries that we control or can patch. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-5/+bug/1267393/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang
Response to James' inquiries in comment #67: * juju team: can you comment on the package breakdown? For items requiring further discussion, it might be worthwhile understanding how often you are updating the embedded package (useful for the SRU question, below) On average 50% of the package dependencies change between minor release (for example there were 14 package dependency changes from 1.24 to 1.25) * SRU team: juju-core already has a release exception. For packages that are being broken out that were formerly part of the juju-core package and that the juju team will now maintain, can those just be given a release exception? Yes, those should also be given a release exception. Many of these are central to keeping ubuntu current with existing clouds. For Juju to actually work, if the dependent packages are being split out, every single one of them will need to be included in the release exception. * Ubuntu Archive team: juju-core will likely need a PPU for members of the juju team when it goes to main. Can we extend the acl to include the packages that are being broken out that they are going to maintain? Yes, to deliver a fix to juju core, we need to fix the dependencies at the same time. This will be done by the same person, so yes to extending the acls to those packages. * MIR team: for the packages that are being broken out, I propose that they don't get extended MIR review, but rather simply the packaging review to make sure they are following the Go standards as outlined in the MIRteam document Yes, agreed. * juju team (/security team): the juju team has said that they would like coordination of security updates for juju-core and golang-*-dev packages for which they maintain. I propose the security team maintains a list of packages and when we triage a CVE against a package in that list, we file a bug for the juju team to fix, and sponsor their uploads (like for other Canonical upstreams). juju team-- does that address your concerns? Yes, we will own fixing security bugs for juju, and dependent libraries that we control or can patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-5/+bug/1267393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang
> Will the juju team be asking for an MRE? Is it anticipated that new series > (e.g., the 1.18 to 1.22 change) would be included as an MRE? What > processes are in place to test updates before including updates into the > archive? What processes are available to the security team to test > updates that we would prepare? To more directly answer this comment, Juju does have a Stable Release Update policy in place. As part of that policy the QA team outline testing Juju CI and testing procedures, details are here: https://docs.google.com/document/d/1TVW0QzpLo622pzBUsEK9SqZAod4oJn9ROF1IWMqa9tg/edit#heading=h.f3goroun9jd1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-5/+bug/1267393/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang
> Will the juju team be asking for an MRE? Is it anticipated that new series > (e.g., the 1.18 to 1.22 change) would be included as an MRE? What > processes are in place to test updates before including updates into the > archive? What processes are available to the security team to test > updates that we would prepare? To more directly answer this comment, Juju does have a Stable Release Update policy in place. As part of that policy the QA team outline testing Juju CI and testing procedures, details are here: https://docs.google.com/document/d/1TVW0QzpLo622pzBUsEK9SqZAod4oJn9ROF1IWMqa9tg/edit#heading=h.f3goroun9jd1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-5/+bug/1267393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** Changed in: juju-core/1.25 Milestone: 1.25-beta1 => 1.25-beta2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1349949] Re: Juju's mongodb does not need to log every command in syslog
** Changed in: juju-core/1.25 Milestone: 1.25-beta1 => 1.25-beta2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349949 Title: Juju's mongodb does not need to log every command in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1349949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang
LP #1481502 has been opened to track the development work to fix ShQuote() https://bugs.launchpad.net/juju-core/+bug/1481502 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-5/+bug/1267393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267393] Re: [MIR] juju-core, juju-mongodb, gccgo, golang
LP #1481502 has been opened to track the development work to fix ShQuote() https://bugs.launchpad.net/juju-core/+bug/1481502 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1267393 Title: [MIR] juju-core, juju-mongodb, gccgo, golang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gccgo-5/+bug/1267393/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
