[Bug 802400] Re: mysql help sends unchecked contents to mysqld
https://mariadb.atlassian.net/browse/MDEV-687 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/802400 Title: mysql help sends unchecked contents to mysqld To manage notifications about this bug go to: https://bugs.launchpad.net/maria/+bug/802400/+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 1032550] Re: [multipath] failed to get sysfs information
I'm seeing the same issue with an EMC clariion, see attached syslog. On my systems this problem leads to hanging processes and a server crash that can only be fixed with a reboot .. ** Attachment added: syslog of multipath failure https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+attachment/3456041/+files/syslog_multipath_fail.gz -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1032550 Title: [multipath] failed to get sysfs information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+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 1032550] Re: [multipath] failed to get sysfs information
** Attachment added: My multipath.conf https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+attachment/3456042/+files/multipath.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1032550 Title: [multipath] failed to get sysfs information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+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 1082699] Re: cannot copy to samba share
the upgrade did not help. I started a new thread at http://askubuntu.com/questions/227458/cannot-copy-to-samba-share-ubuntu Thank you for your time -- 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/1082699 Title: cannot copy to samba share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1082699/+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 1088411] [NEW] Cannot attach volumes to instances if using NexentaStor driver
Public bug reported: It looks like the bug #871278 is still present in NexentaStor driver. I'm using Ubuntu 12.04.1 64bit with cinder-volumes package 2012.2-0ubuntu2~cloud0 and if I try to attach cinder volume to an instance, it fails with the following error in nova-compute.log: 2012-12-05 16:10:26 TRACE Error: iSCSI device not found at /dev/disk/by- path/ip-10.1.0.2:3260-iscsi-iqn.1986-03.com.sun:02:cinder- volume-001-lun-1 However the file /dev/disk/by-path/ip-10.1.0.2:3260-iscsi- iqn.1986-03.com.sun:02:cinder-volume-001-lun-0 exists. So if I do ln -s /dev/disk/by-path/ip-10.1.0.2:3260-iscsi-iqn.1986-03.com.sun:02 :cinder-volume-001-lun-0 /dev/disk/by-path/ip-10.1.0.2:3260-iscsi- iqn.1986-03.com.sun:02:cinder-volume-001-lun-1 everything works. I fixed it by changing line 232 in /usr/share/pyshared/cinder/volume/nexenta/volume.py from 'lun': '0'}) to 'lun': '1'}) ** Affects: cinder (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Cannot attach volumes to instances if using NexentaStror driver + Cannot attach volumes to instances if using NexentaStor driver -- 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/1088411 Title: Cannot attach volumes to instances if using NexentaStor driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1088411/+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 1086833] Re: All nova upstart configuration use 'su' instead of 'start-stop-daemon'
** Changed in: nova (Ubuntu Raring) Status: New = Fix Committed -- 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/1086833 Title: All nova upstart configuration use 'su' instead of 'start-stop-daemon' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1086833/+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 1088312] Re: package setserial 2.17-47 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. This looks like a local configuration problem, rather than a bug in Ubuntu, so I'm marking this bug as Invalid. Specifically, your /etc/init.d/setserial file is missing, which is supplied by the package. Try purging and reinstalling setserial, instead of simply uninstalling and reinstalling. If you still have problems, you can find pointers to get help for this sort of issue here: http://www.ubuntu.com/support/community If you believe that this is really a bug, then you may find it helpful to read How to report bugs effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, and then change the bug status back to New. ** Changed in: setserial (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to setserial in Ubuntu. https://bugs.launchpad.net/bugs/1088312 Title: package setserial 2.17-47 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/setserial/+bug/1088312/+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 1088235] Re: package puppetmaster-passenger 2.7.18-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. This looks like a local configuration problem, rather than a bug in Ubuntu, so I'm marking this bug as Invalid. Specifically, it looks like you have a misconfigured web server installed, or perhaps multiple installations of passenger. You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community If you believe that this is really a bug, then you may find it helpful to read How to report bugs effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, and then change the bug status back to New. ** Changed in: puppet (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1088235 Title: package puppetmaster-passenger 2.7.18-1ubuntu1 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/puppet/+bug/1088235/+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 1087261] Re: package openssh-server 1:5.3p1-3ubuntu7 failed to install/upgrade: el subproceso post-installation script devolvió el código de salida de error 2
From log: Configurando openssh-server (1:5.3p1-3ubuntu7) ... Creating SSH2 RSA key; this may take some time ... Creating SSH2 DSA key; this may take some time ... exec: 34: /lib/init/upstart-job: not found invoke-rc.d: initscript ssh, action stop failed. dpkg: error al procesar openssh-server (--configure): el subproceso post-installation script devolvió el código de salida de error 2 Processing triggers for libc-bin ... -- 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/1087261 Title: package openssh-server 1:5.3p1-3ubuntu7 failed to install/upgrade: el subproceso post-installation script devolvió el código de salida de error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1087261/+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 1087261] Re: package openssh-server 1:5.3p1-3ubuntu7 failed to install/upgrade: el subproceso post-installation script devolvió el código de salida de error 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. This looks like a local configuration problem, rather than a bug in Ubuntu, so I'm marking this bug as Invalid. Specifically, you seem to be running some packages from 8.04, and some from 10.04. Is this part of an aborted or incomplete upgrade? You can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community If you believe that this is really a bug, then you may find it helpful to read How to report bugs effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, and then change the bug status back to New. ** Changed in: openssh (Ubuntu) Status: New = Invalid -- 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/1087261 Title: package openssh-server 1:5.3p1-3ubuntu7 failed to install/upgrade: el subproceso post-installation script devolvió el código de salida de error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1087261/+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 1088136] Re: AUTH cannot handle a request with an initial-response over 2048 bytes (GSSAPI-related)
Thank you for taking the time prepare this patch and helping to make Ubuntu better. There are just a few things we need to do in order to get this fix ready for sponsoring and then for the stable release team to approve. Please note that I'm making these comments as a bug triager only. I cannot sponsor this package, but this might save you some time getting this patch through the sponsorship queue. Most of these are requirements from https://wiki.ubuntu.com/StableReleaseUpdates Can you please confirm that this bug is definitely fixed in the current development release (Raring)? This needs to be done first, and then this bug needs to be marked Fix Released with a task added for Precise. The test case needs to allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. This requirement is from SRU policy. I don't think your test case is detailed enough for me, and I am familiar with GSSAPI (via Kerberos)! Please could you provide sufficient detail in your test case? The changelog should detail exactly what is being fixed, rather than just referring to the upstream bug. The version number in the changelog should be 4.76-3ubuntu3.2 rather than 4.76-3ubuntu3.1+bug1088136, and targeted at precise-proposed rather than precise. I'm sure a sponsor would make these minor changes for you, but you might want to be aware of this and/or correct it. It's great that you have DEP-3 headers in the patch. It could help though if you added a Bug-Ubuntu header that points to this bug. Once you're happy, please subscribe ~ubuntu-sponsors to this bug to make sure it makes it in the sponsorship queue. ~ubuntu-sru will need to be subscribed to approve the upload, but it is a sponsor who will actually need to do the upload itself. Thanks again for your help! ** Changed in: exim4 (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to exim4 in Ubuntu. https://bugs.launchpad.net/bugs/1088136 Title: AUTH cannot handle a request with an initial-response over 2048 bytes (GSSAPI-related) To manage notifications about this bug go to: https://bugs.launchpad.net/exim/+bug/1088136/+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 1088136] Re: AUTH cannot handle a request with an initial-response over 2048 bytes (GSSAPI-related)
** Description changed:
smtp_cmd_buffer_size is currently 2048 bytes. 2048 bytes is not sufficient
for
clients that send an AUTH with an initial-response for GSSAPI when Windows
Kerberos tickets are used that contain a PAC -- as of Windows 2003, the
maximum
ticket size is 12000 bytes.
MUAs that use AUTH GSSAPI without an initial-response are not impacted by the
2048 limit, since the remainder of the SASL session is handled by
auth_get_data
in Exim, which uses big_buffer and has sufficient space to process large
Kerberos tickets.
Thunderbird will always send an AUTH GSSAPI with an initial-response, which
makes it subject to the 2048 byte limit. A large Kerberos ticket will easily
surpass 2048 bytes when base64-encoded, causing the AUTH to fail.
RFC 4954 recommends 12288 bytes as a line limit to handle AUTH. For a base64
encoded max-size Windows Kerberos ticket, at least 16000 bytes are needed.
This bug is fixed upstream (4.77). It would be nice to backport it to
precise.
[Impact]
smtp_cmd_buffer_size is currently 2048 bytes. 2048 bytes is not sufficient
for
clients that send an AUTH with an initial-response for GSSAPI when Windows
Kerberos tickets are used that contain a PAC. For a base64
encoded max-size Windows Kerberos ticket, at least 16000 bytes are needed.
+ Fixing this bug lets us to use exim4 smtp server with AD kerberos
authentication and windows clients, so I think it's worth fixing.
[Test Case]
- 1. Configure exim4 to use GSSAPI auth.
- 2. Configure thunderbird to use GSSAPI smtp auth on windows
xp/vista/7/2003/2008.
- 3. Auth will always fail.
+ 1. You need a configured AD/samba4 domain
+ 2. Configure exim4 to use GSSAPI auth (here is dovecot method):
+ - # apt-get instal dovecot-imapd exim4-daemon-heavy
+ - /etc/krb5.keytab should contain 'smtp/fqdn.host.name@YOUR.REALM'
credentials (import it somehow), just for test make it readable for all. (chmod
644 /etc/krb5.keytab)
+ - your dovecot config should contain something like this:
+ auth_mechanisms = gssapi
+ auth_default_realm = YOUR.REALM
+ auth_realms = YOUR.REALM
+ auth_gssapi_hostname = fqdn.host.name
+ auth_krb5_keytab = /etc/krb5.keytab
+ service auth {
+ unix_listener auth-client {
+ mode = 0600
+ user = Debian-exim
+ }
+ - your exim's 'begin authenticators' section of the config should contain
something like:
+ auth_gssapi:
+ driver= dovecot
+ public_name = GSSAPI
+ server_socket = /var/run/dovecot/auth-client
+ server_set_id = $auth1
+ 3. Configure thunderbird to use GSSAPI smtp auth on windows
xp/vista/7/2003/2008 (member of your AD domain).
+ - install thunderbird or use thunderbird portable
+ - configure any (e.g. it could be nonexisting at all) IMAP/POP mail account
in thunderbird (using some domain member account)
+ - in account settings set authentication address/port to your exim server,
username to your domain username, auth method to 'Kerberos/GSSAPI'
+ 4. Try to send mail. Auth will always fail. In exim's log there will be
messages like these:
+ 2012-12-09 00:04:46 SMTP syntax error in AUTH GSSAPI
[Bug 1088136] Re: AUTH cannot handle a request with an initial-response over 2048 bytes (GSSAPI-related)
** Also affects: exim4 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: exim4 (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: exim4 (Ubuntu Raring) Importance: Medium Status: New ** Changed in: exim4 (Ubuntu Quantal) Status: New = Fix Released ** Changed in: exim4 (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: exim4 (Ubuntu Raring) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to exim4 in Ubuntu. https://bugs.launchpad.net/bugs/1088136 Title: AUTH cannot handle a request with an initial-response over 2048 bytes (GSSAPI-related) To manage notifications about this bug go to: https://bugs.launchpad.net/exim/+bug/1088136/+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 1088136] Re: AUTH cannot handle a request with an initial-response over 2048 bytes (GSSAPI-related)
Hi! I'm confirming that this bug is fixed in raring an quantal. How could I mark it Fix released for raring? I've also updated bug description, made test case more detailed, is it detailed enough now? And here is updated debdiff. Thank you. ** Patch added: updated exim4.debdiff https://bugs.launchpad.net/ubuntu/+source/exim4/+bug/1088136/+attachment/3456247/+files/exim4.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to exim4 in Ubuntu. https://bugs.launchpad.net/bugs/1088136 Title: AUTH cannot handle a request with an initial-response over 2048 bytes (GSSAPI-related) To manage notifications about this bug go to: https://bugs.launchpad.net/exim/+bug/1088136/+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 617463] Re: mysql fails to load innodb plugin due to apparmor rejection.
I confirm this fixes the issue, I don't see the relevant denials in when running the test suite anymore. This fix will be included in the security release that will be published in a few minutes. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/617463 Title: mysql fails to load innodb plugin due to apparmor rejection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/617463/+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 1088136] Re: AUTH cannot handle a request with an initial-response over 2048 bytes (GSSAPI-related)
Thanks! Marc has kindly sorted the bug statuses out for us, and I see that you've subscribed ~ubuntu-sponsors so this is now in the sponsorship queue. The next step is to wait for a sponsor to review your debdiff. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to exim4 in Ubuntu. https://bugs.launchpad.net/bugs/1088136 Title: AUTH cannot handle a request with an initial-response over 2048 bytes (GSSAPI-related) To manage notifications about this bug go to: https://bugs.launchpad.net/exim/+bug/1088136/+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 617463] Re: mysql fails to load innodb plugin due to apparmor rejection.
This bug was fixed in the package mysql-dfsg-5.1 - 5.1.66-0ubuntu0.10.04.3 --- mysql-dfsg-5.1 (5.1.66-0ubuntu0.10.04.3) lucid-security; urgency=low * SECURITY UPDATE: arbitrary code execution via long argument - debian/patches/99_CVE-2012-5611.patch: don't overflow buffer in sql/sql_acl.cc, add tests to mysql-test/t/information_schema.test, mysql-test/r/information_schema.result. - CVE-2012-5611 -- Marc Deslauriers marc.deslauri...@ubuntu.com Fri, 07 Dec 2012 12:14:34 -0500 ** Changed in: mysql-dfsg-5.1 (Ubuntu Lucid) Status: Fix Committed = Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2012-5611 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/617463 Title: mysql fails to load innodb plugin due to apparmor rejection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/617463/+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 1087765] Re: Not all containers get started at bootime
** Changed in: lxc (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1087765 Title: Not all containers get started at bootime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1087765/+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 1032550] Re: [multipath] failed to get sysfs information
It maybe a kernel bug Dec 9 08:16:07 ealxs00195 kernel: [1723012.226196] BUG: soft lockup - CPU#2 stuck for 23s! [kworker/2:5:1283] Vincent Chen EMC2 | E-Lab Linux team -Original Message- From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Ronald Moesbergen Sent: Monday, December 10, 2012 5:07 PM To: Chen, Vincent Subject: [Bug 1032550] Re: [multipath] failed to get sysfs information ** Attachment added: My multipath.conf https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+attachment/3456042/+files/multipath.conf -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1032550 Title: [multipath] failed to get sysfs information Status in “multipath-tools” package in Ubuntu: In Progress Bug description: when shutdown switch port of host HBA, multippath-tool can't get correct information of subpath. by check the multipath output, some storage device type info disapppear and the failed path always stay in path group and don't be clear out. mpath2 (3600601601c102900944737e4a73fe011) dm-51 , size=6.0G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw |-+- policy='round-robin 0' prio=1 status=active | |- #:#:#:# -#:# failed faulty running | `- 5:0:2:5 sdcu 70:32 active ready running `-+- policy='round-robin 0' prio=0 status=enabled |- 5:0:3:5 sdfa 129:192 active ready running `- #:#:#:# -#:# failed faulty running mpath38 (3600601601c1029008eb6dbe8ae3fe011) dm-59 DGC,VRAID size=5.0G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw |-+- policy='round-robin 0' prio=1 status=active | `- 5:0:2:13 sddf 70:208 active ready running `-+- policy='round-robin 0' prio=0 status=enabled `- 5:0:3:13 sdfk 130:96 active ready running mpath63 (3697198700131533030303932) dm-13 EMC,SYMMETRIX size=5.6G features='0' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active |- 5:0:0:8 sdl 8:176 active ready running `- 5:0:1:8 sdbd 67:112 active ready running mpath95 (3697198700131533030323445) dm-43 , size=898M features='0' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active |- #:#:#:# -#:# failed faulty running |- #:#:#:# -#:# failed faulty running |- 5:0:0:38 sdas 66:192 active ready running `- 5:0:1:38 sdck 69:128 active ready running Same time, the syslog show many --- Aug 2 18:25:16 Linux51 multipathd: sdht: failed to get sysfs information Aug 2 18:25:16 Linux51 multipathd: sdht: unusable path ... ... --- After path recover, all failed path come back without problem. there is no IP blocked and error happend during fail/recover period. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1032550 Title: [multipath] failed to get sysfs information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+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 1087765] Re: Not all containers get started at bootime
** Changed in: lxc (Ubuntu) Assignee: (unassigned) = Serge Hallyn (serge-hallyn) -- 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/1087765 Title: Not all containers get started at bootime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1087765/+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 1032550] Re: [multipath] failed to get sysfs information
What I really need is a crashdump. I'm simply short on time to reproduce this myself. https://wiki.ubuntu.com/Kernel/CrashdumpRecipe Configure sysctl to panic on oops, that should do it. This stack section is interesting. Dec 9 09:18:27 ealxs00195 kernel: [1726974.078795] RIP: 0010:[8165b049] [8165b049] _raw_spin_unlock_irqrestore+0x19/0x30 ... Dec 9 09:18:27 ealxs00195 kernel: [1726974.091694] [8142f764] __scsi_remove_target+0xd4/0xf0 Dec 9 09:18:27 ealxs00195 kernel: [1726974.091696] [8142f841] scsi_remove_target+0xc1/0xe0 Dec 9 09:18:27 ealxs00195 kernel: [1726974.091701] [a00deb96] fc_starget_delete+0x26/0x30 [scsi_transport_fc] Dec 9 09:18:27 ealxs00195 kernel: [1726974.091706] [81084b1a] process_one_work+0x11a/0x480 It's required to be able to sleep in a workq context, we're grabbing spinlocks here, which when done quickly is fine, but holding them too long and well, you see this. I doubt this is the root cause, something else is likely holding the locks due to an error handling condition and the removal threads are just victims. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/1032550 Title: [multipath] failed to get sysfs information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1032550/+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 1088540] [NEW] ec2-bundle-image gives error 'can't convert Fixnum into String'
Public bug reported: $ ec2-bundle-image --cert cert.pem --privatekey pk.pem --user 123456789012 --image my.img --arch i386 --debug Bundling image file... ERROR: can't convert Fixnum into String #TypeError: can't convert Fixnum into String /usr/lib/ec2-ami-tools/lib/ec2/amitools/util.rb:19:in `+' /usr/lib/ec2-ami-tools/lib/ec2/amitools/util.rb:19:in `block in gen_ident' /usr/lib/ec2-ami-tools/lib/ec2/amitools/util.rb:19:in `each' /usr/lib/ec2-ami-tools/lib/ec2/amitools/util.rb:19:in `inject' /usr/lib/ec2-ami-tools/lib/ec2/amitools/util.rb:19:in `gen_ident' /usr/lib/ec2-ami-tools/lib/ec2/amitools/fileutil.rb:227:in `block in tempfifo' /usr/lib/ec2-ami-tools/lib/ec2/amitools/fileutil.rb:226:in `each' /usr/lib/ec2-ami-tools/lib/ec2/amitools/fileutil.rb:226:in `tempfifo' /usr/lib/ec2-ami-tools/lib/ec2/amitools/bundle.rb:48:in `bundle_image' /usr/lib/ec2-ami-tools/lib/ec2/amitools/bundleimage.rb:56:in `bundle_image' /usr/lib/ec2-ami-tools/lib/ec2/amitools/bundleimage.rb:85:in `main' /usr/lib/ec2-ami-tools/lib/ec2/amitools/tool_base.rb:201:in `run' /usr/lib/ec2-ami-tools/lib/ec2/amitools/bundleimage.rb:93:in `main' I found this when trying with real cert.pem and pk.pem and user, but the error occurs before those things are actually tested, so you can do: mkdir foo; cd foo img=my.img; cert=cert.pem; pk=pk.pem; user=123456789012 truncate --size 1M $img mke2fs -F $img touch $cert $pk ec2-bundle-image --cert $cert --privatekey $pk --user $user --image $img --arch i386 --debug ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ec2-ami-tools 1.4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Mon Dec 10 11:07:25 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-19 (418 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ec2-ami-tools UpgradeStatus: Upgraded to quantal on 2011-11-07 (399 days ago) ** Affects: ec2-ami-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ec2-ami-tools in Ubuntu. https://bugs.launchpad.net/bugs/1088540 Title: ec2-bundle-image gives error 'can't convert Fixnum into String' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-ami-tools/+bug/1088540/+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 1088540] Re: ec2-bundle-image gives error 'can't convert Fixnum into String'
This seems to be a change from ruby 1.8 to 1.9, that caused 'gen_ident' to be
valid.
basically, before it had:
##
# generate a unique identifier used for filenames
#
def gen_ident()
(0..19).inject() {|ident, n| ident+(?A + Kernel.rand(26)).chr}
end
That needs updating to:
(0..19).inject() {|ident, n| ident+(?A.ord + Kernel.rand(26)).chr}
** Changed in: ec2-ami-tools (Ubuntu)
Importance: Undecided = Medium
** Changed in: ec2-ami-tools (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ec2-ami-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1088540
Title:
ec2-bundle-image gives error 'can't convert Fixnum into String'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-ami-tools/+bug/1088540/+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 1088540] Re: ec2-bundle-image gives error 'can't convert Fixnum into String' with ruby 1.9
** Summary changed: - ec2-bundle-image gives error 'can't convert Fixnum into String' + ec2-bundle-image gives error 'can't convert Fixnum into String' with ruby 1.9 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ec2-ami-tools in Ubuntu. https://bugs.launchpad.net/bugs/1088540 Title: ec2-bundle-image gives error 'can't convert Fixnum into String' with ruby 1.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-ami-tools/+bug/1088540/+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 1084089] Re: lxc-clone shouldn't add fstab line if it wasn't there originally
** Branch linked: lp:ubuntu/lxc -- 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/1084089 Title: lxc-clone shouldn't add fstab line if it wasn't there originally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1084089/+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 1087765] Re: Not all containers get started at bootime
What kind of storage is /data on? Is it possible that /data is not yet available when runlevel 2 starts? ** Changed in: lxc (Ubuntu) Status: New = Incomplete -- 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/1087765 Title: Not all containers get started at bootime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1087765/+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 1088611] [NEW] using random hostnames to detect dns proxies allows for false positives
Public bug reported: The fix that's been applied for bug #974509 checks for the presence of a redirector by looking of three hostnames, and treating as invalid any results pointing to a matching address: - does-not-exist.example.com. - example.invalid. - a random, unqualified 32-character alphanumeric hostname. The last of these carries a small but non-zero risk of colliding with a real hostname, and there's a small but non-zero risk that this host points to the same address as something we care about. If possible, it would be better to not include this random-host lookup in the algorithm, as somewhere, some day, chances are there will eventually be a collision, causing an incomprehensible and unreproducible failure for a user. ** Affects: cloud-init (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/1088611 Title: using random hostnames to detect dns proxies allows for false positives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1088611/+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 1088053] Re: Kernel needs to provide FIFREEZE/FITHAW ioctl so that open-vm-dkms can build
What's the status of this? I told you the problem and the solution. I have the branch done, I'm just waiting for it (FIFREEZE/FITHAW ioctl) to be compiled into the kernel. -- 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/1088053 Title: Kernel needs to provide FIFREEZE/FITHAW ioctl so that open-vm-dkms can build To manage notifications about this bug go to: https://bugs.launchpad.net/open-vm-tools/+bug/1088053/+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 1018554] Re: write timestamp to console on halt/reboot/shutdown
FWIW, this would be more precise if it had a start condition of: start on runlevel [06] though it's unlikely that cloud users are going to make much use of runlevels other than runlevel 2. -- 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/1018554 Title: write timestamp to console on halt/reboot/shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1018554/+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 1088611] Re: using random hostnames to detect dns proxies allows for false positives
Instead of random request, you can check the checksum of: http://start.ubuntu.com/connectivity-check.html Which is highly available connectivity check hosted for installer purposes currently and is used by ubiquity. -- 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/1088611 Title: using random hostnames to detect dns proxies allows for false positives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1088611/+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 998712] Re: domain name completion broken when dnsmasq is used
@Wolf: Is it the case that when using the NM-controlled dnsmasq, fully qualified domain names can always be resolved using the glibc resolver but short domain names cannot be resolved using the resolver, despite the correct search option being present in /etc/resolv.conf; that this anomaly does not always occur, but when it does occur it lasts about five minutes? Please correct me if any of the following is not (no longer) true. Please try to provide as complete information as possible. In the anomalous situation, your /etc/resolv.conf contains the following nameserver 127.0.1.1 search rsb.intern rsb.at and nm-tool|grep DNS shows the following DNS:10.1.0.4 and the following command fails with unknown host s4 ping s4 but the following two commands succeed. ping s4.rsb.intern ping s4.rsb.at When the anomaly occurs, does dig s4.rsb.intern work on the affected system? When the anomaly occurs, does dig s4.rsb.at work on the affected system? When the anomaly occurs, does dig s4 +search work on the affected system? -- 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/998712 Title: domain name completion broken when dnsmasq is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/998712/+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 998712] Re: domain name completion broken when dnsmasq is used
nm-tool | grep DNS gives DNS: 10.1.0.4 DNS: 10.1.0.254 DNS: 195.202.128.3 dig s4 gives nothing wolf@mbp:~$ dig s4 ; DiG 9.8.1-P1 s4 ;; global options: +cmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 60009 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;s4.IN A ;; Query time: 1 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Mon Dec 10 21:52:10 2012 ;; MSG SIZE rcvd: 20 but dig s4 + search returns s4.rsb.intern IP and the domain rsb.intern wolf@mbp:~$ dig s4 +search ; DiG 9.8.1-P1 s4 +search ;; global options: +cmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NOERROR, id: 28303 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;s4.rsb.intern. IN A ;; ANSWER SECTION: s4.rsb.intern. 34000 IN A 10.1.0.4 ;; AUTHORITY SECTION: rsb.intern. 34000 IN NS s4.rsb.intern. ;; Query time: 1 msec ;; SERVER: 127.0.1.1#53(127.0.1.1) ;; WHEN: Mon Dec 10 21:51:24 2012 ;; MSG SIZE rcvd: 61 -- 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/998712 Title: domain name completion broken when dnsmasq is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/998712/+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 1085255] Re: Meta bug for tracking Openstack 2012.2.1 Stable Update
** Also affects: cloud-archive Importance: Undecided Status: New -- 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/1085255 Title: Meta bug for tracking Openstack 2012.2.1 Stable Update To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1085255/+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 1066115] Re: The landscape client plugin doesn't create the config file with the proper permissions
** Description changed: === Begin SRU Information === [Impact] - * If an image does not have landscape-client installed inside it, and the -user provided landscape config, then: -a.) the landscape config file would be written with root:root permissions -so that the user that landscape runs as could not change it. -b.) the landscape package would not be installed. + * If an image does not have landscape-client installed inside it, and the + user provided landscape config, then: + a.) the landscape config file would be written with root:root permissions + so that the user that landscape runs as could not change it. + b.) the landscape package would not be installed. - * The fix here is just to install the landscape-client package. This is -clearly what the user would want. -Additionally, no package installation occurs unless the user made that -request. The fix for 'a' is also addressed by this because the file will -exist on disk with proper permissions before cloud-init writes it, and -will thus keep the same ownership. + * The fix here is just to install the landscape-client package. This is + clearly what the user would want. + Additionally, no package installation occurs unless the user made that + request. The fix for 'a' is also addressed by this because the file will + exist on disk with proper permissions before cloud-init writes it, and + will thus keep the same ownership. [Test Case] - * launch instance with landscape config in user-data like the following: -#cloud-config -apt_upgrade: True -apt_sources: - - source: deb $MIRROR $RELEASE-proposed main -landscape: - client: -url: https://landscape.canonical.com/message-system; -ping_url: http://landscape.canonical.com/ping; -data_path: /var/lib/landscape/client -http_proxy: http://my.proxy.com/foobar; -tags: server,cloud - * upon investigation, /etc/landscape/client.conf should be owned -by 'landscape' user rather than root. + * launch instance with landscape config in user-data like the following: + #cloud-config + apt_upgrade: True + apt_sources: + - source: deb $MIRROR $RELEASE-proposed main + landscape: + client: + url: https://landscape.canonical.com/message-system; + ping_url: http://landscape.canonical.com/ping; + data_path: /var/lib/landscape/client + http_proxy: http://my.proxy.com/foobar; + tags: server,cloud + * upon investigation, /etc/landscape/client.conf should be owned + by 'landscape' user rather than root. - [Regression Potential] - * This was broken before, so it is not likely to be broken worse now. + [Regression Potential] + * If a user with a generic user_data setup is assuming that the 'landscape' config will be applied only on those images which already have landscape-client installed, automatically installing landscape-client will be an unexpected a behavior change. === End SRU Information === - When cloud-init runs and landscape-client is not installed, it creates /etc/landscape/client.conf owned as root:root, whereas landscape-client expects it to be landscape:root. The proper fix is although probably to require installation of landscape-client first, as it will create the file properly, and then landscape-client can update it. -- 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/1066115 Title: The landscape client plugin doesn't create the config file with the proper permissions To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1066115/+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 1088540] Re: ec2-bundle-image gives error 'can't convert Fixnum into String' with ruby 1.9
** Branch linked: lp:~awstools-dev/ubuntu/raring/ec2-ami-tools/raring -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ec2-ami-tools in Ubuntu. https://bugs.launchpad.net/bugs/1088540 Title: ec2-bundle-image gives error 'can't convert Fixnum into String' with ruby 1.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-ami-tools/+bug/1088540/+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 1088681] [NEW] startup script prevents use of IPv6
Public bug reported: The tomcat7 startup script sets java.net.preferIPv4Stack=true if authbind is activated. Ubuntu 12.10 does however include authbind 2, which supports IPv6. Consequently the parameter should not be set anymore. Once I uncommented that line tomcat7 worked just fine via IPv6 and authbind. regards, Hendrik ** Affects: tomcat7 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat7 in Ubuntu. https://bugs.launchpad.net/bugs/1088681 Title: startup script prevents use of IPv6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1088681/+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 1087765] Re: Not all containers get started at bootime
I was not able to reproduce this. Could you edit /etc/init/lxc.conf to add '-l info -o /var/log/lxc-$c.debug' to the lxc-start options, then tar up and post the /var/log/lxc-*.debug files here? ** Changed in: lxc (Ubuntu) Assignee: Serge Hallyn (serge-hallyn) = (unassigned) -- 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/1087765 Title: Not all containers get started at bootime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1087765/+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 1073077] Re: zsh complains about locale_warn on launch
Hello Marti, or anyone else affected, Accepted cloud-init into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/cloud- init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-init (Ubuntu Precise) Status: Triaged = Fix Committed ** Tags added: verification-needed -- 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/1073077 Title: zsh complains about locale_warn on launch To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1073077/+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 1070345] Re: need to restart landscape after updating config
Hello Scott, or anyone else affected, Accepted cloud-init into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/cloud- init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-init (Ubuntu Precise) Status: Triaged = Fix Committed ** Tags added: verification-needed -- 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/1070345 Title: need to restart landscape after updating config To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1070345/+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 1066115] Re: The landscape client plugin doesn't create the config file with the proper permissions
Hello Thomas, or anyone else affected, Accepted cloud-init into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/cloud- init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-init (Ubuntu Precise) Status: Triaged = Fix Committed ** Tags added: verification-needed -- 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/1066115 Title: The landscape client plugin doesn't create the config file with the proper permissions To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1066115/+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 1028501] Re: cloud-init selects wrong mirrors for arm
Hello Scott, or anyone else affected, Accepted cloud-init into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/cloud- init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-init (Ubuntu Precise) Status: Triaged = Fix Committed ** Tags added: verification-needed -- 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/1028501 Title: cloud-init selects wrong mirrors for arm To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1028501/+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 1018554] Re: write timestamp to console on halt/reboot/shutdown
Hello Scott, or anyone else affected, Accepted cloud-init into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/cloud- init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-init (Ubuntu Precise) Status: Triaged = Fix Committed ** Tags added: verification-needed -- 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/1018554 Title: write timestamp to console on halt/reboot/shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1018554/+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 978127] Re: incorrect time on node causes failed oauth
Hello Scott, or anyone else affected, Accepted cloud-init into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/cloud- init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-init (Ubuntu Precise) Status: Triaged = Fix Committed ** Tags added: verification-needed -- 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/978127 Title: incorrect time on node causes failed oauth To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/978127/+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 974509] Re: cloud-init selects wrong mirror with dns server redirection
Hello Chuck, or anyone else affected, Accepted cloud-init into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/cloud- init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-init (Ubuntu Precise) Status: Triaged = Fix Committed ** Tags added: verification-needed -- 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/974509 Title: cloud-init selects wrong mirror with dns server redirection To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/974509/+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 1049146] Re: cloud-init runs again after reboot in release upgraded instance
Hello Andreas, or anyone else affected, Accepted cloud-init into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/cloud- init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-init (Ubuntu Precise) Status: Triaged = Fix Committed ** Tags added: verification-needed -- 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/1049146 Title: cloud-init runs again after reboot in release upgraded instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1049146/+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 1037727] Re: support adding region/availability to mirror selection
Hello Scott, or anyone else affected, Accepted cloud-init into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/cloud- init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-init (Ubuntu Precise) Status: Triaged = Fix Committed ** Tags added: verification-needed -- 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/1037727 Title: support adding region/availability to mirror selection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1037727/+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 1006963] Re: sources.list configuration does not cover security
Hello Scott, or anyone else affected, Accepted cloud-init into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/cloud- init/0.6.3-0ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-init (Ubuntu Precise) Status: Triaged = Fix Committed ** Tags added: verification-needed -- 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/1006963 Title: sources.list configuration does not cover security To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1006963/+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 1088720] [NEW] facter virtual runs lspci unconditionally
Public bug reported: 'facter virtual' runs 'lspci' unconditionally on physical machines. This causes warning spew on machines without PCI, e.g. arm. | root@jenipapo:~# facter virtual | pcilib: Cannot open /proc/bus/pci | lspci: Cannot find any working access method. | physical | root@jenipapo:~# Attached is the patch we've used to fix this locally, but it's probably not suitable for upstream as it assumes Linux. ** Affects: facter (Ubuntu) Importance: Undecided Status: New ** Attachment added: Check for /proc/bus/pci/devices before running lspci https://bugs.launchpad.net/bugs/1088720/+attachment/3456648/+files/diff.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to facter in Ubuntu. https://bugs.launchpad.net/bugs/1088720 Title: facter virtual runs lspci unconditionally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1088720/+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 1088540] Re: ec2-bundle-image gives error 'can't convert Fixnum into String' with ruby 1.9
This bug was fixed in the package ec2-ami-tools - 1.4.0.9-0ubuntu1 --- ec2-ami-tools (1.4.0.9-0ubuntu1) raring; urgency=low * New upstream release 1.4.0.9 (2012-11-12) * add knowledge of 'ap-southeast-2' * add flag '--delegation-token' to tools, to allow use of the iam credentials inside an ec2 instance. * New upstream release 1.4.0.7 (2012-03-26) * centralize the list of regions and locations ec2/amitools/region.rb * add govcloud support, with * public certificate to /ec2/amitools/cert-ec2-gov.pem * knowledge of us-gov-west-1 region * use pid in fifo name, which improves upstream for the same code path that use-mktemp-like-mkfifo-name.patch affects. But the patch here still does a better job. * debian/patches/remove-explicit-regions.patch: rework to build upon existing functionality in upstream code. upstream consolidated the lists to a single place. * New upstream release 1.4.0.5 (2011-12-14) * image bundle is now created with '--user 0' and '--group 0'. This just avoids the local username getting into the tarball. * ec2-bundle-vol: add --filter flag, with description 'Do not use the default filtered files list.' * add knowledge of regions us-west-2 and sa-east-1 * debian/patches/use-mktemp-like-mkfifo-name.patch update to work with ruby 1.9 (LP: #1088540) * add debian/watch and update debian/rules to support uscan. * debian/patches/ruby-1.9-cleanup.patch fix some errors when running with ruby 1.9 -- Scott Moser smo...@ubuntu.com Mon, 10 Dec 2012 18:46:35 -0500 ** Changed in: ec2-ami-tools (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ec2-ami-tools in Ubuntu. https://bugs.launchpad.net/bugs/1088540 Title: ec2-bundle-image gives error 'can't convert Fixnum into String' with ruby 1.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-ami-tools/+bug/1088540/+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 1004775] Re: NetworkManager restarts dnsmasq and adds host route on every IPv6 route lookup
I'm still having the issue with 0.9.4.0-0ubuntu4.2~mtrudel7 in precise. I've also checked the box to have network manager ignore automatically obtained routes but it doesn't help. I even tried using the network- manager package in precise-proposed (0.9.4.0-0ubuntu4.2), and it also still has the issue. It happens pretty regularly with 0.9.4.0-0ubuntu4.2~mtrudel7. It happens exactly every 20 or 30 minutes (sometimes it's exactly 20 minutes, other times it's exactly 30 minutes). This could just be related to when the IPv6 announce timing is though. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1004775 Title: NetworkManager restarts dnsmasq and adds host route on every IPv6 route lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1004775/+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
