[Bug 1180867] Re: cloud-config merging not forward or backward compatible
** Changed in: cloud-init (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1180867 Title: cloud-config merging not forward or backward compatible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1180867/+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 1159715] Re: winbind_krb5_locator plugin is missing from winbind 3.6.3
I noticed this bug while researching symptoms similar to yours. However, while during logon we occasionally hit the external DC, it reponds quickly in our case. In the end, I found out the delays were caused by time sync issues resulting in the client having to request service tickets for the LDAP queries to the DC's multiple times which in return resulted in an extremely high number of DNS queries. The total number of DNS lookups for a single logon + homedir mount runs into the hundreds because each time all service records are queried again. It also turned out that every now and than a query would not be answered, resulting in timeouts. The cumulative DNS timeouts (10-30 timeouts for a single logon session) caused most of the delays. What does not help here is that Ubuntu uses dnsmasq, but has its resolver cache disabled. (windows clients do have resolver caches and need them) In the end I did three quick fixes pending further investigation: - I defined my domain controllers as NTP servers in ntp.conf - I hard coded the DC's in krb5.conf, reducing the number of service records lookups needed to fild the KDC for the realm; - I installed a pdns resolver listening on 127.0.0.3 and configured it to forwarded all queries to the DC's (the disabling of the cache in dnsmasq turned out to be hard-coded by Ubuntu and I didn't wanted to touch that) winbind and kerberos is a fragile thing.. -- 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/1159715 Title: winbind_krb5_locator plugin is missing from winbind 3.6.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1159715/+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 1181135] [NEW] open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
Public bug reported: 1 ProblemType: Package DistroRelease: Ubuntu 12.04 Package: open-vm-dkms 2011.12.20-562307-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-28.48~precise1-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.2 Architecture: amd64 DKMSKernelVersion: 3.5.0-28-generic Date: Fri May 17 10:30:37 2013 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True PackageArchitecture: all PackageVersion: 2011.12.20-562307-0ubuntu1 SourcePackage: open-vm-tools Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: open-vm-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1181135 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1181135/+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 1181136] [NEW] Empty log file when a container is started with the API
Public bug reported: When a container is started with the python API the log file /var/log/lxc/NAME.log is empty. This is pretty annoying to debug pre- start hook issues for example. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lxc 0.9.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.9.0-1.5-generic 3.9.1 Uname: Linux 3.9.0-1-generic x86_64 ApportVersion: 2.10.1-0ubuntu1 Architecture: amd64 Date: Fri May 17 10:31:44 2013 MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to saucy on 2012-01-31 (471 days ago) lxcsyslog: ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- 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/1181136 Title: Empty log file when a container is started with the API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1181136/+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 1181135] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1181135 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1181135/+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
[Blueprint servercloud-s-ceph] Ceph activities for Saucy
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.06: - Enable google-perftools on armhf: TODO + Enable google-perftools on armhf: DONE Upload cuttlefish to saucy: TODO Upload cuttlefish to the havana cloud archive: TODO Work items for ubuntu-13.07: Upload dumpling - 4 weeks to saucy: TODO Upload dumpling - 2 weeks to saucy: TODO Work items for ubuntu-13.08: Upload dumpling to saucy: TODO Upload dumpling to the havana cloud archive: TODO Write dep8 tests for ceph: TODO Review upstream patches for mod_fastcgi: TODO Review/test ceph RADOS with mod_fcgid: TODO Identify use-cases for ceph performance scenarios: TODO Update ceph charms to support cuttlefish features: TODO ceph-deploy packaging: TODO Work items for ubuntu-13.10: Regular multi-node ceph testing in the lab: BLOCKED Implement more in-depth testing of Ceph to support SRU's: TODO Ceph teuthology tests for deploying with Juju: TODO Ability to use upstream packages in Juju charms: TODO -- Ceph activities for Saucy https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-ceph -- 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 454566] Re: False positive for SucKit
This went away in 12.10 and reappared when I upgraded to 13.04. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to chkrootkit in Ubuntu. https://bugs.launchpad.net/bugs/454566 Title: False positive for SucKit To manage notifications about this bug go to: https://bugs.launchpad.net/server-papercuts/+bug/454566/+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
[Blueprint servercloud-s-seeded-qa-workflow] Improving QA for seeded server packages
Blueprint changed by Yolanda Robla: Work items changed: Work items: [andreserl] write dep-8 test for heartbeat/corosync/pacemaker: TODO [andreserl] write dep-8 test for tftpd-hpa: TODO [gandelman-a] write dep-8 test for haproxy: TODO [gandelman-a] write dep-8 tests puppet + facter: TODO Get all tests automated by QA team: DONE [ivoks] write dep-8 test for bacula: TODO [yolanda] write dep-8 test for ganglia: DONE [yolanda] write dep-8 test for iscsitarget: DONE [james-page] write dep-8 test for jenkins: TODO [yolanda] write dep-8 test for nagios3: DONE - [yolanda] write dep-8 test for open-iscsi: TODO - [james-page] write dep-8 test for quagga: TODO + [yolanda] write dep-8 test for open-iscsi: DONE + [yolanda] write dep-8 test for quagga: TODO [james-page] write dep-8 test for radvd: TODO [james-page] write dep-8 test for solr-tomcat/jetty: TODO [james-page] write dep-8 test for tgt: TODO [james-page] write dep-8 test for openvswitch: DONE [james-page] Write some guidelines for test authors so we get things right first time: TODO [james-page] Update https://wiki.ubuntu.com/QATeam/RequiredTests where appropriate: DONE [pcarrier] write dep-8 test for munin: TODO [racb] write dep-8 test for clamav: TODO [racb] write dep-8 test for exim4: TODO [racb] write dep-8 test for mailman: TODO [racb] write dep-8 test for memcached: TODO [racb] write dep-8 test for squid3: TODO [racb] write dep-8 test for varnish: TODO [racb] write dep-8 test for vsftpd: TODO review backuppc for continued seed inclusion: TODO review likewise-open for continued seed inclusion: TODO [serge-hallyn] write dep-8 test for kvm: TODO [serge-hallyn] write dep-8 test for lxc: DONE [yolanda] write dep-8 test for amavisd-new: DONE [yolanda] write dep-8 test for nut: DONE [yolanda] write dep-8 test for postfix: DONE [yolanda] write dep-8 test for slapd/openldap: DONE [pcarrier] write dep-8 test for snmpd: TODO [yolanda] write dep-8 test for spamassassin: DONE [zulcss] write dep-8 test for freeradius: TODO [zulcss] write dep-8 test for rabbitmq-server: TODO -- Improving QA for seeded server packages https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-seeded-qa-workflow -- 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 1176202] Re: ipmitool 1.8.12 needs -C3 to work with lanplus
** Bug watch added: Red Hat Bugzilla #877219 https://bugzilla.redhat.com/show_bug.cgi?id=877219 ** Also affects: ipmitool (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=877219 Importance: Unknown Status: Unknown ** Changed in: ipmitool (Ubuntu) Status: New = In Progress ** Changed in: ipmitool (Ubuntu) Assignee: (unassigned) = Robie Basak (racb) ** Tags removed: needs-upstream-report -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1176202 Title: ipmitool 1.8.12 needs -C3 to work with lanplus To manage notifications about this bug go to: https://bugs.launchpad.net/ipmitool/+bug/1176202/+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 1176202] Re: ipmitool 1.8.12 needs -C3 to work with lanplus
I'm hesitant to suggest an SRU for this, since a fix would necessarily break users on Raring depending on -C0 as the default. Opinions welcome. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1176202 Title: ipmitool 1.8.12 needs -C3 to work with lanplus To manage notifications about this bug go to: https://bugs.launchpad.net/ipmitool/+bug/1176202/+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 1176202] Re: ipmitool 1.8.12 needs -C3 to work with lanplus
Thanks for tracking this down, Samantha. I hadn't realised that we'd already synced with Debian in Saucy after they picked up our changes. I've filed a bug in Debian for a cherry-pick of this fix. We'll auto-sync as soon as Debian fixes the bug - that way we can stay synced. If Debian haven't addressed the bug nearer Saucy release time, we can introduce an Ubuntu delta to fix this in time for release - please poke me if so and I'll get it done. ** Also affects: ipmitool via http://sourceforge.net/support/tracker.php?aid=3571371 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #708621 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708621 ** Also affects: ipmitool (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708621 Importance: Unknown Status: Unknown ** Changed in: ipmitool (Ubuntu) Status: In Progress = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipmitool in Ubuntu. https://bugs.launchpad.net/bugs/1176202 Title: ipmitool 1.8.12 needs -C3 to work with lanplus To manage notifications about this bug go to: https://bugs.launchpad.net/ipmitool/+bug/1176202/+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 1004606] Re: virsh create-snapshot fails to create external snapshot (blockdev-snapshot-sync fails in json monitor)
Is there any bugfix in sight or work around known except for disabling apparmor? -- 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/1004606 Title: virsh create-snapshot fails to create external snapshot (blockdev- snapshot-sync fails in json monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1004606/+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
Re: [Bug 1004606] Re: virsh create-snapshot fails to create external snapshot (blockdev-snapshot-sync fails in json monitor)
i don't know others work around 2013/5/17 Theodor van Nahl 1004...@bugs.launchpad.net Is there any bugfix in sight or work around known except for disabling apparmor? -- You received this bug notification because you are subscribed to a duplicate bug report (1096125). https://bugs.launchpad.net/bugs/1004606 Title: virsh create-snapshot fails to create external snapshot (blockdev- snapshot-sync fails in json monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1004606/+subscriptions -- Riccardo Casatta -- 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/1004606 Title: virsh create-snapshot fails to create external snapshot (blockdev- snapshot-sync fails in json monitor) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1004606/+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
[Blueprint servercloud-s-seeded-qa-workflow] Improving QA for seeded server packages
Blueprint changed by James Page: Assignee: James Page = Ubuntu Server Team -- Improving QA for seeded server packages https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-seeded-qa-workflow -- 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
[Blueprint servercloud-s-seeded-qa-workflow] Improving QA for seeded server packages
Blueprint changed by James Page: Drafter: Ubuntu Server Team = James Page -- Improving QA for seeded server packages https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-seeded-qa-workflow -- 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
[Blueprint servercloud-s-ceph] Ceph activities for Saucy
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.06: - Enable google-perftools on armhf: DONE - Upload cuttlefish to saucy: TODO - Upload cuttlefish to the havana cloud archive: TODO + [james-page] Enable google-perftools on armhf: DONE + [james-page] Upload cuttlefish to saucy: TODO + [james-page] Upload cuttlefish to the havana cloud archive: TODO Work items for ubuntu-13.07: - Upload dumpling - 4 weeks to saucy: TODO - Upload dumpling - 2 weeks to saucy: TODO + [james-page] Upload dumpling - 4 weeks to saucy: TODO + [james-page] Upload dumpling - 2 weeks to saucy: TODO Work items for ubuntu-13.08: - Upload dumpling to saucy: TODO - Upload dumpling to the havana cloud archive: TODO - Write dep8 tests for ceph: TODO + [james-page] Upload dumpling to saucy: TODO + [james-page] Upload dumpling to the havana cloud archive: TODO + [james-page] Write dep8 tests for ceph: TODO Review upstream patches for mod_fastcgi: TODO Review/test ceph RADOS with mod_fcgid: TODO Identify use-cases for ceph performance scenarios: TODO - Update ceph charms to support cuttlefish features: TODO + [james-page] Update ceph charms to support cuttlefish features: TODO ceph-deploy packaging: TODO Work items for ubuntu-13.10: - Regular multi-node ceph testing in the lab: BLOCKED - Implement more in-depth testing of Ceph to support SRU's: TODO + [james-page] Regular multi-node ceph testing in the lab: BLOCKED + [james-page] Implement more in-depth testing of Ceph to support SRU's: TODO Ceph teuthology tests for deploying with Juju: TODO Ability to use upstream packages in Juju charms: TODO -- Ceph activities for Saucy https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-ceph -- 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
[Blueprint servercloud-s-cloud-archive] Ubuntu Cloud Archive Status Check
Blueprint changed by James Page: Work items changed: + Work items for ubuntu-13.05: + Open Cloud Archive for Havana development: TODO + + Work items for ubuntu-13.06: + [james-page] Document proposed OpenStack SRU cadence process: TODO + Update Cloud Archive documentation inline with support lifecycle: TODO + + Work items for ubuntu-13.08: + [zulcss] Backport of qemu for Havana: TODO + [james-page] Discuss communications plan around cloud-archive releases with jcastro: TODO + Work items: - Open Cloud Archive for Havana development: TODO - Document proposed OpenStack SRU cadence process: TODO - Update Cloud Archive documentation inline with support lifecycle: TODO - Expose build logs for UCA packages: TODO - Better expose per package build state for UCA packages: TODO + [gandelman-a] CA pipeline reporting for updates: TODO + [gandelman-a] Document backports tool in openstack-ubuntu-testing: TODO + [gandelman-a] Investigate automated changelog creation as part of per-commit testing: TODO + [gandelman-a] Document how to run verification testing against proposed updates: TODO + add-apt-repository for cloud-archive: TODO + Bug closure for cloud-archive bugs: TODO -- Ubuntu Cloud Archive Status Check https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-archive -- 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
[Blueprint servercloud-s-cloud-archive] Ubuntu Cloud Archive Status Check
Blueprint changed by James Page: Whiteboard changed: - Things to discuss: - Stable release update cadence - Tooling - Support period alignment with Ubuntu distro releases (18 - 9 months) - - Upstream stable release schedule: - - stable release proposed dates: - 2013.1.1 May 9 - DONE - 2013.1.2 Jun 6 - 2013.1.3 Aug 8 - 2013.1.4 Oct 10 - 2013.1.5 - post-H release - [USER STORIES] [ASSUMPTIONS] [RISKS] [IN SCOPE] [OUT OF SCOPE] [USER ACCEPTANCE] [RELEASE NOTE/BLOG] + + [SESSION NOTES] + http://pad.ubuntu.com/uds-1305-servercloud-s-cloud-archive -- Ubuntu Cloud Archive Status Check https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-archive -- 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
[Blueprint servercloud-s-cloud-archive] Ubuntu Cloud Archive for Havana
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.05: Open Cloud Archive for Havana development: TODO Work items for ubuntu-13.06: [james-page] Document proposed OpenStack SRU cadence process: TODO Update Cloud Archive documentation inline with support lifecycle: TODO + [james-page] Implement workflow for critical security updates: TODO Work items for ubuntu-13.08: [zulcss] Backport of qemu for Havana: TODO [james-page] Discuss communications plan around cloud-archive releases with jcastro: TODO Work items: [gandelman-a] CA pipeline reporting for updates: TODO [gandelman-a] Document backports tool in openstack-ubuntu-testing: TODO [gandelman-a] Investigate automated changelog creation as part of per-commit testing: TODO [gandelman-a] Document how to run verification testing against proposed updates: TODO add-apt-repository for cloud-archive: TODO Bug closure for cloud-archive bugs: TODO -- Ubuntu Cloud Archive for Havana https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-archive -- 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
[Blueprint servercloud-s-cloud-archive] Ubuntu Cloud Archive for Havana
Blueprint changed by James Page: Whiteboard changed: [USER STORIES] + Gavin wants to deploy OpenStack Havana on 12.04; he's able todo this using the Ubuntu Cloud Archive for Havana. + [ASSUMPTIONS] + None + [RISKS] + SRU process not timely + Critical security updates don't land fast. + [IN SCOPE] + [OUT OF SCOPE] + [USER ACCEPTANCE] + N/A + [RELEASE NOTE/BLOG] + OpenStack Havana is also avaliable for Ubuntu 12.04 LTS by using the Ubuntu Cloud Archive. [SESSION NOTES] http://pad.ubuntu.com/uds-1305-servercloud-s-cloud-archive -- Ubuntu Cloud Archive for Havana https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-archive -- 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
[Blueprint servercloud-s-cloud-archive] Ubuntu Cloud Archive for Havana
Blueprint changed by James Page: Definition Status: Discussion = Review -- Ubuntu Cloud Archive for Havana https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-archive -- 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
[Blueprint servercloud-s-juju-2-delivery] Delivering Juju 2.0 into Ubuntu
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.06: - Get Go 1.1 into the archive: TODO + [james-page] Get Go 1.1 into the archive: TODO [dave-cheney] verify that Juju works with gccgo: TODO Upload juju-core point release: TODO Work items for ubuntu-13.07: Upload juju-core point release: TODO Work items for ubuntu-13.08: Upload juju-core point release: TODO Work items for ubuntu-13.09: Upload juju-core point release: TODO Work items for ubuntu-13.10: Upload juju-core final release: TODO Backport juju-core to 12.04, 12.10 and 13.04: TODO Work items: Investigate automated releases of juju-core into Ubuntu: TODO -- Delivering Juju 2.0 into Ubuntu https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-2-delivery -- 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
[Blueprint servercloud-s-juju-2-delivery] Delivering Juju 2.0 into Ubuntu
Blueprint changed by James Page: Definition Status: Discussion = Review -- Delivering Juju 2.0 into Ubuntu https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-2-delivery -- 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
[Blueprint servercloud-s-juju-2-delivery] Delivering Juju 2.0 into Ubuntu
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.06: [james-page] Get Go 1.1 into the archive: TODO [dave-cheney] verify that Juju works with gccgo: TODO Upload juju-core point release: TODO Work items for ubuntu-13.07: Upload juju-core point release: TODO Work items for ubuntu-13.08: Upload juju-core point release: TODO Work items for ubuntu-13.09: Upload juju-core point release: TODO Work items for ubuntu-13.10: Upload juju-core final release: TODO + Enable ARM support: TODO Backport juju-core to 12.04, 12.10 and 13.04: TODO Work items: Investigate automated releases of juju-core into Ubuntu: TODO -- Delivering Juju 2.0 into Ubuntu https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-2-delivery -- 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
[Blueprint servercloud-s-cloud-archive] Ubuntu Cloud Archive for Havana
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.05: Open Cloud Archive for Havana development: TODO Work items for ubuntu-13.06: [james-page] Document proposed OpenStack SRU cadence process: TODO Update Cloud Archive documentation inline with support lifecycle: TODO [james-page] Implement workflow for critical security updates: TODO Work items for ubuntu-13.08: + Figure out and document security update process for 3 month shortfall between distro and OpenStack support: TODO [zulcss] Backport of qemu for Havana: TODO [james-page] Discuss communications plan around cloud-archive releases with jcastro: TODO Work items: [gandelman-a] CA pipeline reporting for updates: TODO [gandelman-a] Document backports tool in openstack-ubuntu-testing: TODO [gandelman-a] Investigate automated changelog creation as part of per-commit testing: TODO [gandelman-a] Document how to run verification testing against proposed updates: TODO add-apt-repository for cloud-archive: TODO Bug closure for cloud-archive bugs: TODO -- Ubuntu Cloud Archive for Havana https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-archive -- 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 1173265] Re: facter fails to run from rebuilt source package
My mistake: Precise is not affected by this bug, and I've just tested a rebuilt package to double-check. ** Changed in: facter (Ubuntu Precise) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in Ubuntu. https://bugs.launchpad.net/bugs/1173265 Title: facter fails to run from rebuilt source package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1173265/+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
[Blueprint servercloud-s-juju-2-delivery] Delivering Juju 2.0 into Ubuntu
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.06: - [james-page] Get Go 1.1 into the archive: TODO + [james-page] Get Go 1.1 into the archive: INPROGRESS [dave-cheney] verify that Juju works with gccgo: TODO Upload juju-core point release: TODO Work items for ubuntu-13.07: Upload juju-core point release: TODO Work items for ubuntu-13.08: Upload juju-core point release: TODO Work items for ubuntu-13.09: Upload juju-core point release: TODO Work items for ubuntu-13.10: Upload juju-core final release: TODO Enable ARM support: TODO Backport juju-core to 12.04, 12.10 and 13.04: TODO Work items: Investigate automated releases of juju-core into Ubuntu: TODO -- Delivering Juju 2.0 into Ubuntu https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-2-delivery -- 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
[Blueprint servercloud-s-seeded-qa-workflow] Improving QA for seeded server packages
Blueprint changed by Yolanda Robla: Work items changed: Work items: [andreserl] write dep-8 test for heartbeat/corosync/pacemaker: TODO [andreserl] write dep-8 test for tftpd-hpa: TODO [gandelman-a] write dep-8 test for haproxy: TODO [gandelman-a] write dep-8 tests puppet + facter: TODO Get all tests automated by QA team: DONE [ivoks] write dep-8 test for bacula: TODO [yolanda] write dep-8 test for ganglia: DONE [yolanda] write dep-8 test for iscsitarget: DONE [james-page] write dep-8 test for jenkins: TODO [yolanda] write dep-8 test for nagios3: DONE [yolanda] write dep-8 test for open-iscsi: DONE - [yolanda] write dep-8 test for quagga: TODO - [james-page] write dep-8 test for radvd: TODO + [yolanda] write dep-8 test for quagga: DONE + [yolanda] write dep-8 test for radvd: TODO [james-page] write dep-8 test for solr-tomcat/jetty: TODO [james-page] write dep-8 test for tgt: TODO [james-page] write dep-8 test for openvswitch: DONE [james-page] Write some guidelines for test authors so we get things right first time: TODO [james-page] Update https://wiki.ubuntu.com/QATeam/RequiredTests where appropriate: DONE [pcarrier] write dep-8 test for munin: TODO [racb] write dep-8 test for clamav: TODO [racb] write dep-8 test for exim4: TODO [racb] write dep-8 test for mailman: TODO [racb] write dep-8 test for memcached: TODO [racb] write dep-8 test for squid3: TODO [racb] write dep-8 test for varnish: TODO [racb] write dep-8 test for vsftpd: TODO review backuppc for continued seed inclusion: TODO review likewise-open for continued seed inclusion: TODO [serge-hallyn] write dep-8 test for kvm: TODO [serge-hallyn] write dep-8 test for lxc: DONE [yolanda] write dep-8 test for amavisd-new: DONE [yolanda] write dep-8 test for nut: DONE [yolanda] write dep-8 test for postfix: DONE [yolanda] write dep-8 test for slapd/openldap: DONE [pcarrier] write dep-8 test for snmpd: TODO [yolanda] write dep-8 test for spamassassin: DONE [zulcss] write dep-8 test for freeradius: TODO [zulcss] write dep-8 test for rabbitmq-server: TODO -- Improving QA for seeded server packages https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-seeded-qa-workflow -- 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 1180084] Re: nova-conductor should be in main
** Changed in: nova (Ubuntu Saucy) Status: Triaged = In Progress -- 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/1180084 Title: nova-conductor should be in main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1180084/+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 1180084] Re: nova-conductor should be in main
** Branch linked: lp:~ubuntu-core-dev/ubuntu-seeds/platform.saucy -- 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/1180084 Title: nova-conductor should be in main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1180084/+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 1181135] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: open-vm-tools (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1181135 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1181135/+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 1181135] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
i try a new kernel install with synaptic -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1181135 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1181135/+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 1164107] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
i have 3.2.kernel i uptade a kernel install with synaptic -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1164107 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1164107/+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 1181265] [NEW] acquire followed quickly by start may not start system
Public bug reported: I'm using some tools (maas-deploy-node [1]) to quickly call 'acquire' and then 'start' for a node, and I often end up with the node not being powered on. I have to add some sleeps to work around. -- [1] http://bazaar.launchpad.net/~virtual-maasers/+junk/maas-libvirt-utils/view/head:/maas-deploy-node ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: maas-region-controller 1.3+bzr1461+dfsg-0ubuntu2 [modified: usr/share/maas/preseeds/preseed_xinstall] ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri May 17 10:49:26 2013 InstallationDate: Installed on 2011-11-16 (547 days ago) InstallationMedia: Ubuntu-Server 11.10 Oneiric Ocelot - Release amd64 (20111011) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=screen-bce PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: python-django-maas 1.3+bzr1461+dfsg-0ubuntu2 apparmor 2.8.0-0ubuntu11 SourcePackage: maas UpgradeStatus: Upgraded to raring on 2013-05-09 (8 days ago) modified.conffile..etc.maas.maas.local.celeryconfig.py: [inaccessible: [Errno 13] Permission denied: '/etc/maas/maas_local_celeryconfig.py'] ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1181265 Title: acquire followed quickly by start may not start system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1181265/+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 1181263] [NEW] no 'poweroff' template for pxe boot
Public bug reported: After re-discovering bug 1074317 (the fact that 'system_id' means nothing to 'acquire'), I found that if a node is powered on when not expected maas-pserv will first repeatedly stack trace and then the 'default' (enlistment) profile will be run. The additional information in the exception (poweroff, amd64, generic) are added by me, and I'd suggest that they might be helpful to actually add to the code. 2013-05-17 09:45:40-0400 [HTTPPageGetter,client] Unhandled error in Deferred: 2013-05-17 09:45:40-0400 [HTTPPageGetter,client] Unhandled Error Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 381, in callback self._startRunCallbacks(result) File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 489, in _startRunCallbacks self._runCallbacks() File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 576, in _runCallbacks current.result = callback(current.result, *args, **kw) File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 1127, in gotResult _inlineCallbacks(r, g, deferred) --- exception caught here --- File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 1069, in _inlineCallbacks result = result.throwExceptionIntoGenerator(g) File /usr/lib/python2.7/dist-packages/twisted/python/failure.py, line 389, in throwExceptionIntoGenerator return g.throw(self.type, self.value, self.tb) File /usr/lib/python2.7/dist-packages/tftp/protocol.py, line 67, in _startSession context, self.backend.get_reader, datagram.filename) File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 576, in _runCallbacks current.result = callback(current.result, *args, **kw) File /usr/lib/python2.7/dist-packages/provisioningserver/tftp.py, line 171, in generate_config kernel_params=kernel_params, **params) File /usr/lib/python2.7/dist-packages/provisioningserver/pxe/config.py, line 83, in render_pxe_config kernel_params.subarch) File /usr/lib/python2.7/dist-packages/provisioningserver/pxe/config.py, line 70, in get_pxe_template No PXE template found in %r for %s,%s,%s! % (template_dir, purpose, arch, subarch)) exceptions.AssertionError: No PXE template found in '/usr/lib/python2.7/dist-packages/provisioningserver/pxe' for poweroff,amd64,generic! ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: maas-cluster-controller 1.3+bzr1461+dfsg-0ubuntu2 [modified: usr/sbin/maas-import-ephemerals] ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri May 17 10:48:16 2013 InstallationDate: Installed on 2011-11-16 (547 days ago) InstallationMedia: Ubuntu-Server 11.10 Oneiric Ocelot - Release amd64 (20111011) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=screen-bce PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: maas UpgradeStatus: Upgraded to raring on 2013-05-09 (8 days ago) modified.conffile..etc.maas.maas.cluster.conf: [inaccessible: [Errno 13] Permission denied: '/etc/maas/maas_cluster.conf'] ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1181263 Title: no 'poweroff' template for pxe boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1181263/+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 752172] Re: Logwatch looks for afpd output in messages, not in log files that afpd writes to
*** This bug is a duplicate of bug 794727 *** https://bugs.launchpad.net/bugs/794727 Thanks Craig - I agree. ** This bug has been marked a duplicate of bug 794727 /var/log/messages is empty after upgrade to natty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/752172 Title: Logwatch looks for afpd output in messages, not in log files that afpd writes to To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/752172/+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 1010625] Re: named logs are not being reported in logwatch
@Craig Thanks for taking the time to find the duplicates. I agree with bug 752172 and have marked that duplicate. I disagree on bug 1010602 - samba doesn't log to /var/log/messages; it logs to /var/log/samba/. So I think that is a separate issue and have left it as-is. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010625 Title: named logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010625/+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 334374] Re: libnss-ldap should not depend on libpam-ldap
@Daniel Makes sense to me. Since NSS isn't strictly auth, would it also make sense to rename ldap-auth-config to ldap-config? This area is complex, especially with the delta with Debian in mind. I'm not even considering touching this because I'm worried I'll break something, and it seems like it would take significant effort to verify that all use cases will be fulfilled with any change at all. I think this needs a stakeholder to drive it, particularly with speaking to Debian, coordinating, etc. Since it may have wider implications, I think it makes sense to seek consensus on the Ubuntu mailing lists, too. Volunteers welcome :) -- 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/334374 Title: libnss-ldap should not depend on libpam-ldap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ldap-auth-client/+bug/334374/+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
[Blueprint servercloud-s-ceph] Ceph activities for Saucy
Blueprint changed by James Page: Work items changed: Work items for ubuntu-13.06: [james-page] Enable google-perftools on armhf: DONE - [james-page] Upload cuttlefish to saucy: TODO + [james-page] Upload cuttlefish to saucy: INPROGRESS [james-page] Upload cuttlefish to the havana cloud archive: TODO Work items for ubuntu-13.07: [james-page] Upload dumpling - 4 weeks to saucy: TODO [james-page] Upload dumpling - 2 weeks to saucy: TODO Work items for ubuntu-13.08: [james-page] Upload dumpling to saucy: TODO [james-page] Upload dumpling to the havana cloud archive: TODO [james-page] Write dep8 tests for ceph: TODO Review upstream patches for mod_fastcgi: TODO Review/test ceph RADOS with mod_fcgid: TODO Identify use-cases for ceph performance scenarios: TODO [james-page] Update ceph charms to support cuttlefish features: TODO ceph-deploy packaging: TODO Work items for ubuntu-13.10: [james-page] Regular multi-node ceph testing in the lab: BLOCKED [james-page] Implement more in-depth testing of Ceph to support SRU's: TODO Ceph teuthology tests for deploying with Juju: TODO Ability to use upstream packages in Juju charms: TODO -- Ceph activities for Saucy https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-ceph -- 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 1103022] Re: 70-udev-acl.rules needs to put g+rw on /dev/kvm
Thanks Daviey. confirmed, with quantal-proposed I get crw-rw 1 root kvm 10, 232 May 17 15:43 /dev/kvm ** Description changed: When qemu-system gets installed, the newly installed udev rule causes /dev/kvm to gets chgrpd to kvm and its mode to get set to g+rw. However, because /dev/kvm was tagged with ACL previously, there is a group:: acl on /dev/kvm which does not get removed. Therefore /dev/kvm is g+rw in the file mode, but the acl denies group read/write access. After a reboot all is fine. I have not seen a clean way to have udev remove that acl, and there is no reason for it. So please update the 70-udev-acl.rules file to set MODE=0660 on /dev/kvm SRU Justification 1. Impact: when qemu-kvm is first installed, /dev/kvm is not owned by group kvm (until subsequent reboot). This prevents libvirt from using kvm until a reboot. 2. Development fix: add group kvm during preinst. (this was done in precise, but accidentally dropped in a merge from debian in quantal) 3. Stable fix: same as development fix - 4. Test case: Create a new quantal vm. sudo apt-get install qemu-kvm. ls -l /dev/kvm, check that it is owned by group kvm. + 4. Test case: Create a new quantal vm. sudo apt-get install qemu-kvm. ls -l /dev/kvm, check that it is owned by group kvm. Note if you've install qemu-kvm previously, purging it is not enough before retesting - you must also remove the kvm group entry. 5. Regression potential: none ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1103022 Title: 70-udev-acl.rules needs to put g+rw on /dev/kvm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1103022/+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 1181135] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
Thank you for taking the time to report this bug and helping to make Ubuntu better. I think the underlying cause is that you're using the Quantal Hardware Enablement Stack, which supplies a 3.5 kernel, whereas 12.04 originally shipped with a 3.2 kernel. Details of this are at: https://wiki.ubuntu.com/Kernel/LTSEnablementStack I'm not sure what the situation is around DKMS modules in the archive and the newer kernel. I've asked for someone to get back to this bug on this issue. In the meantime, if you are able to use the original kernel, then that may work for you. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1181135 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1181135/+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 1181135] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
*** This bug is a duplicate of bug 1083719 *** https://bugs.launchpad.net/bugs/1083719 ** This bug has been marked a duplicate of bug 1157212 just after install Ubuntu LTS12.4.2 in VM vmware player 5.0.1 under WinXP SP3 - open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build ** This bug is no longer a duplicate of bug 1157212 just after install Ubuntu LTS12.4.2 in VM vmware player 5.0.1 under WinXP SP3 - open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build ** This bug has been marked a duplicate of bug 1083719 open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1181135 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1181135/+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 1157212] Re: just after install Ubuntu LTS12.4.2 in VM vmware player 5.0.1 under WinXP SP3 - open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
*** This bug is a duplicate of bug 1083719 *** https://bugs.launchpad.net/bugs/1083719 ** This bug has been marked a duplicate of bug 1083719 open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1157212 Title: just after install Ubuntu LTS12.4.2 in VM vmware player 5.0.1 under WinXP SP3 - open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1157212/+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 1169717] Re: installing vmware client tools - perhaps internet connection dropped during install?
*** This bug is a duplicate of bug 1083719 *** https://bugs.launchpad.net/bugs/1083719 ** This bug is no longer a duplicate of bug 1157212 just after install Ubuntu LTS12.4.2 in VM vmware player 5.0.1 under WinXP SP3 - open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build ** This bug has been marked a duplicate of bug 1083719 open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1169717 Title: installing vmware client tools - perhaps internet connection dropped during install? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1169717/+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 1166687] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
*** This bug is a duplicate of bug 1083719 *** https://bugs.launchpad.net/bugs/1083719 ** This bug is no longer a duplicate of bug 1157212 just after install Ubuntu LTS12.4.2 in VM vmware player 5.0.1 under WinXP SP3 - open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build ** This bug has been marked a duplicate of bug 1083719 open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1166687 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1166687/+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 1083719] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
** Changed in: open-vm-tools (Ubuntu) Importance: Medium = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1083719 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1083719/+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 1164107] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
*** This bug is a duplicate of bug 1083719 *** https://bugs.launchpad.net/bugs/1083719 ** This bug has been marked a duplicate of bug 1083719 open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1164107 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1164107/+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 1083719] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
** Tags added: hwe-dkms -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1083719 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1083719/+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 1083719] Re: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
This is one of the reasons I want to start backporting the newer packages to versions like 12.04. This is part of my Saucy blueprint. But first I want to finish up my work (and proposal) on the Saucy update, as well as submit my developer application. But we have to be really careful, or we'll break stuff that works. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1083719 Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1083719/+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 1181265] Re: acquire followed quickly by start may not start system
** Also affects: maas Importance: Undecided Status: New -- 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/1181265 Title: acquire followed quickly by start may not start system To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1181265/+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 1181334] [NEW] i386 required to install amd64
Public bug reported: A system I was working on had amd64 files for raring imported, but did not have i386. That should be fine, since I'm only hoping to deploy to systems that are identified as amd64. However, trying to allocate and the start a node results in pxe timeout and fallback to 'default' (which is enlistment) and then poweroff. log shows: 2013-05-17 13:44:41-0400 [-] Starting factory HTTPClientFactory: http://localhost/MAAS/api/1.0/pxeconfig/?cluster_uuid=9a4dbe50-1015-4fe1-92ab-d37c34052733local=192.168.20.1mac=18-03-73-fb-d1-cdremote=192.168.20.50 2013-05-17 13:44:41-0400 [HTTPPageGetter,client] Unhandled error in Deferred: 2013-05-17 13:44:41-0400 [HTTPPageGetter,client] Unhandled Error Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 381, in callback self._startRunCallbacks(result) File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 489, in _startRunCallbacks self._runCallbacks() File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 576, in _runCallbacks current.result = callback(current.result, *args, **kw) File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 1127, in gotResult _inlineCallbacks(r, g, deferred) --- exception caught here --- File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 1069, in _inlineCallbacks result = result.throwExceptionIntoGenerator(g) File /usr/lib/python2.7/dist-packages/twisted/python/failure.py, line 389, in throwExceptionIntoGenerator return g.throw(self.type, self.value, self.tb) File /usr/lib/python2.7/dist-packages/tftp/protocol.py, line 67, in _startSession context, self.backend.get_reader, datagram.filename) File /usr/lib/python2.7/dist-packages/twisted/internet/defer.py, line 576, in _runCallbacks current.result = callback(current.result, *args, **kw) File /usr/lib/python2.7/dist-packages/provisioningserver/tftp.py, line 171, in generate_config kernel_params=kernel_params, **params) File /usr/lib/python2.7/dist-packages/provisioningserver/pxe/config.py, line 108, in render_pxe_config return template.substitute(namespace) File /usr/lib/python2.7/dist-packages/tempita/__init__.py, line 173, in substitute result, defs, inherit = self._interpret(ns) File /usr/lib/python2.7/dist-packages/tempita/__init__.py, line 184, in _interpret self._interpret_codes(self._parsed, ns, out=parts, defs=defs) File /usr/lib/python2.7/dist-packages/tempita/__init__.py, line 212, in _interpret_codes self._interpret_code(item, ns, out, defs) File /usr/lib/python2.7/dist-packages/tempita/__init__.py, line 235, in _interpret_code base = func(base) File /usr/lib/python2.7/dist-packages/provisioningserver/pxe/config.py, line 100, in kernel_command return compose_kernel_command_line(params) File /usr/lib/python2.7/dist-packages/provisioningserver/kernel_opts.py, line 176, in compose_kernel_command_line options += compose_purpose_opts(params) File /usr/lib/python2.7/dist-packages/provisioningserver/kernel_opts.py, line 130, in compose_purpose_opts get_ephemeral_name(params.release, params.arch)) File /usr/lib/python2.7/dist-packages/provisioningserver/kernel_opts.py, line 107, in get_ephemeral_name 'maas-import-pxe-files'. % root) provisioningserver.kernel_opts.EphemeralImagesDirectoryNotFound: The directory containing the ephemeral images/info is missing (u'/var/lib/maas/ephemeral/raring/ephemeral/i386'). Make sure to run the script 'maas-import-pxe-files'. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: python-maas-provisioningserver 1.3+bzr1461+dfsg-0ubuntu2 [modified: usr/share/pyshared/provisioningserver/pxe/config.py usr/share/pyshared/provisioningserver/pxe/install_image.py] ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri May 17 13:48:55 2013 InstallationDate: Installed on 2011-11-16 (548 days ago) InstallationMedia: Ubuntu-Server 11.10 Oneiric Ocelot - Release amd64 (20111011) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=screen-bce PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: maas UpgradeStatus: Upgraded to raring on 2013-05-09 (8 days ago) ** Affects: maas Importance: Undecided Status: New ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring ** Also affects: maas Importance: Undecided Status: New -- 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/1181334 Title: i386 required to install amd64 To manage
[Bug 1181263] Re: no 'poweroff' template for pxe boot
** Also affects: maas Importance: Undecided Status: New -- 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/1181263 Title: no 'poweroff' template for pxe boot To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1181263/+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 1010625] Re: named logs are not being reported in logwatch
Every service that specifies 'LogFile = messages' in its LogWatch .conf file (there are 40 of them) is now dead in LogWatch. I would propose one of the following fixes: 1) Remove the 'LogFile = messages' line completely from all of the aforementioned .conf files. The result will be that the default location(s) will be searched/parsed for messages. The current default is 'All' This is simple and straightforward. Or... 2) Change the 'LogFile = messages' line to 'LogFile = syslog' in all of the aforementioned .conf files. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010625 Title: named logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010625/+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 1179707] Re: Meta bug for tracking OpenStack 2012.2.4 Stable Update
** Also affects: cloud-archive Importance: Undecided Status: New ** Changed in: cloud-archive Status: New = In Progress ** Changed in: cloud-archive Assignee: (unassigned) = Adam Gandelman (gandelman-a) -- 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/1179707 Title: Meta bug for tracking OpenStack 2012.2.4 Stable Update To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1179707/+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 1179626] Re: Meta bug for tracking Openstack 2013.1.1 Stable Update
** Changed in: cloud-archive Status: New = In Progress ** Changed in: cloud-archive Assignee: (unassigned) = Adam Gandelman (gandelman-a) -- 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/1179626 Title: Meta bug for tracking Openstack 2013.1.1 Stable Update To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1179626/+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 1098299] Re: entropy pool should be seeded earlier in boot process
I think I would argue that the bug here is on the side of the ssh upstart job, which has a start condition of: start on filesystem or runlevel [2345] /etc/rcS.d/S*urandom is guaranteeably run (via /etc/init/rc- sysinit.conf) before 'runlevel' is emitted. So the question is, why does ssh need to start on 'filesystem', instead of waiting for 'runlevel'? rc-sysinit itself runs (and fires off the 'runlevel' event) as soon as it sees: start on (filesystem and static-network-up) or failsafe-boot So in the common case, the only difference between the current behavior and a 'start on runlevel' is that ssh will start before the network is up, which seems of dubious value given the nature of the service. In the pathological case, since 'failsafe-boot' is guaranteed to trigger after a timeout, the system will still boot and ssh will still come up, it may just not come up as quickly as it does currently. I think we do want to translate /etc/init.d/urandom to an upstart job - I frankly am just not sure at present how to write it correctly to ensure it sequences before ssh without adding a lot of syntactic boilerplate, given that urandom can't run until the filesystem is up (for access to /var/lib), and 'start on starting ssh' is not right either. ** Changed in: sysvinit (Ubuntu) Assignee: (unassigned) = Steve Langasek (vorlon) -- 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/1098299 Title: entropy pool should be seeded earlier in boot process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/installation-report/+bug/1098299/+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
Re: [Bug 592610] Re: Shared folders (through Samba) when following instructions sometimes does not work correctly
On Thu, May 16, 2013 at 2:30 PM, julius von kohout 592...@bugs.launchpad.net wrote: are you referring to root share or usershare? root shares work properly and they are meant to be done by fiddling with smb.conf I don't understand the distinction you're making. This bug report was about attempting to share files in Nautilus- is that a 'root share' or a 'usershare'? I don't have the old setup to test any more. I've since rebuilt the computer and it now runs Debian Sid. The samba shares are the same, but I did not try to use Nautilus to set them up (I use xfce now). What I was trying to accomplish was an anonymous public read-only share on /media/share. It didn't work then (using Nautilus) and it doesn't work now (having tried via editing smb.conf and using 'net usershare'). Samba currently doesn't work at all: when I try to connect, I get error could not download share list from server. When it does work (apparently at random), samba *always* prompts for a username and password, regardless of configuration. When configured with username and password, it sometimes works and sometimes does not. The workaround cited in my report stopped working a day or so later. I should have updated the report at that time, but the bug was marked 'invalid' anyway and I was too discouraged to mess with it any further. I don't need samba for authenticated shares, sshfs works fine for that. Thanks for the information and advice, I'm sorry that it doesn't apply more directly to the situation at hand. I tried to test permissions for 'nobody' on the shared directory, but I can't su to nobody. The directory's mode is 744 if that helps. user share via nautilus does not work properly private shares with password (its automatically your login password) work. public (guest) shares in the home directory dont work because samba cannot cd into /home because /home defaul permissons are to strict for nobody which is the guest/public samba user. i had a long talk with the maintainer of nautilus-share. there are several possible fixes. 1. set homedirectoy permissons for eveyone else properly 2. add force user = owner of the /home/'your username' directoy to smb.con and map to guest = bad password -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/592610 Title: Shared folders (through Samba) when following instructions sometimes does not work correctly Status in “samba” package in Ubuntu: Confirmed Bug description: Binary package hint: samba SUMMARY: Following instructions to create a shared folder through Nautilus (right-click Sharing Options Share this folder, and following the subsequent prompts) does not always work. For some people, it works immediately. For other people, a solution has been found, which requires extra steps. I found this a problem across a small network of five computers: - one 64-bit Ubuntu (Lucid 10.04) - two 32-bit Ubuntu (Lucid 10.04) - one 32-bit Xubuntu (Lucid 10.04) - one Windows Vista. Every Ubuntu computer had the identical problem. Other people have reported having this problem. Examples: http://ubuntuforums.org/showthread.php?t=1491092 http://ubuntuforums.org/showthread.php?t=1502265 SYMPTOMS: When it works, everything works properly and quickly. But when it does not work... The shares appear to be created correctly. Using terminal commands, it is found that the machines do in fact connect. However, in Nautilus, the network takes approximately a minute to respond and then fails to find the shares. DISCOVERED SOLUTION: 1. Add the following two lines under the [global] section in file /etc/smb.conf in every Ubuntu and Xubuntu machine: os level = 33 name resolve order = bcast host lmhosts wins 2. Reboot. 3. Some people find that they have to experiment with the order of items in name resolve order. EXTRA INFORMATION: Package versions according to Synaptic (from the default repositories): - samba 2:3.4.7~dfsg-1ubuntu3 - nautilus-share 0.7.2-12build1 - system-config-samba 1.2.63-0ubuntu4 REQUIRED ACTION: Shared folders should work through the GUI without workarounds and fiddling, just as Windows and Mac do. It should not be necessary to get onto the forum, search, and mess with /etc/smb.conf. (It took over a week for me to discover the answer.) ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: samba 2:3.4.7~dfsg-1ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 Architecture: amd64 CheckboxSubmission: 5bf569339afeaacf6d8dcc180d0a06f0 CheckboxSystem: b1865df84255b8716d3bcc269ff410d1 Date: Fri Jun 11 11:33:18 2010 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8
[Bug 1121933] [NEW] umountroot remounts partition readonly when called from libvirt/lxc guest
You have been subscribed to a public bug: When a libvirt/lxc guest resides on a partition, which is not /, /etc/init.d/umountroot will remount that partition read-only on a shutdown -r now in the guest. Our current workaround is to use grep -zq '^LIBVIRT_LXC_UUID=' /proc/1/environ if [ $? -eq 0 ]; then echo LXC Container, not mounting / ro... else mount$MOUNT_FORCE_OPT -n -o remount,ro -t dummytype dummydev / 2/dev/null \ || mount $MOUNT_FORCE_OPT -n -o remount,ro dummydev / 2/dev/null \ || mount $MOUNT_FORCE_OPT -n -o remount,ro / ES=$? [ $VERBOSE = no ] || log_action_end_msg $ES fi # dpkg -l lxc libvirt-bin | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++---== ii libvirt-bin 0.9.8-2ubuntu17.7programs for the libvirt library ii lxc 0.7.5-3ubuntu66 Linux containers userspace tools # lsb_release -dr Description:Ubuntu 12.04.1 LTS Release:12.04 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- umountroot remounts partition readonly when called from libvirt/lxc guest https://bugs.launchpad.net/bugs/1121933 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. -- 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 1121933] Re: umountroot remounts partition readonly when called from libvirt/lxc guest
I don't think this is a sysvinit issue. Where lxc is not correctly emulating a normal system, that should be fixed in lxc. ** Package changed: sysvinit (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/1121933 Title: umountroot remounts partition readonly when called from libvirt/lxc guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1121933/+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 1121933] Re: umountroot remounts partition readonly when called from libvirt/lxc guest
No it won't, lxc keeps a file open to prevent specifically that from happening and we also prevent remounts in our apparmor profile, so what you're describing is impossible under lxc. ** Changed in: lxc (Ubuntu) Status: New = Invalid -- 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/1121933 Title: umountroot remounts partition readonly when called from libvirt/lxc guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1121933/+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 592610] Re: Shared folders (through Samba) when following instructions sometimes does not work correctly
Via nautilus is usershare. Via smb.conf is root share. Try to set permissions of home to 755 and make a share /home/public If you make a public share samba uses nobody/other as user to change to that directory. Its the last digit of dir permissions that is used. You can see that if you run samba with debug level. But the best way is to use the smb.config edits from above the you can share folders in /home and external ext4 drive like i do. -- 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/592610 Title: Shared folders (through Samba) when following instructions sometimes does not work correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/592610/+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 1010625] [NEW] named logs are not being reported in logwatch
You have been subscribed to a public bug: After upgrading from 10.04 to 12.04 named logs no longer show up in logwatch reports. Not sure if this should be filed as a bug against rsyslog or logwatch. There was a change to /etc/rsyslog.d/50-default.conf between 10.04 and 12.04 and a bunch of the seperate log files are now commented out and most things are only in /var/log/syslog Since the /usr/share/logwatch/default.conf/services/named.conf lists messages as the log file it never reports any log data. I changed my /etc/rsyslog.d/50-default.conf by uncommenting these lines (match the config in 10.04): daemon. lpr. user. mail.info mail.warn *.=debug *.=info The last one above sends most stuff to the messages file so named logs entries show up in logwatch reports after making the above changes. Part of me believes rsyslog should be considered the problem but on the other hand if rsyslog is correct then logwatch's named.conf needs to be overiden in dist.conf to correct for the rsyslog change. 1. Description: Ubuntu 12.04 LTS Release: 12.04 2. logwatch: Installed: 7.4.0+svn20111221rev79-1ubuntu1 Candidate: 7.4.0+svn20111221rev79-1ubuntu1 Version table: *** 7.4.0+svn20111221rev79-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status bind9: Installed: 1:9.8.1.dfsg.P1-4 Candidate: 1:9.8.1.dfsg.P1-4ubuntu0.1 Version table: 1:9.8.1.dfsg.P1-4ubuntu0.1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages *** 1:9.8.1.dfsg.P1-4 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status rsyslog: Installed: 5.8.6-1ubuntu8 Candidate: 5.8.6-1ubuntu8 Version table: *** 5.8.6-1ubuntu8 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status 3. Logwatch reports/emails should contain named log information. 4. No named log information shows up in logwatch reports/emails. ** Affects: logwatch (Ubuntu) Importance: Medium Status: Confirmed -- named logs are not being reported in logwatch https://bugs.launchpad.net/bugs/1010625 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. -- 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 1121933] Re: umountroot remounts partition readonly when called from libvirt/lxc guest
The bug submitter mentioned libvirt/lxc. I don't believe it has any of the protections which lxc has against this. ** Package changed: lxc (Ubuntu) = libvirt (Ubuntu) ** Changed in: libvirt (Ubuntu) Importance: Undecided = High ** Changed in: libvirt (Ubuntu) Status: Invalid = New -- 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/1121933 Title: umountroot remounts partition readonly when called from libvirt/lxc guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1121933/+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 1010625] Re: named logs are not being reported in logwatch
Reference upstream rsyslog Bug #794727: /var/log/messages is empty after upgrade to natty ** Package changed: logwatch (Ubuntu) = rsyslog (Ubuntu) ** Changed in: rsyslog (Ubuntu) Status: Triaged = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010625 Title: named logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010625/+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 1010625] Re: named logs are not being reported in logwatch
** Package changed: rsyslog (Ubuntu) = logwatch (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1010625 Title: named logs are not being reported in logwatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1010625/+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
Re: [Bug 592610] Re: Shared folders (through Samba) when following instructions sometimes does not work correctly
On Fri, May 17, 2013 at 3:36 PM, julius von kohout 592...@bugs.launchpad.net wrote: Via nautilus is usershare. Via smb.conf is root share. Cool, thanks! Try to set permissions of home to 755 and make a share /home/public If you make a public share samba uses nobody/other as user to change to that directory. Its the last digit of dir permissions that is used. You can see that if you run samba with debug level. OK, I will try that sometime this weekend and report back. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/592610 Title: Shared folders (through Samba) when following instructions sometimes does not work correctly Status in “samba” package in Ubuntu: Confirmed Bug description: Binary package hint: samba SUMMARY: Following instructions to create a shared folder through Nautilus (right-click Sharing Options Share this folder, and following the subsequent prompts) does not always work. For some people, it works immediately. For other people, a solution has been found, which requires extra steps. I found this a problem across a small network of five computers: - one 64-bit Ubuntu (Lucid 10.04) - two 32-bit Ubuntu (Lucid 10.04) - one 32-bit Xubuntu (Lucid 10.04) - one Windows Vista. Every Ubuntu computer had the identical problem. Other people have reported having this problem. Examples: http://ubuntuforums.org/showthread.php?t=1491092 http://ubuntuforums.org/showthread.php?t=1502265 SYMPTOMS: When it works, everything works properly and quickly. But when it does not work... The shares appear to be created correctly. Using terminal commands, it is found that the machines do in fact connect. However, in Nautilus, the network takes approximately a minute to respond and then fails to find the shares. DISCOVERED SOLUTION: 1. Add the following two lines under the [global] section in file /etc/smb.conf in every Ubuntu and Xubuntu machine: os level = 33 name resolve order = bcast host lmhosts wins 2. Reboot. 3. Some people find that they have to experiment with the order of items in name resolve order. EXTRA INFORMATION: Package versions according to Synaptic (from the default repositories): - samba 2:3.4.7~dfsg-1ubuntu3 - nautilus-share 0.7.2-12build1 - system-config-samba 1.2.63-0ubuntu4 REQUIRED ACTION: Shared folders should work through the GUI without workarounds and fiddling, just as Windows and Mac do. It should not be necessary to get onto the forum, search, and mess with /etc/smb.conf. (It took over a week for me to discover the answer.) ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: samba 2:3.4.7~dfsg-1ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 Architecture: amd64 CheckboxSubmission: 5bf569339afeaacf6d8dcc180d0a06f0 CheckboxSystem: b1865df84255b8716d3bcc269ff410d1 Date: Fri Jun 11 11:33:18 2010 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: nautilus 1:2.30.1-0ubuntu1 gvfs 1.6.1-0ubuntu1build1 SambaClientRegression: Yes SourcePackage: samba To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/592610/+subscriptions -- a href=http://www.fsf.org/fb;img src= http://static.fsf.org/nosvn/no-facebook-me.png; alt=Not f'd — you won't find me on Facebook //a -- 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/592610 Title: Shared folders (through Samba) when following instructions sometimes does not work correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/592610/+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 1181447] [NEW] package keystone 1:2013.1-0ubuntu1.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Public bug reported: Upgrade from Quantal to Raring ProblemType: Package DistroRelease: Ubuntu 13.04 Package: keystone 1:2013.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sat May 18 01:46:26 2013 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-04-05 (42 days ago) InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 (20121017.2) MarkForUpload: True PackageArchitecture: all SourcePackage: keystone Title: package keystone 1:2013.1-0ubuntu1.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to raring on 2013-05-18 (0 days ago) ** Affects: keystone (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package raring -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1181447 Title: package keystone 1:2013.1-0ubuntu1.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1181447/+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 1149410] Re: Stuck on Trying to connect to the Juju environment
[Expired for juju (Ubuntu) because there has been no activity for 60 days.] ** Changed in: juju (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1149410 Title: Stuck on Trying to connect to the Juju environment To manage notifications about this bug go to: https://bugs.launchpad.net/juju-gui/+bug/1149410/+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