[Bug 27121] Re: The 'mail' command is not encoding the user name correctly
** Changed in: mailx (Debian) Status: New = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mailx in Ubuntu. https://bugs.launchpad.net/bugs/27121 Title: The 'mail' command is not encoding the user name correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailx/+bug/27121/+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 1236065] Re: Crypto support missing in Saucy
** Bug watch added: Debian Bug tracker #696390 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696390 ** Also affects: ntp (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696390 Importance: Unknown Status: Unknown ** Changed in: ntp (Ubuntu) Status: In Progress = Confirmed ** Changed in: ntp (Ubuntu) Assignee: Tyler Hicks (tyhicks) = (unassigned) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1236065 Title: Crypto support missing in Saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1236065/+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 1236065] Re: Crypto support missing in Saucy
** Changed in: ntp (Debian) Status: Unknown = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1236065 Title: Crypto support missing in Saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1236065/+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 242313] Re: TLS_CACERTDIR not supported in gnutls
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnutls26 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/242313 Title: TLS_CACERTDIR not supported in gnutls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/242313/+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 1236265] [NEW] vmghfs not being build
Public bug reported: Updated to Saucy and not the vmware shared folders don't work anymore. Seems that the module vmghfs is not being build by dkms. Steps to reproduce: - Install open-vm-tools, then via cml: vm@vmrk:~$ vmware-hgfsclient Downloads vm@vmrk:~$ sudo vmware-hgfsmounter .host:/Downloads /media/host/ Error: cannot mount filesystem: No such device vm@vmrk:~$ sudo modprobe vmhgfs FATAL: Module vmhgfs not found. vm@vmrk:~$ lsb_release -rd Description:Ubuntu Saucy Salamander (development branch) Release:13.10 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: open-vm-tools 2013.04.16-1098359-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Mon Oct 7 11:51:45 2013 InstallationDate: Installed on 2012-08-25 (408 days ago) InstallationMedia: Kubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120820.1) MarkForUpload: True SourcePackage: open-vm-tools UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.vmware.tools.tools.conf: mtime.conffile..etc.vmware.tools.tools.conf: 2013-10-07T11:15:12.283459 ** Affects: open-vm-tools (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 open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1236265 Title: vmghfs not being build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1236265/+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 1235231] Re: ci-info: eth0 not reliable in latest saucy images
Upstart certainly changed, but none of the changes affect console handling. Could the kernel change be the culprit maybe? -- 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/1235231 Title: ci-info: eth0 not reliable in latest saucy images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1235231/+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 1236299] [NEW] ssh-agent env variables not set when not using Bourne shell
Public bug reported:
When I start an X session (default gnome/unity setup) I find that ssh-
agent is started but the appropriate environment variables
(SSH_AGENT_PID, SSH_AUTH_SOCK) are not set. .xsession-errors contains:
init: ssh-agent pre-start process (1797) terminated with status 127
The problem appears to be in /usr/share/upstart/sessions/ssh-agent.conf.
It evals ssh-agent expecting the output to be valid Bourne shell syntax
however ssh-agent checks (IIUC) the user's shell and output C shell
style code if the user is using a C based shell. I use tcsh and so get
output like 'setenv SSH_AGENT_PID ...' from ssh-agent. This of course
fails to set any environment variables in the Bourne shell script that
the upstart job effectively is.
Luckily ssh-agent has a flag to ask for Bourne shell syntax.
--- ssh-agent.conf.orig 2013-10-07 11:30:08.546222472 +0200
+++ ssh-agent.conf 2013-10-07 11:30:30.858221774 +0200
@@ -7,7 +7,7 @@
[ -e /etc/X11/Xsession.options ] || { stop; exit 0; }
grep -q ^use-ssh-agent$ /etc/X11/Xsession.options || { stop; exit 0; }
-eval $(ssh-agent) /dev/null
+eval $(ssh-agent -s) /dev/null
initctl set-env --global SSH_AUTH_SOCK=$SSH_AUTH_SOCK
initctl set-env --global SSH_AGENT_PID=$SSH_AGENT_PID
end script
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: openssh-client 1:6.2p2-6 [modified:
usr/share/upstart/sessions/ssh-agent.conf]
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Mon Oct 7 12:50:45 2013
InstallationDate: Installed on 2013-06-28 (101 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64
(20130213)
MarkForUpload: True
RelatedPackageVersions:
ssh-askpass N/A
libpam-sshN/A
keychain N/A
ssh-askpass-gnome 1:6.2p2-6
SSHClientVersion: OpenSSH_6.2p2 Ubuntu-6, OpenSSL 1.0.1e 11 Feb 2013
SourcePackage: openssh
UpgradeStatus: Upgraded to saucy on 2013-09-23 (14 days ago)
** Affects: openssh (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 openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1236299
Title:
ssh-agent env variables not set when not using Bourne shell
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1236299/+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 1236065] Re: Crypto support missing in Saucy
** Branch linked: lp:ubuntu/saucy-proposed/ntp -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1236065 Title: Crypto support missing in Saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1236065/+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 1236065] Re: Crypto support missing in Saucy
This bug was fixed in the package ntp - 1:4.2.6.p5+dfsg-3ubuntu1
---
ntp (1:4.2.6.p5+dfsg-3ubuntu1) saucy; urgency=low
* Merge from Debian testing to regain crypto support (LP: #1236065). Remaining
changes:
+ debian/ntp.conf, debian/ntpdate.default: Change default server to
ntp.ubuntu.com.
+ debian/ntpdate.if-up: Stop ntp before running ntpdate when an interface
comes up, then start again afterwards.
+ debian/ntp.init, debian/rules: Only stop when entering single user mode.
+ Add enforcing AppArmor profile:
- debian/control: Add Conflicts/Replaces on apparmor-profiles.
- debian/control: Add Suggests on apparmor.
- debian/ntp.dirs: Add apparmor directories.
- debian/ntp.preinst: Force complain on certain upgrades.
- debian/ntp.postinst: Reload apparmor profile.
- debian/ntp.postrm: Remove the force-complain file.
- add debian/apparmor-profile*.
- debian/rules: install apparmor-profile and apparmor-profile.tunable.
- debian/README.Debian: Add note on AppArmor.
+ debian/{control,rules}: Add and enable hardened build for PIE.
+ debian/rules, debian/ntp.dirs, debian/source_ntp.py: Add apport hook.
+ debian/ntpdate-debian: Disregard empty ntp.conf files.
+ debian/ntp.preinst: Remove empty /etc/ntp.conf on fresh intallation.
+ debian/ntpdate.if-up: Fix interaction with openntpd.
+ debian/source_ntp.py: Add filter on AppArmor profile names to prevent
false positives from denials originating in other packages.
+ debian/rules: Update config.{guess,sub} for AArch64.
ntp (1:4.2.6.p5+dfsg-3) unstable; urgency=low
* Look for openssl/opensslv.h rather than openssl/opensslconf.h, which
is due to move to a different location in order to support multiarch.
Patch by Colin Watson cjwat...@ubuntu.com (Closes: #696390)
-- Tyler Hicks tyhi...@canonical.com Sun, 06 Oct 2013 12:34:00 -0700
** Changed in: ntp (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1236065
Title:
Crypto support missing in Saucy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1236065/+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 1187001] Re: saslauthd[26791]: segfault at 0 ip b71de6f1 sp bfcd2d9c error 4 in libc-2.17.so[b7160000+1ad000]
This issue only affects Raring and newer. Already fixed in saucy. ** Also affects: cyrus-sasl2 (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: cyrus-sasl2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: cyrus-sasl2 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: cyrus-sasl2 (Ubuntu Saucy) Importance: High Status: Confirmed ** Also affects: cyrus-sasl2 (Ubuntu Raring) Importance: Undecided Status: New ** Changed in: cyrus-sasl2 (Ubuntu Lucid) Status: New = Invalid ** Changed in: cyrus-sasl2 (Ubuntu Precise) Status: New = Invalid ** Changed in: cyrus-sasl2 (Ubuntu Raring) Importance: Undecided = Medium ** Changed in: cyrus-sasl2 (Ubuntu Raring) Status: New = Confirmed ** Changed in: cyrus-sasl2 (Ubuntu Raring) Assignee: (unassigned) = Marc Deslauriers (mdeslaur) ** Changed in: cyrus-sasl2 (Ubuntu Quantal) Status: New = Invalid ** Changed in: cyrus-sasl2 (Ubuntu Saucy) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1187001 Title: saslauthd[26791]: segfault at 0 ip b71de6f1 sp bfcd2d9c error 4 in libc-2.17.so[b716+1ad000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1187001/+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 1235231] Re: ci-info: eth0 not reliable in latest saucy images
So, some more information.. this bug is fixed by doing: for x in /etc/init/plymouth*; do sudo mv $x $x.disabled; done after doing so 100% of /dev/console output makes it to the console (whoohoo!). that lays this squarely on plymouth. There is some conversation with slangasek, smoser and utlemming at http://irclogs.ubuntu.com/2013/10/04/%23ubuntu-devel.html#t18:07 . Steve thinks its not entirely unreasonable to just disable plymouth via .override files in cloud-images. I think he would suggest that that be done at the package level and be handled by cloud-init. That wasn't clear to me though. Given the above, this is clearly a plymouth bug, its supposed to replay output that it captured, but it is losing some. ** Package changed: upstart (Ubuntu) = plymouth (Ubuntu) ** Changed in: plymouth (Ubuntu) Status: New = Confirmed ** Changed in: plymouth (Ubuntu) Importance: Undecided = High -- 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/1235231 Title: plymouth loses output to /dev/console (such as ci-info: messages) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1235231/+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 1235231] Re: ci-info: eth0 not reliable in latest saucy images
** Description changed: + During early boot, plymouth captures writes to /dev/console. As I + understand it, it is supposed to re-play that content later. Whether or + not it intends to is not the issue. In our cloud-images (and in other + cases) users may write data to /dev/console that needs to be seen on the + other side (ie a serial logger or 'get-console-ouptput' api call). + + See the attached 'my-logger.conf' for an upstart job that simply writes + data early in boot to /dev/console. Sometimes data lost is available + in /var/log/boot.log, but sometimes it doesn't even seem to make it + there. + + Related bugs: + * bug 682831: lost console output early in boot + + == Original bug report == On precise cloud images, I get a console output line like this: ci-info: eth0 : 1 192.168.122.204 255.255.255.0 52:54:00:7f:d8:ca^M On saucy cloud images, this is missing. ** Summary changed: - ci-info: eth0 not reliable in latest saucy images + plymouth loses output to /dev/console (such as ci-info: messages) -- 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/1235231 Title: plymouth loses output to /dev/console (such as ci-info: messages) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1235231/+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 1236361] [NEW] need new simple streams based maas-import-ephemerals
Public bug reported: As currently packaged in Ubuntu maas does not use the new import-ephemerals script. As discussed http://irclogs.ubuntu.com/2013/10/07/%23maas.html#t12:46 , this is pretty important to get in. The reasons we need this in 13.10 (and thus Ubuntu cloud archive 'tools' pocket) are: a.) The current version does not clean up Because it doesn't delete old versions of the ephemeral images, updates on the server side will eventually consume all local disk space. The fast path installer uses ephemeral images, we thus have a larger interest in updating these images frequently, so installed systems have all applied updates inside. b.) it fixes security bug 1039513 c.) I believe it fixes bug 1031582. ** Affects: maas Importance: Undecided Status: Confirmed ** Affects: maas (Ubuntu) Importance: Critical Status: Confirmed ** Also affects: maas (Ubuntu) Importance: Undecided Status: New ** Changed in: maas (Ubuntu) Status: New = Confirmed ** Changed in: maas (Ubuntu) Importance: Undecided = Critical ** Changed in: maas Status: New = Confirmed -- 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/1236361 Title: need new simple streams based maas-import-ephemerals To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1236361/+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 1236367] [NEW] [FFe] ceph 0.67.4 point release
Public bug reported: This point release fixes an important performance issue with radosgw, keystone authentication token caching, and CORS. All users (especially those of rgw) are encouraged to upgrade. Notable changes: * crush: fix invalidation of cached names * crushtool: do not crash on non-unique bucket ids * mds: be more careful when decoding LogEvents * mds: fix heap check debugging commands * mon: avoid rebuilding old full osdmaps * mon: fix 'ceph crush move ...' * mon: fix 'ceph osd crush reweight ...' * mon: fix writeout of full osdmaps during trim * mon: limit size of transactions * mon: prevent both unmanaged and pool snaps * osd: disable xattr size limit (prevents upload of large rgw objects) * osd: fix recovery op throttling * osd: fix throttling of log messages for very slow requests * rgw: drain pending requests before completing write * rgw: fix CORS * rgw: fix inefficient list::size() usage * rgw: fix keystone token expiration * rgw: fix minor memory leaks * rgw: fix null termination of buffer For more detail: * http://ceph.com/docs/master/release-notes/#v0-67-4-dumpling * http://ceph.com/docs/master/_downloads/v0.67.4.txt You can get v0.67.4 from the usual locations: * Git at git://github.com/ceph/ceph.git * Tarball at http://ceph.com/download/ceph-0.67.4.tar.gz * For Debian/Ubuntu packages, see http://ceph.com/docs/master/install/debian * For RPMs, see http://ceph.com/docs/master/install/rpm ___ ** Affects: ceph (Ubuntu) Importance: High Assignee: James Page (james-page) Status: In Progress ** Affects: ceph (Ubuntu Saucy) Importance: High Assignee: James Page (james-page) Status: In Progress ** Also affects: ceph (Ubuntu Saucy) Importance: Undecided Status: New ** Changed in: ceph (Ubuntu Saucy) Status: New = In Progress ** Changed in: ceph (Ubuntu Saucy) Importance: Undecided = High ** Changed in: ceph (Ubuntu Saucy) Assignee: (unassigned) = James Page (james-page) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1236367 Title: [FFe] ceph 0.67.4 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1236367/+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 682831] Re: lost console output early in boot
** Changed in: plymouth (Ubuntu Lucid)
Status: Triaged = Won't Fix
** Changed in: linux-ec2 (Ubuntu)
Status: Confirmed = Invalid
** Changed in: linux-ec2 (Ubuntu Lucid)
Status: Triaged = Invalid
** Changed in: cloud-init (Ubuntu Lucid)
Status: Triaged = Won't Fix
** Description changed:
Binary package hint: plymouth
I see some lost output in the ec2 console log when I boot via pv-grub
(meaning a kernel and ramdisk is loaded from inside the instance).
Some info:
- * changing 'console=hvc0' to 'console=tty0' does not seem to change behavior
- * the lost messages are in /var/log/boot.log
- * disabling plymouth fixes the problem (sudo sh -c 'for x in
/etc/init/plymouth*; do mv ${x} ${x}.disabled; done')
- * I found this when attempting to get lucid able to use pv-grub kernels (Bug
671103)
- * We saw a similar issue in maverick, but when adding 'console=hvc0' it went
away (Bug 606373)
+ * changing 'console=hvc0' to 'console=tty0' does not seem to change behavior
+ * the lost messages are in /var/log/boot.log
+ * disabling plymouth fixes the problem (sudo sh -c 'for x in
/etc/init/plymouth*; do mv ${x} ${x}.disabled; done')
+ * I found this when attempting to get lucid able to use pv-grub kernels (Bug
671103)
+ * We saw a similar issue in maverick, but when adding 'console=hvc0' it went
away (Bug 606373)
+
+ Related bugs:
+ * bug 1235231: plymouth loses output to /dev/console (such as ci-info:
messages)
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: plymouth 0.8.2-2ubuntu2.2
ProcVersionSignature: User Name 2.6.32-310.20-ec2 2.6.32.24+drm33.11
Uname: Linux 2.6.32-310-ec2 i686
Architecture: i386
CurrentDmesg: [ 13.731707] eth0: no IPv6 routers present
Date: Mon Nov 29 19:37:00 2010
DefaultPlymouth: Error: command ['readlink',
'/etc/alternatives/default.plymouth'] failed with exit code 1:
Ec2AMI: ami-8c0c5cc9
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-west-1b
Ec2InstanceType: t1.micro
Ec2Kernel: aki-99a0f1dc
Ec2Ramdisk: unavailable
Lspci:
-
+
Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcCmdLine: root=UUID=ce492d03-a18c-4075-871e-1631ed7e0244 ro console=hvc0
ProcEnviron:
- PATH=(custom, user)
- LANG=en_US.UTF-8
- SHELL=/bin/bash
+ PATH=(custom, user)
+ LANG=en_US.UTF-8
+ SHELL=/bin/bash
ProcFB:
-
+
ProcModules: ipv6 243034 10 - Live 0xe7a5f000
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
--
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/682831
Title:
lost console output early in boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/682831/+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 1235231] Re: plymouth loses output to /dev/console (such as ci-info: messages)
** Description changed: During early boot, plymouth captures writes to /dev/console. As I understand it, it is supposed to re-play that content later. Whether or not it intends to is not the issue. In our cloud-images (and in other cases) users may write data to /dev/console that needs to be seen on the other side (ie a serial logger or 'get-console-ouptput' api call). See the attached 'my-logger.conf' for an upstart job that simply writes data early in boot to /dev/console. Sometimes data lost is available in /var/log/boot.log, but sometimes it doesn't even seem to make it - there. + there. bug 682831 has an attachment 'myhack-init' that does a similar + thing but starts outputting by replacing /sbin/init and then calling + /sbin/init itself. Related bugs: - * bug 682831: lost console output early in boot + * bug 682831: lost console output early in boot == Original bug report == On precise cloud images, I get a console output line like this: ci-info: eth0 : 1 192.168.122.204 255.255.255.0 52:54:00:7f:d8:ca^M On saucy cloud images, this is missing. -- 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/1235231 Title: plymouth loses output to /dev/console (such as ci-info: messages) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1235231/+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-cloud-init] Cloud Init Cloud Image Development for Saucy
Blueprint changed by Scott Moser: Work items changed: Work items for ubuntu-13.09: replace oauth with oauthlib (bug 1118815) (2): POSTPONED - cloud-init support for vendor-data (3): TODO - cloud-init support safe user-disabling of vendor-data (2): TODO + cloud-init support for vendor-data (3): POSTPONED + cloud-init support safe user-disabling of vendor-data (2): POSTPONED [smoser] file feature freeze exception for block device partitioning and formatting. bug 1218506. (1): DONE [utlemming] block device creation support. bug 1218506. (3): TODO 0.7.3 cloud-init release (1): TODO 0.7.3 cloud-init inclusion in 13.10 (1): TODO Work items: cloud-init remove grub-legacy-ec2, depend on pv-grub-menu (1): BLOCKED [utlemming] cloud-utils tool for creating derivative images: POSTPONED [utlemming] cloud-utils tool for creating Azure derivate images: POSTPONED openstack vendor-data blueprint for: DONE openstack vendor-data support: DONE cloud-utils inclusion of vcs-run: DONE cloud-utils cleanup of cloud-run-instances: DONE cloud-init pre-init phase: POSTPONED cloud-init in python3: POSTPONED -- Cloud Init Cloud Image Development for Saucy https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-init -- 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-init] Cloud Init Cloud Image Development for Saucy
Blueprint changed by Scott Moser: Work items changed: Work items for ubuntu-13.09: - replace oauth with oauthlib (bug 1118815) (2): TODO + replace oauth with oauthlib (bug 1118815) (2): POSTPONED cloud-init support for vendor-data (3): TODO cloud-init support safe user-disabling of vendor-data (2): TODO [smoser] file feature freeze exception for block device partitioning and formatting. bug 1218506. (1): DONE [utlemming] block device creation support. bug 1218506. (3): TODO 0.7.3 cloud-init release (1): TODO 0.7.3 cloud-init inclusion in 13.10 (1): TODO Work items: cloud-init remove grub-legacy-ec2, depend on pv-grub-menu (1): BLOCKED [utlemming] cloud-utils tool for creating derivative images: POSTPONED [utlemming] cloud-utils tool for creating Azure derivate images: POSTPONED openstack vendor-data blueprint for: DONE openstack vendor-data support: DONE cloud-utils inclusion of vcs-run: DONE cloud-utils cleanup of cloud-run-instances: DONE cloud-init pre-init phase: POSTPONED cloud-init in python3: POSTPONED -- Cloud Init Cloud Image Development for Saucy https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-init -- 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-init] Cloud Init Cloud Image Development for Saucy
Blueprint changed by Scott Moser: Work items changed: Work items for ubuntu-13.09: replace oauth with oauthlib (bug 1118815) (2): POSTPONED cloud-init support for vendor-data (3): POSTPONED cloud-init support safe user-disabling of vendor-data (2): POSTPONED [smoser] file feature freeze exception for block device partitioning and formatting. bug 1218506. (1): DONE - [utlemming] block device creation support. bug 1218506. (3): TODO + [utlemming] block device creation support. bug 1218506. (3): DONE 0.7.3 cloud-init release (1): TODO 0.7.3 cloud-init inclusion in 13.10 (1): TODO Work items: cloud-init remove grub-legacy-ec2, depend on pv-grub-menu (1): BLOCKED [utlemming] cloud-utils tool for creating derivative images: POSTPONED [utlemming] cloud-utils tool for creating Azure derivate images: POSTPONED openstack vendor-data blueprint for: DONE openstack vendor-data support: DONE cloud-utils inclusion of vcs-run: DONE cloud-utils cleanup of cloud-run-instances: DONE cloud-init pre-init phase: POSTPONED cloud-init in python3: POSTPONED -- Cloud Init Cloud Image Development for Saucy https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-init -- 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-init] Cloud Init Cloud Image Development for Saucy
Blueprint changed by Scott Moser: Work items changed: Work items for ubuntu-13.09: replace oauth with oauthlib (bug 1118815) (2): POSTPONED cloud-init support for vendor-data (3): POSTPONED cloud-init support safe user-disabling of vendor-data (2): POSTPONED [smoser] file feature freeze exception for block device partitioning and formatting. bug 1218506. (1): DONE [utlemming] block device creation support. bug 1218506. (3): DONE + + Work items for ubuntu-13.10: 0.7.3 cloud-init release (1): TODO 0.7.3 cloud-init inclusion in 13.10 (1): TODO Work items: cloud-init remove grub-legacy-ec2, depend on pv-grub-menu (1): BLOCKED [utlemming] cloud-utils tool for creating derivative images: POSTPONED [utlemming] cloud-utils tool for creating Azure derivate images: POSTPONED openstack vendor-data blueprint for: DONE openstack vendor-data support: DONE cloud-utils inclusion of vcs-run: DONE cloud-utils cleanup of cloud-run-instances: DONE cloud-init pre-init phase: POSTPONED cloud-init in python3: POSTPONED -- Cloud Init Cloud Image Development for Saucy https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-init -- 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-fastpath-install] fastpath installer work for 13.10
Blueprint changed by Scott Moser: Work items changed: Work items: [smoser] support late_command: DONE [smoser] upstream project for fpi: DONE [smoser] debian packaging of fpi: DONE [smoser] fpi in ubuntu universe: DONE Work items for ubuntu-13.09: file feature freeze exception. bug 1218530.: DONE ubuntu main inclusion request processed. bug 1220434. (2): TODO - support grub installation / make install boot (2): TODO - support for copying from / inside overlayfs root (2): TODO + support grub installation / make install boot (2): DONE + support for copying from / inside overlayfs root (2): DONE [smoser] network setup (1): TODO -- fastpath installer work for 13.10 https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-fastpath-install -- 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-fastpath-install] fastpath installer work for 13.10
Blueprint changed by Scott Moser: Work items changed: Work items: [smoser] support late_command: DONE [smoser] upstream project for fpi: DONE [smoser] debian packaging of fpi: DONE [smoser] fpi in ubuntu universe: DONE Work items for ubuntu-13.09: file feature freeze exception. bug 1218530.: DONE ubuntu main inclusion request processed. bug 1220434. (2): TODO support grub installation / make install boot (2): DONE support for copying from / inside overlayfs root (2): DONE - [smoser] network setup (1): TODO + [smoser] network setup (1): DONE -- fastpath installer work for 13.10 https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-fastpath-install -- 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 1100843] Re: Live Migration Causes Performance Issues
I found that two patches need to be backported to solve this issue: ad0b5321f1f797274603ebbe20108b0750baee94 211ea74022f51164a7729030b28eec90b6c99a08 I've added the necessary bits into precise and tried a few tests: 1) Measure performance before and after savevm/loadvm. 2) Measure performance before and after a migrate to the same host. In both cases the performance measured by something like lmbench was the same as the previous run. A test build is available here: http://people.canonical.com/~arges/lp1100843/precise_v2/ ** Patch added: fix-lp1100843-precise.debdiff https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1100843/+attachment/3864309/+files/fix-lp1100843-precise.debdiff -- 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/1100843 Title: Live Migration Causes Performance Issues To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1100843/+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 1236373] [NEW] samba crashes when client disconnects
Public bug reported: [2013/10/06 02:16:07.148139, 0] param/loadparm.c:9114(process_usershare_file) process_usershare_file: stat of /var/lib/samba/usershares/shared failed. Permission denied [2013/10/06 02:16:07.368665, 0] param/loadparm.c:9114(process_usershare_file) process_usershare_file: stat of /var/lib/samba/usershares/shared failed. Permission denied [2013/10/06 02:16:07.780272, 0] param/loadparm.c:9114(process_usershare_file) process_usershare_file: stat of /var/lib/samba/usershares/shared failed. Permission denied [2013/10/06 04:32:44.450074, 0] param/loadparm.c:9114(process_usershare_file) process_usershare_file: stat of /var/lib/samba/usershares/shared failed. Permission denied [2013/10/06 04:32:44.493917, 0] param/loadparm.c:9114(process_usershare_file) process_usershare_file: stat of /var/lib/samba/usershares/shared failed. Permission denied [2013/10/06 14:11:11.432603, 0] param/loadparm.c:9114(process_usershare_file) process_usershare_file: stat of /var/lib/samba/usershares/shared failed. Permission denied [2013/10/06 21:02:25.242951, 0] param/loadparm.c:9114(process_usershare_file) process_usershare_file: stat of /var/lib/samba/usershares/shared failed. Permission denied [2013/10/06 21:02:29.953110, 0] param/loadparm.c:9114(process_usershare_file) process_usershare_file: stat of /var/lib/samba/usershares/shared failed. Permission denied [2013/10/06 21:02:30.185542, 0] param/loadparm.c:9114(process_usershare_file) process_usershare_file: stat of /var/lib/samba/usershares/shared failed. Permission denied [2013/10/06 21:02:30.502966, 0] param/loadparm.c:9114(process_usershare_file) process_usershare_file: stat of /var/lib/samba/usershares/shared failed. Permission denied [2013/10/06 21:02:30.745405, 0] param/loadparm.c:9114(process_usershare_file) process_usershare_file: stat of /var/lib/samba/usershares/shared failed. Permission denied [2013/10/07 01:49:15.331811, 0] param/loadparm.c:9114(process_usershare_file) process_usershare_file: stat of /var/lib/samba/usershares/shared failed. Permission denied [2013/10/07 03:30:04.592713, 0] lib/fault.c:47(fault_report) === [2013/10/07 03:30:04.592768, 0] lib/fault.c:48(fault_report) INTERNAL ERROR: Signal 11 in pid 21028 (3.6.3) Please read the Trouble-Shooting section of the Samba3-HOWTO [2013/10/07 03:30:04.592791, 0] lib/fault.c:50(fault_report) From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf [2013/10/07 03:30:04.637633, 0] lib/fault.c:51(fault_report) === [2013/10/07 03:30:04.637702, 0] lib/util.c:1117(smb_panic) PANIC (pid 21028): internal error [2013/10/07 03:30:05.255115, 0] lib/util.c:1221(log_stack_trace) BACKTRACE: 23 stack frames: #0 smbd(log_stack_trace+0x1a) [0x7f19c20dcb5a] #1 smbd(smb_panic+0x25) [0x7f19c20dcc35] #2 smbd(+0x409ef8) [0x7f19c20cdef8] #3 /lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7f19bec7d4a0] #4 /lib/x86_64-linux-gnu/libc.so.6(+0x162bf1) [0x7f19beda9bf1] #5 smbd(rep_strlcpy+0x2e) [0x7f19c20b2c7e] #6 smbd(connections_fetch_entry+0x74) [0x7f19c20e94d4] #7 smbd(yield_connection+0x3c) [0x7f19c1dcb10c] #8 smbd(close_cnum+0x93) [0x7f19c1e3fff3] #9 smbd(conn_close_all+0x94) [0x7f19c1dd1de4] #10 smbd(+0x686985) [0x7f19c234a985] #11 smbd(+0x686d2e) [0x7f19c234ad2e] #12 smbd(+0x1734c0) [0x7f19c1e374c0] #13 smbd(tevent_common_check_signal+0x10a) [0x7f19c20eee8a] #14 smbd(run_events_poll+0x25) [0x7f19c20ec5f5] #15 smbd(smbd_process+0x78c) [0x7f19c1e3ceec] #16 smbd(+0x68678f) [0x7f19c234a78f] #17 smbd(run_events_poll+0x34e) [0x7f19c20ec91e] #18 smbd(+0x428aba) [0x7f19c20ecaba] #19 smbd(_tevent_loop_once+0x90) [0x7f19c20ed640] #20 smbd(main+0xed0) [0x7f19c1dbb060] #21 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f19bec6876d] #22 smbd(+0xf7545) [0x7f19c1dbb545] [2013/10/07 03:30:05.255285, 0] lib/util.c:1122(smb_panic) smb_panic(): calling panic action [/usr/share/samba/panic-action 21028] [2013/10/07 03:30:05.311573, 0] lib/util.c:1130(smb_panic) smb_panic(): action returned status 0 [2013/10/07 03:30:05.381324, 0] lib/fault.c:372(dump_core) dumping core in /var/log/samba/cores/smbd [2013/10/07 14:15:58.956166, 0] param/loadparm.c:9114(process_usershare_file) process_usershare_file: stat of /var/lib/samba/usershares/shared failed. Permission denied [2013/10/07 14:31:46.618799, 0] param/loadparm.c:9114(process_usershare_file) process_usershare_file: stat of /var/lib/samba/usershares/shared failed. Permission denied [2013/10/07 14:31:46.618923, 0] param/loadparm.c:9114(process_usershare_file) process_usershare_file: stat of /var/lib/samba/usershares/shared failed. Permission denied [2013/10/07 17:15:54.458848, 0] lib/fault.c:47(fault_report) === [2013/10/07 17:15:54.458960,
[Bug 1100843] Re: Live Migration Causes Performance Issues
** Description changed: + SRU Justification + [Impact] + * Users of QEMU that save their memory states using savevm/loadvm or migrate experience worse performance after the migration/loadvm. To workaround these issues VMs must be completely rebooted. Optimally we should be able to restore a VM's memory state an expect no performance issue. + + [Test Case] + + * savevm/loadvm: +- Create a VM and install a test suite such as lmbench. +- Get numbers right after boot and record them. +- Open up the qemu monitor and type the following: + stop + savevm 0 + loadvm 0 + c +- Measure performance and record numbers. +- Compare if numbers are within margin of error. + * migrate: +- Create VM, install lmbench, get numbers. +- Open up qemu monitor and type the following: + stop + migrate exec:dd of=~/save.vm + quit +- Start a new VM using qemu but add the following argument: + -incoming exec:dd if=~/save.vm +- Run performance test and compare. + + If performance measured is similar then we pass the test case. + + [Regression Potential] + + * The fix is a backport of two upstream patches: + ad0b5321f1f797274603ebbe20108b0750baee94 + 211ea74022f51164a7729030b28eec90b6c99a08 + + On patch allows QEMU to use THP if its enabled. + The other patch changes logic to not memset pages to zero when loading memory for the vm (on an incoming migration). + + -- + I have 2 physical hosts running Ubuntu Precise. With 1.0+noroms- 0ubuntu14.7 and qemu-kvm 1.2.0+noroms-0ubuntu7 (source from quantal, built for Precise with pbuilder.) I attempted to build qemu-1.3.0 debs from source to test, but libvirt seems to have an issue with it that I haven't been able to track down yet. - I'm seeing a performance degradation after live migration on Precise, + I'm seeing a performance degradation after live migration on Precise, but not Lucid. These hosts are managed by libvirt (tested both 0.9.8-2ubuntu17 and 1.0.0-0ubuntu4) in conjunction with OpenNebula. I don't seem to have this problem with lucid guests (running a number of standard kernels, 3.2.5 mainline and backported linux- image-3.2.0-35-generic as well.) I first noticed this problem with phoronix doing compilation tests, and then tried lmbench where even simple calls experience performance degradation. I've attempted to post to the kvm mailing list, but so far the only suggestion was it may be related to transparent hugepages not being used after migration, but this didn't pan out. Someone else has a similar problem here - http://thread.gmane.org/gmane.comp.emulators.kvm.devel/100592 qemu command line example: /usr/bin/kvm -name one-2 -S -M pc-1.2 -cpu Westmere -enable-kvm -m 73728 -smp 16,sockets=2,cores=8,threads=1 -uuid f89e31a4-4945-c12c-6544-149ba0746c2f -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/one-2.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/one//datastores/0/2/disk.0,if=none,id=drive-virtio- disk0,format=raw,cache=none -device virtio-blk- pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio- disk0,bootindex=1 -drive file=/var/lib/one//datastores/0/2/disk.1,if=none,id=drive- ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive =drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=25 -device virtio-net- pci,netdev=hostnet0,id=net0,mac=02:00:0a:64:02:fe,bus=pci.0,addr=0x3 -vnc 0.0.0.0:2,password -vga cirrus -incoming tcp:0.0.0.0:49155 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 Disk backend is LVM running on SAN via FC connection (using symlink from /var/lib/one/datastores/0/2/disk.0 above) - ubuntu-12.04 - first boot == Simple syscall: 0.0527 microseconds Simple read: 0.1143 microseconds Simple write: 0.0953 microseconds Simple open/close: 1.0432 microseconds Using phoronix pts/compuational ImageMagick - 31.54s Linux Kernel 3.1 - 43.91s Mplayer - 30.49s PHP - 22.25s - ubuntu-12.04 - post live migration == Simple syscall: 0.0621 microseconds Simple read: 0.2485 microseconds Simple write: 0.2252 microseconds Simple open/close: 1.4626 microseconds Using phoronix pts/compilation ImageMagick - 43.29s Linux Kernel 3.1 - 76.67s Mplayer - 45.41s PHP - 29.1s - - I don't have phoronix results for 10.04 handy, but they were within 1% of each other... + I don't have phoronix results for 10.04 handy, but they were within 1% + of each other... ubuntu-10.04 - first boot == Simple syscall: 0.0524 microseconds Simple read: 0.1135
[Bug 1203068] Re: glance package tests disabled
** Changed in: glance (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to glance in Ubuntu. https://bugs.launchpad.net/bugs/1203068 Title: glance package tests disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glance/+bug/1203068/+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 1236380] [NEW] growroot fails for images on SD cards
Public bug reported: The growroot script doesn't correctly determine the root device name if the device name itself ends with a digit and partitions are named root devicep1, root devicep2 aso. For example, when using an SD card: $ ls -l /dev/mmcblk0* brw-rw 1 root disk 179, 0 Oct 7 16:04 /dev/mmcblk0 brw-rw 1 root disk 179, 1 Oct 7 16:04 /dev/mmcblk0p1 See https://bugzilla.redhat.com/show_bug.cgi?id=1009172. ** Affects: cloud-initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1236380 Title: growroot fails for images on SD cards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1236380/+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 1236373] Re: samba crashes when client disconnects
ah, sorry seems duplicate of #913809 -- 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/1236373 Title: samba crashes when client disconnects To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1236373/+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 1100843] Re: Live Migration Causes Performance Issues
** Description changed: SRU Justification - [Impact] - * Users of QEMU that save their memory states using savevm/loadvm or migrate experience worse performance after the migration/loadvm. To workaround these issues VMs must be completely rebooted. Optimally we should be able to restore a VM's memory state an expect no performance issue. + [Impact] + * Users of QEMU that save their memory states using savevm/loadvm or migrate experience worse performance after the migration/loadvm. To workaround these issues VMs must be completely rebooted. Optimally we should be able to restore a VM's memory state an expect no performance issue. [Test Case] - * savevm/loadvm: -- Create a VM and install a test suite such as lmbench. -- Get numbers right after boot and record them. -- Open up the qemu monitor and type the following: - stop - savevm 0 - loadvm 0 - c -- Measure performance and record numbers. -- Compare if numbers are within margin of error. - * migrate: -- Create VM, install lmbench, get numbers. -- Open up qemu monitor and type the following: - stop - migrate exec:dd of=~/save.vm - quit -- Start a new VM using qemu but add the following argument: - -incoming exec:dd if=~/save.vm -- Run performance test and compare. - - If performance measured is similar then we pass the test case. + * savevm/loadvm: + - Create a VM and install a test suite such as lmbench. + - Get numbers right after boot and record them. + - Open up the qemu monitor and type the following: + stop + savevm 0 + loadvm 0 + c + - Measure performance and record numbers. + - Compare if numbers are within margin of error. + * migrate: + - Create VM, install lmbench, get numbers. + - Open up qemu monitor and type the following: + stop + migrate exec:dd of=~/save.vm + quit + - Start a new VM using qemu but add the following argument: + -incoming exec:dd if=~/save.vm + - Run performance test and compare. + + If performance measured is similar then we pass the test case. [Regression Potential] - * The fix is a backport of two upstream patches: + * The fix is a backport of two upstream patches: ad0b5321f1f797274603ebbe20108b0750baee94 211ea74022f51164a7729030b28eec90b6c99a08 On patch allows QEMU to use THP if its enabled. The other patch changes logic to not memset pages to zero when loading memory for the vm (on an incoming migration). + * I've also run the qa-regression-testing test-qemu.py script and it passes all tests. -- I have 2 physical hosts running Ubuntu Precise. With 1.0+noroms- 0ubuntu14.7 and qemu-kvm 1.2.0+noroms-0ubuntu7 (source from quantal, built for Precise with pbuilder.) I attempted to build qemu-1.3.0 debs from source to test, but libvirt seems to have an issue with it that I haven't been able to track down yet. I'm seeing a performance degradation after live migration on Precise, but not Lucid. These hosts are managed by libvirt (tested both 0.9.8-2ubuntu17 and 1.0.0-0ubuntu4) in conjunction with OpenNebula. I don't seem to have this problem with lucid guests (running a number of standard kernels, 3.2.5 mainline and backported linux- image-3.2.0-35-generic as well.) I first noticed this problem with phoronix doing compilation tests, and then tried lmbench where even simple calls experience performance degradation. I've attempted to post to the kvm mailing list, but so far the only suggestion was it may be related to transparent hugepages not being used after migration, but this didn't pan out. Someone else has a similar problem here - http://thread.gmane.org/gmane.comp.emulators.kvm.devel/100592 qemu command line example: /usr/bin/kvm -name one-2 -S -M pc-1.2 -cpu Westmere -enable-kvm -m 73728 -smp 16,sockets=2,cores=8,threads=1 -uuid f89e31a4-4945-c12c-6544-149ba0746c2f -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/one-2.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/one//datastores/0/2/disk.0,if=none,id=drive-virtio- disk0,format=raw,cache=none -device virtio-blk- pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio- disk0,bootindex=1 -drive file=/var/lib/one//datastores/0/2/disk.1,if=none,id=drive- ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive =drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=25 -device virtio-net- pci,netdev=hostnet0,id=net0,mac=02:00:0a:64:02:fe,bus=pci.0,addr=0x3 -vnc 0.0.0.0:2,password -vga cirrus -incoming tcp:0.0.0.0:49155 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 Disk backend is LVM running on SAN via FC connection
[Bug 1236367] Re: [FFe] ceph 0.67.4 point release
I've build tested locally and installed the resulting packages on my single node test rig; restarted OK and basic rados bench and aio tests completed OK. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1236367 Title: [FFe] ceph 0.67.4 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1236367/+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 1236367] Re: [FFe] ceph 0.67.4 point release
** Changed in: ceph (Ubuntu Saucy) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1236367 Title: [FFe] ceph 0.67.4 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1236367/+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 1231459] Re: Inconsistency detected by ld.so: dl-close.c: 759: _dl_close: Assertion `map-l_init_called' failed!
Sam, I now get a segfault in gss-server: Reading symbols from /usr/bin/gss-server...(no debugging symbols found)...done. (gdb) set args -verbose host@localhost (gdb) run Starting program: /usr/bin/gss-server -verbose host@localhost [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Program received signal SIGSEGV, Segmentation fault. 0x0001f136 in ?? () (gdb) bt #0 0x0001f136 in ?? () #1 0x77bae8a1 in ?? () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #2 0x77baaaee in gss_add_cred () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #3 0x77bab187 in gss_acquire_cred () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #4 0x77bca624 in ?? () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #5 0x77bcadc8 in ?? () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #6 0x77baabc3 in gss_add_cred () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #7 0x77bab187 in gss_acquire_cred () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #8 0x0040182e in ?? () #9 0x777fe76d in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x00401ad1 in ?? () #11 0x7fffe6c8 in ?? () #12 0x001c in ?? () #13 0x0003 in ?? () #14 0x7fffe90a in ?? () #15 0x7fffe91e in ?? () #16 0x7fffe927 in ?? () #17 0x in ?? () (gdb) quit A debugging session is active. Inferior 1 [process 1550] will be killed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1231459 Title: Inconsistency detected by ld.so: dl-close.c: 759: _dl_close: Assertion `map-l_init_called' failed! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1231459/+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 1231459] Re: Inconsistency detected by ld.so: dl-close.c: 759: _dl_close: Assertion `map-l_init_called' failed!
Did you update moonshot-gs-eap?, There's a bad version the produce is that Stefan Paetow stefan.pae...@diamond.ac.uk wrote: Sam, I now get a segfault in gss-server: Reading symbols from /usr/bin/gss-server...(no debugging symbols found)...done. (gdb) set args -verbose host@localhost (gdb) run Starting program: /usr/bin/gss-server -verbose host@localhost [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Program received signal SIGSEGV, Segmentation fault. 0x0001f136 in ?? () (gdb) bt #0 0x0001f136 in ?? () #1 0x77bae8a1 in ?? () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #2 0x77baaaee in gss_add_cred () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #3 0x77bab187 in gss_acquire_cred () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #4 0x77bca624 in ?? () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #5 0x77bcadc8 in ?? () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #6 0x77baabc3 in gss_add_cred () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #7 0x77bab187 in gss_acquire_cred () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #8 0x0040182e in ?? () #9 0x777fe76d in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x00401ad1 in ?? () #11 0x7fffe6c8 in ?? () #12 0x001c in ?? () #13 0x0003 in ?? () #14 0x7fffe90a in ?? () #15 0x7fffe91e in ?? () #16 0x7fffe927 in ?? () #17 0x in ?? () (gdb) quit A debugging session is active. Inferior 1 [process 1550] will be killed. -- You received this bug notification because you are a member of Moonshot Drivers, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1231459 Title: Inconsistency detected by ld.so: dl-close.c: 759: _dl_close: Assertion `map-l_init_called' failed! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1231459/+subscriptions -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1231459 Title: Inconsistency detected by ld.so: dl-close.c: 759: _dl_close: Assertion `map-l_init_called' failed! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1231459/+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 1236361] Re: need new simple streams based maas-import-ephemerals
just for my own reference. I put this script together to clean up a maas instance where I was tracking daily. ** Attachment added: cleanup-ephemerals: clean up obsolete ephemeral images. https://bugs.launchpad.net/maas/+bug/1236361/+attachment/3864424/+files/cleanup-ephemerals -- 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/1236361 Title: need new simple streams based maas-import-ephemerals To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1236361/+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 1231459] Re: Inconsistency detected by ld.so: dl-close.c: 759: _dl_close: Assertion `map-l_init_called' failed!
Moonshot-gss-eap did get updated, yes. Stefan -Original Message- From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Sam Hartman Sent: 07 October 2013 16:19 To: Paetow, Stefan (DLSLtd,RAL,LSCI) Subject: Re: [Bug 1231459] Re: Inconsistency detected by ld.so: dl- close.c: 759: _dl_close: Assertion `map-l_init_called' failed! Did you update moonshot-gs-eap?, There's a bad version the produce is that Stefan Paetow stefan.pae...@diamond.ac.uk wrote: Sam, I now get a segfault in gss-server: Reading symbols from /usr/bin/gss-server...(no debugging symbols found)...done. (gdb) set args -verbose host@localhost (gdb) run Starting program: /usr/bin/gss-server -verbose host@localhost [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Program received signal SIGSEGV, Segmentation fault. 0x0001f136 in ?? () (gdb) bt #0 0x0001f136 in ?? () #1 0x77bae8a1 in ?? () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #2 0x77baaaee in gss_add_cred () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #3 0x77bab187 in gss_acquire_cred () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #4 0x77bca624 in ?? () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #5 0x77bcadc8 in ?? () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #6 0x77baabc3 in gss_add_cred () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #7 0x77bab187 in gss_acquire_cred () from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 #8 0x0040182e in ?? () #9 0x777fe76d in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x00401ad1 in ?? () #11 0x7fffe6c8 in ?? () #12 0x001c in ?? () #13 0x0003 in ?? () #14 0x7fffe90a in ?? () #15 0x7fffe91e in ?? () #16 0x7fffe927 in ?? () #17 0x in ?? () (gdb) quit A debugging session is active. Inferior 1 [process 1550] will be killed. -- You received this bug notification because you are a member of Moonshot Drivers, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1231459 Title: Inconsistency detected by ld.so: dl-close.c: 759: _dl_close: Assertion `map-l_init_called' failed! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1231459/+subscript i ons -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1231459 Title: Inconsistency detected by ld.so: dl-close.c: 759: _dl_close: Assertion `map-l_init_called' failed! Status in “krb5” package in Ubuntu: Confirmed Bug description: When I dynamically load a GSS mechanism that itself depends on the GSS library I get the following error on process exit: Inconsistency detected by ld.so: dl-close.c: 759: _dl_close: Assertion `map-l_init_called' failed! The Debian package apparently has a workaround for this (according to Sam), so... could you make this available to us Ubuntu 12 users too, please? The server runs Ubuntu 12.04.3 LTS. The KRB5 package version is 1.10+dfsg~beta1-2ubuntu0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1231459/+subscripti ons -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1231459 Title: Inconsistency detected by ld.so: dl-close.c: 759: _dl_close: Assertion `map-l_init_called' failed! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1231459/+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 1236433] [NEW] maas-cluster-celery did not survive upgrade
Public bug reported: This morning I upgraded maas. Then I went to deploy a node, and the node did not power on. I found that 'maas-cluster-celery' was 'stop/waiting'. I am able to 'sudo start maas-cluster-celery' now and it is functioning, but I do not expect for apt-upgrade to break the system. Further investigation shows the following in /var/log/maas/celery.log [2013-10-07 13:35:49,020: INFO/Beat] Scheduler: Sending due task provisioningserver.tasks.upload_dhcp_leases [2013-10-07 13:35:49,022: INFO/MainProcess] Got task from broker: provisioningserver.tasks.upload_dhcp_leases[76f1caad-3ba9-4cbe-8894-9ca96534a903] [2013-10-07 13:35:49,169: INFO/MainProcess] Task provisioningserver.tasks.upload_dhcp_leases[76f1caad-3ba9-4cbe-8894-9ca96534a903] succeeded in 0.141157150269s: None [2013-10-07 13:36:06,647: INFO/Beat] Scheduler: Sending due task provisioningserver.tasks.report_boot_images [2013-10-07 13:36:06,649: INFO/MainProcess] Got task from broker: provisioningserver.tasks.report_boot_images[fa862682-3ffb-44bf-9733-268701d73e9a] [2013-10-07 13:36:06,826: INFO/MainProcess] Task provisioningserver.tasks.report_boot_images[fa862682-3ffb-44bf-9733-268701d73e9a] succeeded in 0.128345966339s: None [2013-10-07 13:36:10,644: WARNING/MainProcess] celeryd: Warm shutdown (MainProcess) [2013-10-07 13:36:10,644: INFO/MainProcess] Celerybeat: Shutting down... [2013-10-07 13:36:10,759: INFO/MainProcess] process shutting down The time stamp there correlates to /var/log/apt/history.log Start-Date: 2013-10-07 13:36:09 Commandline: apt-get dist-upgrade Install: libsasl2-modules-db:amd64 (2.1.25.dfsg1-17, automatic), python-markdown:amd64 (2.3.1-1, automatic) Upgrade: python-maas-provisioningserver:amd64 (1.4+bzr1656+dfsg-0ubuntu1, 1.4+bzr1656+dfsg-0ubuntu2), libboost-thread1.53.0:amd64 (1.53.0-6+exp3ubuntu6, 1.53.0-6+exp3ubuntu7), juju-core:amd64 (1.15.0-0~1903~ubuntu13.10.1, 1.15.1-0~1954~ubuntu13.10.1), maas-common:amd64 (1.4+bzr1656+dfsg-0ubuntu1, 1.4+bzr1656+dfsg-0ubuntu2), maas-region-controller:amd64 (1.4+bzr1656+dfsg-0ubuntu1, 1.4+bzr1656+dfsg-0ubuntu2), maas-dns:amd64 (1.4+bzr1656+dfsg-0ubuntu1, 1.4+bzr1656+dfsg-0ubuntu2), libboost-system1.53.0:amd64 (1.53.0-6+exp3ubuntu6, 1.53.0-6+exp3ubuntu7), charm-tools:amd64 (1.0.0-0ubuntu1, 1.0.0-0ubuntu2), maas-cli:amd64 (1.4+bzr1656+dfsg-0ubuntu1, 1.4+bzr1656+dfsg-0ubuntu2), libgmp10:amd64 (5.1.2+dfsg-2, 5.1.2+dfsg-2ubuntu1), upstart:amd64 (1.10-0ubuntu3, 1.10-0ubuntu6), maas-dhcp:amd64 (1.4+bzr1656+dfsg-0ubuntu1, 1.4+bzr1656+dfsg-0ubuntu2), maas-cluster-controller:amd64 (1.4+bzr1656+dfsg-0ubuntu1, 1.4+bzr1656+dfsg-0ubuntu2), libboost-iostreams1.53.0:amd64 (1.53.0-6+exp3ubuntu6, 1.53.0-6+exp3ubuntu7), python-django-maas:amd64 (1.4+bzr1656+dfsg-0ubuntu1, 1.4+bzr1656+dfsg-0ubuntu2), libsasl2-modules:amd64 (2.1.25.dfsg1-14, 2.1.25.dfsg1-17), libsasl2-2:amd64 (2.1.25.dfsg1-14, 2.1.25.dfsg1-17), maas:amd64 (1.4+bzr1656+dfsg-0ubuntu1, 1.4+bzr1656+dfsg-0ubuntu2), python-maas-client:amd64 (1.4+bzr1656+dfsg-0ubuntu1, 1.4+bzr1656+dfsg-0ubuntu2) End-Date: 2013-10-07 13:36:48 So I'm assuming this was shut down during upgrade and did not get restarted. /var/log/upstart/maas-cluster-celery.log shows: Traceback (most recent call last): File /usr/lib/python2.7/runpy.py, line 162, in _run_module_as_main __main__, fname, loader, pkg_name) File /usr/lib/python2.7/runpy.py, line 72, in _run_code exec code in run_globals File /usr/lib/python2.7/dist-packages/provisioningserver/__main__.py, line 39, in module main() File /usr/lib/python2.7/dist-packages/provisioningserver/utils.py, line 431, in __call__ self.execute(argv) File /usr/lib/python2.7/dist-packages/provisioningserver/utils.py, line 426, in execute args.handler.run(args) File /usr/lib/python2.7/dist-packages/provisioningserver/start_cluster_controller.py, line 178, in run connection_details = register(args.server_url) File /usr/lib/python2.7/dist-packages/provisioningserver/start_cluster_controller.py, line 90, in register interfaces=interfaces, uuid=cluster_uuid) File /usr/lib/python2.7/dist-packages/apiclient/maas_client.py, line 216, in post url, method=POST, headers=headers, data=body) File /usr/lib/python2.7/dist-packages/apiclient/maas_client.py, line 99, in dispatch_query res = urllib2.urlopen(req) File /usr/lib/python2.7/urllib2.py, line 127, in urlopen return _opener.open(url, data, timeout) File /usr/lib/python2.7/urllib2.py, line 404, in open response = self._open(req, data) File /usr/lib/python2.7/urllib2.py, line 422, in _open '_open', req) File /usr/lib/python2.7/urllib2.py, line 382, in _call_chain result = func(*args) File /usr/lib/python2.7/urllib2.py, line 1214, in http_open return self.do_open(httplib.HTTPConnection, req) File /usr/lib/python2.7/urllib2.py, line 1187, in do_open r = h.getresponse(buffering=True) File /usr/lib/python2.7/httplib.py, line 1045, in getresponse
[Bug 1236445] [NEW] smartos hostname assignment fails due to whitespace
You have been subscribed to a public bug: SmartOS uses whitespace when reporting the hostname via the meta-data source. As a result, the hostname assignment fails. Simple fix: === modified file 'cloudinit/sources/DataSourceSmartOS.py' --- cloudinit/sources/DataSourceSmartOS.py 2013-10-05 01:05:21 + +++ cloudinit/sources/DataSourceSmartOS.py 2013-10-07 16:12:19 + @@ -145,6 +145,7 @@ if not md['local-hostname']: md['local-hostname'] = system_uuid +md['local-hostname'] = md['local-hostname'].strip() ud = None if md['user-data']: ** Affects: cloud-init (Ubuntu) Importance: Medium Assignee: Ben Howard (utlemming) Status: Confirmed -- smartos hostname assignment fails due to whitespace https://bugs.launchpad.net/bugs/1236445 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init 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 1236439] [NEW] switch to use not fully qualified hostnames breaks upgrades of l3-agent
Public bug reported: Commit https://github.com/openstack/neutron/commit/140029ebd006c116ee684890dd70e13b7fc478ec switch to using socket.gethostname() for the name of neutron agents; this has the unfortunate side effect with the l3-agent that all router services are no longer scheduled on an active agent, resulting in floating ip and access outages. Looks like this will effect upgrades from grizzly-havana as well: ubuntu@churel:/etc/maas$ quantum agent-list +--++--+---++ | id | agent_type | host | alive | admin_state_up | +--++--+---++ | 02ad1175-209c-4125-889a-e390a15ecd50 | Open vSwitch agent | caipora.1ss.qa.lexington | xxx | True | | 191d4757-05f6-4170-a78d-d6a3c1b9265e | Open vSwitch agent | canaima | :-) | True | | 306cbfbb-8879-4d64-ac26-db007f9113a9 | DHCP agent | cofgod.1ss.qa.lexington | xxx | True | | 32081821-1e94-4274-993b-b0bf2714e5ac | Open vSwitch agent | ciguapa.1ss.qa.lexington | xxx | True | | 5697a23a-712e-4de3-a218-2a6c177bf555 | Open vSwitch agent | chakora | :-) | True | | 5ea5e207-1da0-47e3-9a7e-984589b11300 | Open vSwitch agent | cuegle.1ss.qa.lexington | xxx | True | | 71e31354-76e7-4640-9a5b-368678bc22d0 | Open vSwitch agent | canaima.1ss.qa.lexington | xxx | True | | 7267e3d2-d9bf-4e57-8d19-803aab636f36 | Open vSwitch agent | chakora.1ss.qa.lexington | xxx | True | | 75ff2563-f5a5-4df3-aa19-fe8310146c10 | Open vSwitch agent | cuegle | :-) | True | | 875de52e-d6c3-4e82-8cbd-269831ff00bc | Open vSwitch agent | cofgod | :-) | True | | 9afaf6f2-2756-4863-b5d0-7faba502e878 | L3 agent | cofgod | :-) | True | | a81ac370-a318-42e4-9279-eef2b6141644 | Open vSwitch agent | cofgod.1ss.qa.lexington | xxx | True | | d6e6332e-822a-438e-8613-16013da825e0 | L3 agent | cofgod.1ss.qa.lexington | xxx | True | | d9712755-03b3-4326-99c1-3bf66c878dc6 | Open vSwitch agent | ciguapa | :-) | True | | dadf284c-ac8f-4dc1-9ba4-73182e5f1911 | DHCP agent | cofgod | :-) | True | | ed07ff1a-dcca-4bbd-b026-1296bb90f89b | Open vSwitch agent | caipora | :-) | True | +--++--+---++ ** Affects: cloud-archive Importance: Undecided Status: New ** Affects: neutron Importance: Undecided Status: New ** Affects: neutron (Ubuntu) Importance: High Status: New ** Affects: neutron (Ubuntu Saucy) Importance: High Status: New ** Also affects: neutron (Ubuntu) Importance: Undecided Status: New ** Also affects: neutron (Ubuntu Saucy) Importance: Undecided Status: New ** Also affects: cloud-archive Importance: Undecided Status: New ** Changed in: neutron (Ubuntu Saucy) Importance: Undecided = High ** Description changed: Commit https://github.com/openstack/neutron/commit/140029ebd006c116ee684890dd70e13b7fc478ec switch to using socket.gethostname() for the name of neutron agents; this has the unfortunate side effect with the l3-agent that all router - services are not longer scheduled on an active agent, resulting in + services are no longer scheduled on an active agent, resulting in floating ip and access outages. Looks like this will effect upgrades from grizzly-havana as well: ubuntu@churel:/etc/maas$ quantum agent-list +--++--+---++ | id | agent_type | host | alive | admin_state_up | +--++--+---++ | 02ad1175-209c-4125-889a-e390a15ecd50 | Open vSwitch agent | caipora.1ss.qa.lexington | xxx | True | | 191d4757-05f6-4170-a78d-d6a3c1b9265e | Open vSwitch agent | canaima | :-) | True | | 306cbfbb-8879-4d64-ac26-db007f9113a9 | DHCP agent | cofgod.1ss.qa.lexington | xxx | True | | 32081821-1e94-4274-993b-b0bf2714e5ac | Open vSwitch agent | ciguapa.1ss.qa.lexington | xxx | True | | 5697a23a-712e-4de3-a218-2a6c177bf555 | Open vSwitch agent | chakora | :-) | True | | 5ea5e207-1da0-47e3-9a7e-984589b11300 | Open vSwitch agent | cuegle.1ss.qa.lexington | xxx | True | |
[Bug 1235372] Re: managesieve skipping of CRLF at end of AUTHENTICATE command
Thank you for taking the time to report this bug and helping to make Ubuntu better. I can see that this bug is not yet fixed in the current version of dovecot in Ubuntu (1:2.1.7-7ubuntu2) but appears to be fixed in Debian (1:2.1.17-2). So Ubuntu should pick up the fix in the next merge from Debian, which I expect will happen in the T series. If you'd like this issue fixed in existing stable releases, then the policy, procedure and rationale is described here: https://wiki.ubuntu.com/StableReleaseUpdates Based on that policy, to update dovecot in a stable release to fix this bug I think we'll need: 1) An understanding of the bug and its impact (rather than just the patch) to ensure that we don't inadvertently introduce any regressions. 2) This issue fixed in the development release (a merge as expected to happen anyway will do; but we're very close to freeze for Saucy now, so waiting for T to open after Saucy's release is probably more realistic). ** Changed in: dovecot (Ubuntu) Status: New = Triaged ** Changed in: dovecot (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/1235372 Title: managesieve skipping of CRLF at end of AUTHENTICATE command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1235372/+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 1236445] [NEW] smartos hostname assignment fails due to whitespace
Public bug reported: SmartOS uses whitespace when reporting the hostname via the meta-data source. As a result, the hostname assignment fails. Simple fix: === modified file 'cloudinit/sources/DataSourceSmartOS.py' --- cloudinit/sources/DataSourceSmartOS.py 2013-10-05 01:05:21 + +++ cloudinit/sources/DataSourceSmartOS.py 2013-10-07 16:12:19 + @@ -145,6 +145,7 @@ if not md['local-hostname']: md['local-hostname'] = system_uuid +md['local-hostname'] = md['local-hostname'].strip() ud = None if md['user-data']: ** Affects: cloud-init (Ubuntu) Importance: Medium Assignee: Ben Howard (utlemming) Status: Confirmed ** Package changed: ubuntu = cloud-init (Ubuntu) ** Branch linked: lp:~utlemming/cloud-init/lp-1236445-smartos-hostname ** Description changed: SmartOS uses whitespace when reporting the hostname via the meta-data source. As a result, the hostname assignment fails. Simple fix: === modified file 'cloudinit/sources/DataSourceSmartOS.py' --- cloudinit/sources/DataSourceSmartOS.py2013-10-05 01:05:21 + +++ cloudinit/sources/DataSourceSmartOS.py2013-10-07 16:12:19 + @@ -145,6 +145,7 @@ - - if not md['local-hostname']: - md['local-hostname'] = system_uuid + + if not md['local-hostname']: + md['local-hostname'] = system_uuid +md['local-hostname'] = md['local-hostname'].strip() - - ud = None - if md['user-data']: + + ud = None + if md['user-data']: ** Description changed: SmartOS uses whitespace when reporting the hostname via the meta-data source. As a result, the hostname assignment fails. Simple fix: === modified file 'cloudinit/sources/DataSourceSmartOS.py' --- cloudinit/sources/DataSourceSmartOS.py2013-10-05 01:05:21 + +++ cloudinit/sources/DataSourceSmartOS.py2013-10-07 16:12:19 + @@ -145,6 +145,7 @@ if not md['local-hostname']: md['local-hostname'] = system_uuid - +md['local-hostname'] = md['local-hostname'].strip() + +md['local-hostname'] = md['local-hostname'].strip() ud = None if md['user-data']: -- 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/1236445 Title: smartos hostname assignment fails due to whitespace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1236445/+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 1236445] Re: smartos hostname assignment fails due to whitespace
** Branch linked: lp:cloud-init -- 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/1236445 Title: smartos hostname assignment fails due to whitespace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1236445/+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 1235231] Re: ci-info: eth0 not reliable in latest saucy images
On Mon, Oct 07, 2013 at 01:05:44PM -, Scott Moser wrote:
Steve thinks its not entirely unreasonable to just disable plymouth via
.override files in cloud-images. I think he would suggest that that be
done at the package level and be handled by cloud-init. That wasn't
clear to me though.
Yes, that is my recommendation.
From a follow-on discussion with Ben:
04-10-2013 12:03:12 slangasek so I think adding 'manual' .overrides
for all of /etc/init/plymouth{,-log,-splash,-upstart-bridge}.conf would
DTRT
--
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/1235231
Title:
plymouth loses output to /dev/console (such as ci-info: messages)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1235231/+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 1236462] [NEW] [SRU] update openstack packages to 2013.2 release tarballs
You have been subscribed to a public bug: Openstack 2013.2 will release on October 17, 2013. Ubuntu 13.04 will release on October 17, 2013. That means that we're basically guaranteed to not have 2013.2 official release tarballs in Ubuntu. This bug is a place holder for all the openstack packages that will need updating to the official release tarballs. ** Affects: ceilometer (Ubuntu) Importance: Undecided Status: New -- [SRU] update openstack packages to 2013.2 release tarballs https://bugs.launchpad.net/bugs/1236462 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceilometer 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 1233698] Re: ephemeral disk formating fails on Windows Azure
This bug was fixed in the package cloud-init - 0.7.3~bzr884-0ubuntu1 --- cloud-init (0.7.3~bzr884-0ubuntu1) saucy; urgency=low * New upstream snapshot. * allow disabling of growpart via file /etc/growroot-disabled (LP: #1234331) * add default user to sudo group (LP: #1228228) * fix disk creation on azure (LP: #1233698) * DatasourceSmartOS: allow availabiltity-zone to be fed from the datasource via 'region' (which allows 'mirrors' and other things to make use of it). -- Scott Moser smo...@ubuntu.com Fri, 04 Oct 2013 21:08:07 -0400 ** Changed in: cloud-init (Ubuntu) Status: New = Fix Released -- 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/1233698 Title: ephemeral disk formating fails on Windows Azure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1233698/+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 1234331] Re: cloud-init should respect /etc/growroot-disabled
This bug was fixed in the package cloud-init - 0.7.3~bzr884-0ubuntu1 --- cloud-init (0.7.3~bzr884-0ubuntu1) saucy; urgency=low * New upstream snapshot. * allow disabling of growpart via file /etc/growroot-disabled (LP: #1234331) * add default user to sudo group (LP: #1228228) * fix disk creation on azure (LP: #1233698) * DatasourceSmartOS: allow availabiltity-zone to be fed from the datasource via 'region' (which allows 'mirrors' and other things to make use of it). -- Scott Moser smo...@ubuntu.com Fri, 04 Oct 2013 21:08:07 -0400 ** Changed in: cloud-init (Ubuntu) Status: New = Fix Released -- 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/1234331 Title: cloud-init should respect /etc/growroot-disabled To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1234331/+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 1228228] Re: ubuntu is not added to sudo group
This bug was fixed in the package cloud-init - 0.7.3~bzr884-0ubuntu1 --- cloud-init (0.7.3~bzr884-0ubuntu1) saucy; urgency=low * New upstream snapshot. * allow disabling of growpart via file /etc/growroot-disabled (LP: #1234331) * add default user to sudo group (LP: #1228228) * fix disk creation on azure (LP: #1233698) * DatasourceSmartOS: allow availabiltity-zone to be fed from the datasource via 'region' (which allows 'mirrors' and other things to make use of it). -- Scott Moser smo...@ubuntu.com Fri, 04 Oct 2013 21:08:07 -0400 ** Changed in: cloud-init (Ubuntu Saucy) Status: Triaged = Fix Released -- 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/1228228 Title: ubuntu is not added to sudo group To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1228228/+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 1236462] [NEW] [SRU] update openstack packages to 2013.2 release tarballs
Public bug reported: Openstack 2013.2 will release on October 17, 2013. Ubuntu 13.04 will release on October 17, 2013. That means that we're basically guaranteed to not have 2013.2 official release tarballs in Ubuntu. This bug is a place holder for all the openstack packages that will need updating to the official release tarballs. ** Affects: ceilometer (Ubuntu) Importance: Medium Status: Confirmed ** Affects: cinder (Ubuntu) Importance: Medium Status: Confirmed ** Affects: glance (Ubuntu) Importance: Medium Status: Confirmed ** Affects: horizon (Ubuntu) Importance: Medium Status: Confirmed ** Affects: keystone (Ubuntu) Importance: Medium Status: Confirmed ** Affects: nova (Ubuntu) Importance: Medium Status: Confirmed ** Affects: oslo-config (Ubuntu) Importance: Medium Status: Confirmed ** Affects: python-django-openstack-auth (Ubuntu) Importance: Medium Status: Confirmed ** Affects: quantum (Ubuntu) Importance: Medium Status: Confirmed ** Affects: swift (Ubuntu) Importance: Medium Status: Confirmed ** Summary changed: - [SRU] update openstack packages to released versions + [SRU] update openstack packages to 2013.2 release tarballs ** Package changed: ubuntu = ceilometer (Ubuntu) ** Also affects: cinder (Ubuntu) Importance: Undecided Status: New ** Also affects: glance (Ubuntu) Importance: Undecided Status: New ** Also affects: horizon (Ubuntu) Importance: Undecided Status: New ** Also affects: keystone (Ubuntu) Importance: Undecided Status: New ** Also affects: nova (Ubuntu) Importance: Undecided Status: New ** Also affects: oslo-config (Ubuntu) Importance: Undecided Status: New ** Also affects: python-django-openstack-auth (Ubuntu) Importance: Undecided Status: New ** Also affects: quantum (Ubuntu) Importance: Undecided Status: New ** Also affects: swift (Ubuntu) Importance: Undecided Status: New ** Changed in: ceilometer (Ubuntu) Importance: Undecided = Medium ** Changed in: ceilometer (Ubuntu) Status: New = Confirmed ** Changed in: cinder (Ubuntu) Importance: Undecided = Medium ** Changed in: cinder (Ubuntu) Status: New = Confirmed ** Changed in: glance (Ubuntu) Importance: Undecided = Medium ** Changed in: glance (Ubuntu) Status: New = Confirmed ** Changed in: horizon (Ubuntu) Importance: Undecided = Medium ** Changed in: horizon (Ubuntu) Status: New = Confirmed ** Changed in: keystone (Ubuntu) Importance: Undecided = Medium ** Changed in: keystone (Ubuntu) Status: New = Confirmed ** Changed in: nova (Ubuntu) Importance: Undecided = Medium ** Changed in: nova (Ubuntu) Status: New = Confirmed ** Changed in: oslo-config (Ubuntu) Importance: Undecided = Medium ** Changed in: oslo-config (Ubuntu) Status: New = Confirmed ** Changed in: python-django-openstack-auth (Ubuntu) Importance: Undecided = Medium ** Changed in: python-django-openstack-auth (Ubuntu) Status: New = Confirmed ** Changed in: quantum (Ubuntu) Importance: Undecided = Medium ** Changed in: quantum (Ubuntu) Status: New = Confirmed ** Changed in: swift (Ubuntu) Importance: Undecided = Medium ** Changed in: swift (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1236462 Title: [SRU] update openstack packages to 2013.2 release tarballs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1236462/+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 1231459] Re: Inconsistency detected by ld.so: dl-close.c: 759: _dl_close: Assertion `map-l_init_called' failed!
OK, that's probably the cause of the segfault. I've deleted the broken packages from our debian and ubuntu archives. Unfortunately getting fixed packages to reappear is a bit annoying at the moment. The packages in http://repository.project-moonshot.org/debian-moonshot/pool/main/m/moonshot-gss-eap now sholud be OK. In particular the deb from April. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1231459 Title: Inconsistency detected by ld.so: dl-close.c: 759: _dl_close: Assertion `map-l_init_called' failed! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1231459/+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 1236490] [NEW] Container has no networking
Public bug reported: I try to start lxc, things go wrong, I eventually get a console login, but networking is notworking. $ sudo lxc-start -n cwdev 4init: ureadahead main process (6) terminated with status 5 4init: udev-fallback-graphics main process (53) terminated with status 1 4init: console-setup main process (61) terminated with status 1 4init: procps (virtual-filesystems) main process (64) terminated with status 255 4init: setvtrgb main process (72) terminated with status 1 30udevd[87]: starting version 175 TERM environment variable not set. 4init: plymouth-upstart-bridge main process (139) terminated with status 1 long pause here Ubuntu 12.04.2 LTS cwdev console cwdev login: 4init: setvtrgb main process (288) terminated with status 1 abentley Password: Last login: Mon Oct 7 13:36:31 EDT 2013 on lxc/console Welcome to Ubuntu 12.04.2 LTS (GNU/Linux 3.11.0-11-generic x86_64) * Documentation: https://help.ubuntu.com/ abentley@cwdev:~$ ping 8.8.8.8 connect: Network is unreachable abentley@cwdev:~$ abentley@cwdev:~$ ifconfig eth0 Link encap:Ethernet HWaddr 00:16:3e:37:0e:f6 inet6 addr: fe80::216:3eff:fe37:ef6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:78 errors:0 dropped:0 overruns:0 frame:0 TX packets:32 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:11923 (11.9 KB) TX bytes:6921 (6.9 KB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:27 errors:0 dropped:0 overruns:0 frame:0 TX packets:27 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2088 (2.0 KB) TX bytes:2088 (2.0 KB) This container is for Precise, and was originally created under Raring. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lxc 1.0.0~alpha1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Mon Oct 7 13:34:57 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2010-12-09 (1032 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MarkForUpload: True SourcePackage: lxc UpgradeStatus: Upgraded to saucy on 2013-09-26 (10 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor 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/1236490 Title: Container has no networking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1236490/+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 1236265] Re: vmghfs not being build
There were issues. Working on it. -- 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/1236265 Title: vmghfs not being build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1236265/+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 1236171] Re: package postfix 2.9.6-1~12.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1236171 Title: package postfix 2.9.6-1~12.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1236171/+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 1236171] Re: package postfix 2.9.6-1~12.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1236171 Title: package postfix 2.9.6-1~12.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1236171/+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 1236490] Re: Container has no networking
Stephane Graber explains: bug 1236490 very much looks like isc-dhcp-* is out of date in your container a kernel change in 3.10 caused veth devices to do udp offloading which wasn't supported by the isc-dhcp we shipped in precise, quantal and raring so I SRUed the fix a couple months back to all supported releases. If that's the problem you're having, just chroot into /var/lib/lxc/container/rootfs and do an apt-get update apt-get install isc-dhcp-common isc-dhcp-client if that updates isc-dhcp, then there's a good chance the next boot of that container will work you'll need to do that to all affected containers and if you have an old container cache in /var/cache/lxc then also update that one or flush it so it gets re-created on the next lxc-create -- 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/1236490 Title: Container has no networking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1236490/+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 1158708] [NEW] Services start/stop multiple times during boot
You have been subscribed to a public bug: I'm running a fresh installation of Ubuntu 12.04.2 LTS with all updates from security/updates applied. While everything works as expected after boot, I see that several services are started and stopped multiple times. After adding --verbose to the kernel command line in grub, I see the following in /var/log/dmesg (grep on ssh, but other services look similar): [ 15.448785] init: ssh goal changed from stop to start [ 15.448977] init: ssh state changed from waiting to starting [ 15.722522] init: ssh state changed from starting to pre-start [ 15.740479] init: ssh pre-start process (412) [ 15.892560] init: ssh pre-start process (412) exited normally [ 15.892697] init: ssh state changed from pre-start to spawned [ 15.900573] init: ssh main process (427) [ 15.900877] init: ssh state changed from spawned to post-start [ 15.912513] init: ssh state changed from post-start to running [ 18.292483] init: ssh goal changed from start to stop [ 18.292723] init: ssh state changed from running to pre-stop [ 18.292826] init: ssh state changed from pre-stop to stopping [ 18.293129] init: ssh state changed from stopping to killed [ 18.293236] init: Sending TERM signal to ssh main process (427) [ 18.296505] init: ssh main process (427) exited normally [ 18.296683] init: ssh state changed from killed to post-stop [ 18.297359] init: ssh state changed from post-stop to waiting [ 18.344245] init: ssh goal changed from stop to start [ 18.344378] init: ssh state changed from waiting to starting [ 18.344801] init: ssh state changed from starting to pre-start [ 18.356479] init: ssh pre-start process (593) [ 18.414658] init: ssh pre-start process (593) exited normally [ 18.415023] init: ssh state changed from pre-start to spawned [ 18.424710] init: ssh main process (596) [ 18.424886] init: ssh state changed from spawned to post-start [ 18.429089] init: ssh state changed from post-start to running You can see that SSH is started 4 times. This seems unnecessary and looks like a bug to me. I see this behaviour on other Ubuntu 12.04 systems as well. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: upstart 1.5-0ubuntu7.2 ProcVersionSignature: Ubuntu 3.5.0-26.42~precise1-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Fri Mar 22 11:20:16 2013 InstallationMedia: Ubuntu-Server 12.04.2 LTS Precise Pangolin - Release amd64 (20130214) MarkForUpload: True ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- Services start/stop multiple times during boot https://bugs.launchpad.net/bugs/1158708 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh 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 1236531] [NEW] support running apt with eatmydata
Public bug reported: During instance boot, cloud-init installs packages (if instructed by the user). During instance boot, there is no state of the system that the user cares about. I'd like to use eatmydata for apt-get install at that point, as it is dramatically faster than apt-get even with --force-unsafe-io. From an ubuntu perspective, this change would mean: a.) depending on eatmydata b.) MIR for eatmydata c.) fixing eatmydata's relationship with sysvinit scripts. The thing to fix there is that if you 'eatmydata apt-get install some-service' and some-service starts a daemon, the daemon will inherit the LD_PRELOAD which is most likely not desired. ** Affects: cloud-init Importance: Undecided Status: Confirmed ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: libeatmydata (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Milestone: None = ubuntu-14.02 ** Changed in: cloud-init (Ubuntu) Status: New = Confirmed ** Changed in: cloud-init Status: New = Confirmed ** Also affects: libeatmydata (Ubuntu) Importance: Undecided Status: New -- 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/1236531 Title: support running apt with eatmydata To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1236531/+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 1158708] Re: Services start/stop multiple times during boot
Ok, that explains. The openssh-server package ships /etc/network/if- up.d/openssh-server, which exists precisely to restart the service when a network interface comes up. And NetworkManager does not use the normal ADDRFAM==inet[6] convention, so this isn't triggered on the desktop. [ 10.978364] init: Connection from private client [ 10.982980] init: ssh goal changed from start to stop I don't know why this ssh service restart is needed/wanted when a network interface comes up. It may be vestigial. Reassigning to the openssh package. Whatever the right answer is here, the behavior should probably be consistent between NetworkManager and !NetworkManager uses. ** Package changed: upstart (Ubuntu) = openssh (Ubuntu) ** Changed in: openssh (Ubuntu) Status: Incomplete = New -- 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/1158708 Title: Services start/stop multiple times during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1158708/+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 1236544] [NEW] canot access static images over http with apache 2.2 (precise)
Public bug reported: when running saucy maas on precise (via cloud-archive), access to the static images is denied. [Mon Oct 07 18:50:06 2013] [crit] [client 127.0.0.1] configuration error: couldn't perform authentication. AuthType not set!: /MAAS/static/images/amd64/generic/precise/xinstall/root.tar.gz adam_g dropping 'Require all granted' from maas-cluster-http.conf helps https://wiki.debian.org/Apache/PackagingFor24 suggests that we shoudl be able to use version specific content in a single config module with 'ifversion'. Just for reference, trunk change at revno 1549 changed this in contrib /maas-cluster-http.conf ** Affects: cloud-archive Importance: Critical Status: Confirmed ** Affects: maas Importance: Critical Assignee: Andres Rodriguez (andreserl) Status: Confirmed ** Affects: maas (Ubuntu) Importance: Medium Assignee: Andres Rodriguez (andreserl) Status: Confirmed ** Changed in: maas (Ubuntu) Status: New = Confirmed ** Also affects: maas Importance: Undecided Status: New ** Also affects: cloud-archive Importance: Undecided Status: New ** Changed in: cloud-archive Status: New = Confirmed ** Changed in: maas Status: New = Confirmed ** Changed in: cloud-archive Importance: Undecided = Critical ** Changed in: maas (Ubuntu) Importance: Undecided = Medium ** Changed in: maas Importance: Undecided = Critical ** Description changed: when running saucy maas on precise (via cloud-archive), access to the static images is denied. - - [Mon Oct 07 18:50:06 2013] [crit] [client 127.0.0.1] configuration error: couldn't perform authentication. AuthType not set!: /MAAS/static/images/amd64/generic/precise/xinstall/root.tar.gz + [Mon Oct 07 18:50:06 2013] [crit] [client 127.0.0.1] configuration + error: couldn't perform authentication. AuthType not set!: + /MAAS/static/images/amd64/generic/precise/xinstall/root.tar.gz adam_g dropping 'Require all granted' from maas-cluster-http.conf helps https://wiki.debian.org/Apache/PackagingFor24 suggests that we shoudl be able to use version specific content in a single config module with 'ifversion'. + + Just for reference, trunk change at revno 1549 changed this in contrib + /maas-cluster-http.conf -- 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/1236544 Title: canot access static images over http with apache 2.2 (precise) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1236544/+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 1236544] Re: canot access static images over http with apache 2.2 (precise)
** Changed in: maas Assignee: (unassigned) = Andres Rodriguez (andreserl) ** Changed in: maas (Ubuntu) Assignee: (unassigned) = Andres Rodriguez (andreserl) -- 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/1236544 Title: canot access static images over http with apache 2.2 (precise) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1236544/+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 1236544] Re: canot access static images over http with apache 2.2 (precise)
** Branch linked: lp:~andreserl/maas/lp1236544 -- 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/1236544 Title: canot access static images over http with apache 2.2 (precise) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1236544/+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 1236544] Re: canot access static images over http with apache 2.2 (precise)
** Branch linked: lp:~andreserl/maas/packaging_lp1236544 -- 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/1236544 Title: canot access static images over http with apache 2.2 (precise) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1236544/+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 1236462] Re: [SRU] update openstack packages to 2013.2 release tarballs
We dont have a MRE for ceilometer or heat. ** No longer affects: oslo-config (Ubuntu) ** No longer affects: python-django-openstack-auth (Ubuntu) ** Also affects: heat (Ubuntu) Importance: Undecided Status: New ** Changed in: heat (Ubuntu) Status: New = Confirmed ** Changed in: heat (Ubuntu) Importance: Undecided = Medium -- 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/1236462 Title: [SRU] update openstack packages to 2013.2 release tarballs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1236462/+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 1100843] Re: Live Migration Causes Performance Issues
** Description changed: SRU Justification [Impact] * Users of QEMU that save their memory states using savevm/loadvm or migrate experience worse performance after the migration/loadvm. To workaround these issues VMs must be completely rebooted. Optimally we should be able to restore a VM's memory state an expect no performance issue. [Test Case] * savevm/loadvm: - Create a VM and install a test suite such as lmbench. - Get numbers right after boot and record them. - Open up the qemu monitor and type the following: stop savevm 0 loadvm 0 c - Measure performance and record numbers. - Compare if numbers are within margin of error. * migrate: - Create VM, install lmbench, get numbers. - Open up qemu monitor and type the following: stop migrate exec:dd of=~/save.vm quit - Start a new VM using qemu but add the following argument: -incoming exec:dd if=~/save.vm - Run performance test and compare. If performance measured is similar then we pass the test case. [Regression Potential] * The fix is a backport of two upstream patches: ad0b5321f1f797274603ebbe20108b0750baee94 211ea74022f51164a7729030b28eec90b6c99a08 - On patch allows QEMU to use THP if its enabled. + One patch allows QEMU to use THP if its enabled. The other patch changes logic to not memset pages to zero when loading memory for the vm (on an incoming migration). - * I've also run the qa-regression-testing test-qemu.py script and it passes all tests. + * I've also run the qa-regression-testing test-qemu.py script and it + passes all tests. + + [Additional Information] + + Kernels from 3.2 onwards are affected, and all have the config: + CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y. Therefore enabling THP is + applicable. + -- I have 2 physical hosts running Ubuntu Precise. With 1.0+noroms- 0ubuntu14.7 and qemu-kvm 1.2.0+noroms-0ubuntu7 (source from quantal, built for Precise with pbuilder.) I attempted to build qemu-1.3.0 debs from source to test, but libvirt seems to have an issue with it that I haven't been able to track down yet. I'm seeing a performance degradation after live migration on Precise, but not Lucid. These hosts are managed by libvirt (tested both 0.9.8-2ubuntu17 and 1.0.0-0ubuntu4) in conjunction with OpenNebula. I don't seem to have this problem with lucid guests (running a number of standard kernels, 3.2.5 mainline and backported linux- image-3.2.0-35-generic as well.) I first noticed this problem with phoronix doing compilation tests, and then tried lmbench where even simple calls experience performance degradation. I've attempted to post to the kvm mailing list, but so far the only suggestion was it may be related to transparent hugepages not being used after migration, but this didn't pan out. Someone else has a similar problem here - http://thread.gmane.org/gmane.comp.emulators.kvm.devel/100592 qemu command line example: /usr/bin/kvm -name one-2 -S -M pc-1.2 -cpu Westmere -enable-kvm -m 73728 -smp 16,sockets=2,cores=8,threads=1 -uuid f89e31a4-4945-c12c-6544-149ba0746c2f -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/one-2.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -no-kvm-pit-reinjection -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/one//datastores/0/2/disk.0,if=none,id=drive-virtio- disk0,format=raw,cache=none -device virtio-blk- pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio- disk0,bootindex=1 -drive file=/var/lib/one//datastores/0/2/disk.1,if=none,id=drive- ide0-0-0,readonly=on,format=raw -device ide-cd,bus=ide.0,unit=0,drive =drive-ide0-0-0,id=ide0-0-0 -netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=25 -device virtio-net- pci,netdev=hostnet0,id=net0,mac=02:00:0a:64:02:fe,bus=pci.0,addr=0x3 -vnc 0.0.0.0:2,password -vga cirrus -incoming tcp:0.0.0.0:49155 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 Disk backend is LVM running on SAN via FC connection (using symlink from /var/lib/one/datastores/0/2/disk.0 above) ubuntu-12.04 - first boot == Simple syscall: 0.0527 microseconds Simple read: 0.1143 microseconds Simple write: 0.0953 microseconds Simple open/close: 1.0432 microseconds Using phoronix pts/compuational ImageMagick - 31.54s Linux Kernel 3.1 - 43.91s Mplayer - 30.49s PHP - 22.25s ubuntu-12.04 - post live migration == Simple syscall: 0.0621 microseconds Simple read: 0.2485 microseconds Simple write: 0.2252 microseconds Simple open/close: 1.4626 microseconds Using phoronix pts/compilation ImageMagick - 43.29s Linux Kernel 3.1 - 76.67s Mplayer - 45.41s PHP - 29.1s I
[Bug 1236265] Re: vmghfs not being build
** Branch linked: lp:~n-muench/ubuntu/saucy/open-vm-tools/open-vm-tools .sept-update -- 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/1236265 Title: vmghfs not being build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1236265/+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 1236265] Re: vmghfs not being build
For those who wish to help me figure this out. Here's the notable part of the boot log: [ 125.729819] vmhgfs: disagrees about version of symbol vmci_datagram_destroy_handle [ 125.729823] vmhgfs: Unknown symbol vmci_datagram_destroy_handle (err -22) [ 125.729865] vmhgfs: disagrees about version of symbol vmci_datagram_send [ 125.729867] vmhgfs: Unknown symbol vmci_datagram_send (err -22) [ 125.729907] vmhgfs: disagrees about version of symbol vmci_datagram_create_handle [ 125.729909] vmhgfs: Unknown symbol vmci_datagram_create_handle (err -22) Don't know which version of vmci it is: Package or Kernel The current incarnation of my prep branch (which I updated 30 minutes ago) is taking vmci completely out of the package equation (as in DKMS doesn't notice it during the build process). Since you didn't specify which VMware product you're using I'm going to assume it's the new version of Workstation/Player/Fusion possibly available. Use those tools that come with the program -- 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/1236265 Title: vmghfs not being build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1236265/+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 1236594] Re: cc_mounts fails to properly find ephermal0 on first partition
Confirmed on EC2: -Boot m1.small. disabled /etc/fstab for swap and mnt. Ran code and confirmed that /mnt and swap were activated. Confirmed on Azure: - tested against parted and unparted /mnt Confirmed fix. -- 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/1236594 Title: cc_mounts fails to properly find ephermal0 on first partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1236594/+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 1236594] [NEW] cc_mounts fails to properly find ephermal0 on first partition
Public bug reported: ephemeral0 should map to ephemeral0.1 or ephemeral0, but it doesn't. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: cloud-init 0.7.3~bzr879-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Mon Oct 7 21:09:58 2013 MarkForUpload: True PackageArchitecture: all SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cloud-init (Ubuntu) Importance: Undecided Assignee: Ben Howard (utlemming) Status: New ** Tags: amd64 apport-bug saucy uec-images ** Branch linked: lp:~utlemming/cloud-init/lp1236594-bad_ephemeral0_mnt -- 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/1236594 Title: cc_mounts fails to properly find ephermal0 on first partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1236594/+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 1236265] Re: vmghfs not being build
Thank you for working on it :) You're right, it's Fusion 6.0.1 If you tell me I'm better off using VMWare Tools I'll do that. I'd just prefer the open-vm-tools. If've been happy with them so far. -- 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/1236265 Title: vmghfs not being build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1236265/+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 1236265] Re: vmghfs not being build
I prefer the open-vm-tools too. I use both versions on my Scratch machine: open-vm-tools for the modules and the proprietary package for everything else. In my time maintaining this package, I've never had this much trouble with this package during a cycle. -- 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/1236265 Title: vmghfs not being build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1236265/+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 1234132] [NEW] Wrong order for mountall-net
You have been subscribed to a public bug: When using DNS resolving daemons like dnsmasq the mountall-net is done to early in the boot process when DNS is not available. ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: Triaged -- Wrong order for mountall-net https://bugs.launchpad.net/bugs/1234132 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq 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 1234132] Re: Wrong order for mountall-net
Well, I see no sense for dnsmasq to run on a desktop. And I see no sense for networmanager to run on a server. Well, while I agree that networkmanager isn't fit for servers, I don't think there are many people using dnsmasq on servers this way, either. Well, dnsmasq _is_ a DNS server and it is usually the primary one. Adding more DNS servers to the resolv.conf makes your server depending on systems you do not want them depending on. You're always dependent on external servers for DNS; in the best case (which is the case dnsmasq aspires to), you're only dependent on the root servers and authoritative servers, but dnsmasq itself doesn't change the fact that there's an external dependency. I could understand if you said you were running bind, or some other *authoritative* nameserver for your local network, since that would ensure reliability in the face of an upstream network outage; but that's not what you're doing here, so dnsmasq isn't actually providing more reliability than if you were just pointing at whichever upstream forwarding resolvers you deem appropriate (proximity vs. high-availability, etc). And in one concrete fashion, your dnsmasq-only configuration is *less* reliable than using resolvers on the network, because it adds dnsmasq as a boot dependency in the rest of the system and the dnsmasq package isn't handling that boot dependency the way you need it to. mountall is a essential part of the system; as is DNS. It is easily possible with a normal system-V system to build this dependency. If it is not with upstart ... However, I am not a expert of upstart so it might be possibly with it too. Of course it's possible to do that with upstart. The bug is that this hasn't *been done* for dnsmasq. And this is in no way upstart-specific, you would have the same race condition with this dnsmasq package on a sysvinit system; just because you might know how to manually mangle an init script to get it to start earlier doesn't mean the system is properly integrated. In fact, the dnsmasq init script declares that it wants network mounts to be done before it starts, which would cause a circular dependency for you! I really don't think the configuration you describe is one that we want to support, but if we were going to support it, the right way to do this would be for dnsmasq to integrate with mountall by sending its own SIGUSR1 once started. dnsmasq does not itself need to be converted to use an upstart job to do this - it can make the same calls in /etc/init.d/dnsmasq that are made in /etc/init/mountall-net.conf - though perhaps it makes sense to convert it to an upstart job rather than including upstart-specific hooks in the init script. ** Package changed: mountall (Ubuntu) = dnsmasq (Ubuntu) ** Changed in: dnsmasq (Ubuntu) Status: Incomplete = Triaged ** Summary changed: - Wrong order for mountall-net + dnsmasq needs to trigger mountall rescan of network mounts -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1234132 Title: dnsmasq needs to trigger mountall rescan of network mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1234132/+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 1236367] Re: [FFe] ceph 0.67.4 point release
** Branch linked: lp:ubuntu/saucy-proposed/ceph -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1236367 Title: [FFe] ceph 0.67.4 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1236367/+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 1236544] Re: canot access static images over http with apache 2.2 (precise)
** Tags added: theme-oil -- 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/1236544 Title: canot access static images over http with apache 2.2 (precise) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1236544/+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 1228228] Re: ubuntu is not added to sudo group
** Branch linked: lp:ubuntu/cloud-init -- 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/1228228 Title: ubuntu is not added to sudo group To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1228228/+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 1234331] Re: cloud-init should respect /etc/growroot-disabled
** Branch linked: lp:ubuntu/cloud-init -- 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/1234331 Title: cloud-init should respect /etc/growroot-disabled To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1234331/+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 1236445] Re: smartos hostname assignment fails due to whitespace
** Branch linked: lp:ubuntu/cloud-init -- 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/1236445 Title: smartos hostname assignment fails due to whitespace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1236445/+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 1236594] Re: cc_mounts fails to properly find ephermal0 on first partition
** Branch linked: lp:cloud-init -- 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/1236594 Title: cc_mounts fails to properly find ephermal0 on first partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1236594/+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 1236367] Re: [FFe] ceph 0.67.4 point release
This bug was fixed in the package ceph - 0.67.4-0ubuntu1 --- ceph (0.67.4-0ubuntu1) saucy; urgency=low * New upstream bugfix release (LP: #1236367). -- James Page james.p...@ubuntu.com Mon, 07 Oct 2013 15:18:41 +0100 ** Changed in: ceph (Ubuntu Saucy) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1236367 Title: [FFe] ceph 0.67.4 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1236367/+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 1069570] Re: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases
This is happening because MAAS added the host{} entry for its MAC before
the lease expired. The 30 second thing is clearly a hack and doesn't
work properly because it's a race condition with MAAS lease scanner.
The only real solution is to SRU the ignore-client-ids fix.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1069570
Title:
1 MAC Address, two IPs - DNS is out of sync with DHCP leases
databases
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1069570/+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 1236594] Re: cc_mounts fails to properly find ephermal0 on first partition
This bug was fixed in the package cloud-init - 0.7.3-0ubuntu2 --- cloud-init (0.7.3-0ubuntu2) saucy; urgency=low * fix bug where a mount entry of 'ephemeral0' would only consider the unpartitioned device, not also the first partition (LP: #1236594) -- Scott Moser smo...@ubuntu.com Mon, 07 Oct 2013 20:16:02 -0400 ** Changed in: cloud-init (Ubuntu) Status: New = Fix Released -- 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/1236594 Title: cc_mounts fails to properly find ephermal0 on first partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1236594/+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 1236445] Re: smartos hostname assignment fails due to whitespace
This bug was fixed in the package cloud-init - 0.7.3-0ubuntu2 --- cloud-init (0.7.3-0ubuntu2) saucy; urgency=low * fix bug where a mount entry of 'ephemeral0' would only consider the unpartitioned device, not also the first partition (LP: #1236594) -- Scott Moser smo...@ubuntu.com Mon, 07 Oct 2013 20:16:02 -0400 ** Changed in: cloud-init (Ubuntu) Status: Confirmed = Fix Released -- 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/1236445 Title: smartos hostname assignment fails due to whitespace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1236445/+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 1227252] Re: Upgrade from precise to precise SRU maas unconditionally disabled system DHCP
I think this is purely a packaging bug, so invalidating the maas task that was just added. ** Changed in: maas Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1227252 Title: Upgrade from precise to precise SRU maas unconditionally disabled system DHCP To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1227252/+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 1231693] Re: maas-dhcp backport does not start on precise
** Changed in: maas Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1231693 Title: maas-dhcp backport does not start on precise To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1231693/+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 1155556] Re: HP ProLiant DL380 G7 tftps kernel, but initrd tracebacks in tftp server. DL380 G6 succeeds.
The fixed package should be in the cloud archive. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-tx-tftp in Ubuntu. https://bugs.launchpad.net/bugs/116 Title: HP ProLiant DL380 G7 tftps kernel, but initrd tracebacks in tftp server. DL380 G6 succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/116/+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 1208506] Re: vsftpd respawns too fast and fails on server boot with pasv_address pasv_addr_resolve=YES
[Expired for vsftpd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vsftpd (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/1208506 Title: vsftpd respawns too fast and fails on server boot with pasv_address pasv_addr_resolve=YES To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1208506/+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 1236361] Re: need new simple streams based maas-import-ephemerals
** Changed in: maas Status: Confirmed = Triaged ** Changed in: maas Importance: Undecided = Critical -- 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/1236361 Title: need new simple streams based maas-import-ephemerals To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1236361/+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
Fujitsu BX900/DX90 installation problem
Hello! i try to install ubuntu 13.04 server on Fujitsu BX900 (BX924S3 diskless blade) whose storage is Fujitsu DX90 iSCSI target (iSCSI boot). in the BX924S3 blade Emulex CNA 10G adapter is used. this device has hardware iSCSI support. i configure iSCSI initiators on it. after that corresponding LUNs become visible in the BX924S3 blade's BIOS. ubuntu installer does not detect LUNs available in such a way. i think its Detect disks/login to iSCSI target functionality supposes starting of software iSCSI initiator in the OS instead of detecting and working with LUNs connected via Emulex CNA adapter. at the same time system successfully detects the presence of Emulex CNA adapter. also in the OS i see loaded components be2iscsi/*. SLES 11 SP3 and CentOS 6.4 successfully detect such hardware configuration. they are installed, run and work (i have corresponding dmesg and lsmod). are there any chances that this hardware configuration will also work in ubuntu in the nearest future? Regards, -- Andy Igoshin a...@vsu.ru Voronezh State University sip: a...@vsu.ru Network Operation Center phone: +7 473 2281160, ext. 2020 Voronezh, Russia -- ubuntu-server mailing list ubuntu-server@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
