[Bug 1302700] Re: Use of NamedTemporaryFile creates rings with restricted permissions
** Changed in: swift Status: Fix Committed = Fix Released ** Changed in: swift Milestone: None = 2.0.0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to swift in Ubuntu. https://bugs.launchpad.net/bugs/1302700 Title: Use of NamedTemporaryFile creates rings with restricted permissions To manage notifications about this bug go to: https://bugs.launchpad.net/swift/+bug/1302700/+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 1297962] Re: [sru] Nova-compute doesnt start
This is no longer in -proposed, and 1:2014.1-0ubuntu1.2 is in -updates. ** Tags removed: verification-needed -- 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/1297962 Title: [sru] Nova-compute doesnt start To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1297962/+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 1332815] [NEW] Don't overwrite /var/www on upgrade
Public bug reported: I just did a few runs of do-release-upgrade to get from 12.04 to 14.04, just as I have been doing upgrades for some time now. ITo my surprise, one of the upgrades has wiped /var/www and overwritten it with the default data. I have kept all my www-data under /var/www/ and this directory hasn't been overwritten in previous upgrades. I know I should do backups, but given this wasn't a problem in the last releases I didn't expect a problem to occur. Could the package install be modified in a way that /var/www is not overwritten if it already exists? ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1332815 Title: Don't overwrite /var/www on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1332815/+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 1328958] Re: Local provider fails to bootstrap on utopic
I came across this on Trusty using ppa:juju/stable : $ dpkg-query -W juju-core juju-local juju-core 1.18.4-0ubuntu1~14.04.1~juju1 juju-local 1.18.4-0ubuntu1~14.04.1~juju1 So on Trusty, an ordinary user's desktop will not have an ubuntu user, and the local environment is completely broken on it. It seems to me that for proper test coverage, the test environment also needs to be changed to not have an ubuntu user. I can understand why Juju must make assumptions about such a user (since cloud images ship with one), but this demonstrates why it is essential that the local environment is tested without one. ** Summary changed: - Local provider fails to bootstrap on utopic + Local provider assumes a local ubuntu user exists ** Changed in: juju-core (Ubuntu) Status: New = Triaged ** Changed in: juju-core (Ubuntu) Importance: Undecided = High ** Also affects: juju-core Importance: Undecided Status: 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/1328958 Title: Local provider assumes a local ubuntu user exists To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1328958/+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 1328958] Re: Local provider assumes a local ubuntu user exists
My steps to reproduce on a Trusty cloud image (off the top of my head - let me know if you have any problems): 1. sudo adduser --disabled-password --gecos '' otheruser 2. echo 'otheruser ALL=(ALL) NOPASSWD:ALL'|sudo tee --append /etc/sudoers 3. sudo add-apt-repository ppa:juju/stable 4. sudo apt-get install -y juju-core juju-local 5. Log in as otheruser (arrange authorized_keys first, etc). 6. sudo deluser ubuntu 7. juju generate-config 8. juju switch local 9. juju bootstrap --upload-tools --series trusty uploading tools for series [trusty] Logging to /home/otheruser/.juju/local/cloud-init-output.log on remote host chown: invalid user: ‘ubuntu:ubuntu’ Bootstrap failed, destroying environment ERROR exit status 1 -- 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/1328958 Title: Local provider assumes a local ubuntu user exists To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1328958/+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 1328958] Re: Local provider assumes a local ubuntu user exists
Filed bug 1332820 for test coverage. -- 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/1328958 Title: Local provider assumes a local ubuntu user exists To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1328958/+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 1332820] Re: QA tests assume that a local ubuntu user exists
dep8 testing in archive packaging should also test this correctly. ** Also affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Changed in: juju-core (Ubuntu) Status: New = Triaged ** Changed in: juju-core (Ubuntu) Importance: Undecided = High ** Summary changed: - QA tests assume that a local ubuntu user exists + QA tests provide a local ubuntu user, causing tests to pass when they should fail -- 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/1332820 Title: QA tests provide a local ubuntu user, causing tests to pass when they should fail To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1332820/+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 1204069] Re: lxc dhcp fails
I had a 12.04, upgraded to the kernel of 12.10 (kernel v3.5.0-21-generic), and used it flawlessly for several month with LXC containers. Very recently, I had a btrfs issue that made my update my kernel to v3.15.1-031501-generic. That's when my existing containers didn't catch anymore their IP on boot via DHCP. A tcpdump shows bad udp cksum: 16:32:32.032975 IP (tos 0x0, ttl 64, id 25006, offset 0, flags [DF], proto UDP (17), length 71) ns3262489.ovh.net.61855 172.128.0.75.domain: [bad udp cksum 0xdbeb - 0x0796!] 43449+ PTR? 75.0.128.172.in-addr.arpa. (43) For a good blog post around this issue and how to deal with it (not mine): http://colinnewell.wordpress.com/2013/12/18/lxc-networking/ -- 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/1204069 Title: lxc dhcp fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1204069/+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 1332893] [NEW] systemd-logind[976]: cgmanager: cgm_remove failed: cpu:user/115.user did not exist
Public bug reported: dmesg ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: cgmanager 0.26-0ubuntu3 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jun 21 20:54:31 2014 InstallationDate: Installed on 2014-04-27 (55 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: cgmanager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cgmanager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cgmanager in Ubuntu. https://bugs.launchpad.net/bugs/1332893 Title: systemd-logind[976]: cgmanager: cgm_remove failed: cpu:user/115.user did not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1332893/+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
