[Bug 1020834] [NEW] instance-state: unknown
Public bug reported: After deploy of a maas setup, the different maas managed servers report: "instance-state: unknown" Why is that? It's possible to juju ssh, ping the machine, ping the maas server from the instances, do dns lookup of the maas server from the instances. It's possible to do dns lookup the different instances from the maas server. The maas server is running: Linux orc 2.6.38-15-server #60-Ubuntu SMP Tue May 22 11:45:41 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Description:Ubuntu 12.04 LTS Release:12.04 The bootstrap instance is running: Linux bootstrap 3.2.0-25-generic #40-Ubuntu SMP Wed May 23 20:30:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Description:Ubuntu 12.04 LTS Release:12.04 If nothing is wrong, then I would suggest that it tells me eg. "instances-state: running" or something like that... juju -v status gives me: 2012-07-04 08:33:19,328 DEBUG Initializing juju status runtime 2012-07-04 08:33:19,339 INFO Connecting to environment... 2012-07-04 08:33:19,506 DEBUG Connecting to environment using bootstrap.mydomain.tld... 2012-07-04 08:33:19,507 DEBUG Spawning SSH process with remote_user="ubuntu" remote_host="bootstrap..mydomain.tld" remote_port="2181" local_port="60337". Enter passphrase for key '/root/.ssh/id_rsa': 2012-07-04 08:33:22,534:19667(0x7f2ab4e1e700):ZOO_INFO@log_env@658: Client environment:zookeeper.version=zookeeper C client 3.3.5 2012-07-04 08:33:22,534:19667(0x7f2ab4e1e700):ZOO_INFO@log_env@662: Client environment:host.name=orc 2012-07-04 08:33:22,534:19667(0x7f2ab4e1e700):ZOO_INFO@log_env@669: Client environment:os.name=Linux 2012-07-04 08:33:22,535:19667(0x7f2ab4e1e700):ZOO_INFO@log_env@670: Client environment:os.arch=2.6.38-15-server 2012-07-04 08:33:22,535:19667(0x7f2ab4e1e700):ZOO_INFO@log_env@671: Client environment:os.version=#60-Ubuntu SMP Tue May 22 11:45:41 UTC 2012 2012-07-04 08:33:22,536:19667(0x7f2ab4e1e700):ZOO_INFO@log_env@679: Client environment:user.name=root 2012-07-04 08:33:22,536:19667(0x7f2ab4e1e700):ZOO_INFO@log_env@687: Client environment:user.home=/root 2012-07-04 08:33:22,536:19667(0x7f2ab4e1e700):ZOO_INFO@log_env@699: Client environment:user.dir=/root 2012-07-04 08:33:22,536:19667(0x7f2ab4e1e700):ZOO_INFO@zookeeper_init@727: Initiating client connection, host=localhost:60337 sessionTimeout=1 watcher=0x7f2ab2dbe6b0 sessionId=0 sessionPasswd= context=0x349ed80 flags=0 2012-07-04 08:33:22,537:19667(0x7f2aab9d0700):ZOO_INFO@check_events@1585: initiated connection to server [127.0.0.1:60337] 2012-07-04 08:33:22,704:19667(0x7f2aab9d0700):ZOO_INFO@check_events@1632: session establishment complete on server [127.0.0.1:60337], sessionId=0x138333212e8006d, negotiated timeout=1 2012-07-04 08:33:22,706 DEBUG Environment is initialized. 2012-07-04 08:33:22,707 INFO Connected to environment. 2012-07-04 08:33:22,828:19667(0x7f2aab9d0700):ZOO_ERROR@handle_socket_error_msg@1603: Socket [127.0.0.1:60337] zk retcode=-4, errno=112(Host is down): failed while receiving a server response machines: 0: agent-state: running dns-name: bootstrap.mydomain.tld instance-id: /MAAS/api/1.0/nodes/node-8513e6e8-c116-11e1-a8c8-00163e8a2fa6/ instance-state: unknown services: {} 2012-07-04 08:33:22,831 INFO 'status' command finished successfully ** Affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1020834 Title: instance-state: unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1020834/+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 1020788] Re: package winbind 2:3.4.7~dfsg-1ubuntu3.10
Some of this bug report is not in English. Please translate it into English to make it more understandable to triagers. Thanks! -- 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/1020788 Title: package winbind 2:3.4.7~dfsg-1ubuntu3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1020788/+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 1020788] Re: package winbind 2:3.4.7~dfsg-1ubuntu3.10
-- 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/1020788 Title: package winbind 2:3.4.7~dfsg-1ubuntu3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1020788/+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 1020788] [NEW] package winbind 2:3.4.7~dfsg-1ubuntu3.10
Public bug reported: package winbind 2:3.4.7~dfsg-1ubuntu3.10 failed to install/upgrade: lectura insuficiente en buffer_copy (error en dpkg-deb durante `./usr/share/doc/winbind/changelog.Debian.gz') ProblemType: Package DistroRelease: Ubuntu 10.04 Package: winbind 2:3.4.7~dfsg-1ubuntu3.10 ProcVersionSignature: Ubuntu 2.6.32-41.91-generic 2.6.32.59+drm33.24 Uname: Linux 2.6.32-41-generic i686 Architecture: i386 Date: Mon Jul 2 18:40:24 2012 ErrorMessage: lectura insuficiente en buffer_copy (error en dpkg-deb durante `./usr/share/doc/winbind/changelog.Debian.gz') InstallationMedia: Kubuntu 10.04 Trinity LTS "Lucid Lynx" - Release i386 (20100427) SambaServerRegression: No SourcePackage: samba Title: package winbind 2:3.4.7~dfsg-1ubuntu3.10 failed to install/upgrade: lectura insuficiente en buffer_copy (error en dpkg-deb durante `./usr/share/doc/winbind/changelog.Debian.gz') WindowsFailedConnect: Yes ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- 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/1020788 Title: package winbind 2:3.4.7~dfsg-1ubuntu3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1020788/+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 1020773] Re: package bacula-director-pgsql 5.2.5-0ubuntu6.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 bacula in Ubuntu. https://bugs.launchpad.net/bugs/1020773 Title: package bacula-director-pgsql 5.2.5-0ubuntu6.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/bacula/+bug/1020773/+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 1020773] Re: package bacula-director-pgsql 5.2.5-0ubuntu6.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/1020773 Title: package bacula-director-pgsql 5.2.5-0ubuntu6.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/bacula/+bug/1020773/+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 1020773] [NEW] package bacula-director-pgsql 5.2.5-0ubuntu6.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Was installing Ubuntu-restricted-extras. Update to a database led to this problem and the inability to complete the requested operation. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: bacula-director-pgsql 5.2.5-0ubuntu6.1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu8 AptOrdering: gstreamer0.10-plugins-bad-multiverse: Install ubuntu-restricted-extras: Install bacula-director-pgsql: Configure gstreamer0.10-plugins-bad-multiverse: Configure ubuntu-restricted-extras: Configure Architecture: amd64 Date: Wed Jul 4 11:09:20 2012 DpkgHistoryLog: Start-Date: 2012-07-04 11:07:21 Commandline: apt-get install ubuntu-restricted-extras Install: gstreamer0.10-plugins-bad-multiverse:amd64 (0.10.21-1), ubuntu-restricted-extras:amd64 (57) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) SourcePackage: bacula Title: package bacula-director-pgsql 5.2.5-0ubuntu6.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bacula (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/1020773 Title: package bacula-director-pgsql 5.2.5-0ubuntu6.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/bacula/+bug/1020773/+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 988819] Re: [SRU] wrong path to libxml2.so.2 in mod_security - broken by multiarch enabled libraries
I have serious misgivings about the particular approach taken here, in SRU or otherwise. Why does mod-security.load need to hard-code libxml2.so.2 *at all*? Isn't that why DSOs are dynamically linked to their dependent libraries (which mod_security2.so is)? And why is libxml2.so.2 being special-cased here, when mod_security2.so is also linked against liblua5.1.so.0? Did anyone try to fix this by just removing the LoadFile line completely? That would be a much safer fix than SRUing the core of apache2, and would probably fix the problem that this SRU seems to be stalled waiting for indeterminate regression testing of "corner cases". A naive test here of commenting out this 'LoadFile' line shows that the apache config validates, and apache2-mpm-prefork starts without any problems. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/988819 Title: [SRU] wrong path to libxml2.so.2 in mod_security - broken by multiarch enabled libraries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/988819/+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 1017729] Re: Eucalyptus allows volume creation beyond the limit set in the configuration
While the UI itself does not clearly state the units of this setting, you can see it in the code in clc/modules/core/src/main/java/edu/ucsb/eucalyptus/cloud/entities/StorageInfo.java: @ConfigurableField( description = "Total disk space reserved for volumes", displayName = "Disk space reserved for volumes" ) @Column( name = "system_storage_volume_size_gb" ) private Integer maxTotalVolumeSizeInGb; So the unit is GB, meaning that a value of "600" is approximately 6 Petabytes. I am guessing you were specifying this assuming that it was a smaller unit. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/1017729 Title: Eucalyptus allows volume creation beyond the limit set in the configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/1017729/+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 1020718] Re: package tomcat6 6.0.35-1ubuntu3 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 tomcat6 in Ubuntu. https://bugs.launchpad.net/bugs/1020718 Title: package tomcat6 6.0.35-1ubuntu3 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/tomcat6/+bug/1020718/+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 1020718] Re: package tomcat6 6.0.35-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat6 in Ubuntu. https://bugs.launchpad.net/bugs/1020718 Title: package tomcat6 6.0.35-1ubuntu3 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/tomcat6/+bug/1020718/+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 1020718] [NEW] package tomcat6 6.0.35-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: with the apt-get command i got this error root@nccs:/home/drcdhardy# apt-get install tomcat6 Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: libtcnative-1 The following NEW packages will be installed: tomcat6 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/28.9 kB of archives. After this operation, 256 kB of additional disk space will be used. Preconfiguring packages ... Selecting previously unselected package tomcat6. (Reading database ... 253743 files and directories currently installed.) Unpacking tomcat6 (from .../tomcat6_6.0.35-1ubuntu3_all.deb) ... Processing triggers for ureadahead ... Setting up tomcat6 (6.0.35-1ubuntu3) ... chmod: cannot access `/etc/tomcat6/tomcat-users.xml': No such file or directory dpkg: error processing tomcat6 (--configure): subprocess installed post-installation script returned error exit status 1 E: Sub-process /usr/bin/dpkg returned an error code (1) root@nccs:/home/drcdhardy# ProblemType: Package DistroRelease: Ubuntu 12.04 Package: tomcat6 6.0.35-1ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-26.41-powerpc-smp 3.2.19 Uname: Linux 3.2.0-26-powerpc-smp ppc ApportVersion: 2.0.1-0ubuntu10 AptOrdering: tomcat6: Install tomcat6: Configure Architecture: powerpc Date: Tue Jul 3 15:12:56 2012 DuplicateSignature: Setting up tomcat6 (6.0.35-1ubuntu3) ... chmod: cannot access `/etc/tomcat6/tomcat-users.xml': No such file or directory dpkg: error processing tomcat6 (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release powerpc (20120423.2) PackageArchitecture: all SourcePackage: tomcat6 Title: package tomcat6 6.0.35-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.tomcat6.catalina.properties: [deleted] modified.conffile..etc.tomcat6.context.xml: [deleted] modified.conffile..etc.tomcat6.logging.properties: [deleted] modified.conffile..etc.tomcat6.policy.d.01system.policy: [deleted] modified.conffile..etc.tomcat6.policy.d.02debian.policy: [deleted] modified.conffile..etc.tomcat6.policy.d.03catalina.policy: [deleted] modified.conffile..etc.tomcat6.policy.d.04webapps.policy: [deleted] modified.conffile..etc.tomcat6.policy.d.50local.policy: [deleted] modified.conffile..etc.tomcat6.server.xml: [deleted] modified.conffile..etc.tomcat6.tomcat.users.xml: [deleted] modified.conffile..etc.tomcat6.web.xml: [deleted] mtime.conffile..etc.logrotate.d.tomcat6: 2012-06-20T19:52:45.462484 ** Affects: tomcat6 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package powerpc precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat6 in Ubuntu. https://bugs.launchpad.net/bugs/1020718 Title: package tomcat6 6.0.35-1ubuntu3 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/tomcat6/+bug/1020718/+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 1017729] Re: Eucalyptus allows volume creation beyond the limit set in the configuration
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: eucalyptus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/1017729 Title: Eucalyptus allows volume creation beyond the limit set in the configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/1017729/+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 1016695] Re: add console=tty0 to cloud-image kernel boot parameters
** Attachment added: "console=tty1 console=ttyS0 ds=nocloud" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1016695/+attachment/3212314/+files/serial_output_tty1_ttyS0_nocloud.txt -- 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/1016695 Title: add console=tty0 to cloud-image kernel boot parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1016695/+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 1016695] Re: add console=tty0 to cloud-image kernel boot parameters
Thanks Clint. I understand that we can't lose any messages going to the serial console. So I experimented and I have a different solution that I think would satisfy. My main goal is to *by default* be able to see in the VMware console the kernel messages as well as the first few messages from cloud-init that show cloud-init is searching for the EC2 datasource by default and is timing out. Sending this info only to the serial port means anyone unfamiliar with running a cloud-image in VMware (or other hypervisor) may not understand that cloud-init is behind the scenes searching for the EC2 datasource and timing out. They would sit there wondering why it's taking so long to boot. *Maybe* they'd figure out they can add console=tty1 to their kernel boot parameters so they can see what is going on. I personally think Ubuntu server is great but this could be frustrating to others and potentially lead them to believe something just ain't right with Ubuntu servers. My new solution is to add console=tty1 *before* console=ttyS0. Note that it's tty1 and not tty0. This produces the same results as expected for the serial port. All messages are output to serial as usual. This also outputs all kernel messages and just enough of the cloud-init messages to tty1 which makes it visible in VMware's vSphere console where you can watch it search for the EC2 datasource and timeout. The remainder of the cloud-init messages (including the cloud-init final message) are not visible in the console so you'd have to log in and check the cloud-init log in /var/log to see it's status but that's much better than nothing at all. When the server is done booting the VMware console displays the tty1 as expected which is why I used tty1 instead of tty0. I tested all this by using VMware's ability to output serial port to a file. I have attached a file for the serial port output for each of the following grub kernel parameter entries: linux /boot/vmliuz-3.2.0-24-virtual root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 linux /boot/vmliuz-3.2.0-24-virtual root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 ds=nocloud The first shows cloud-init searching for EC2 datasource and timing out. The second shows the results when cloud-init is configured with ds=nocloud. Do you think this sounds reasonable? -- 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/1016695 Title: add console=tty0 to cloud-image kernel boot parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1016695/+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 1016695] Re: add console=tty0 to cloud-image kernel boot parameters
** Attachment added: "console=tty1 console=ttyS0" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1016695/+attachment/3212313/+files/serial_output_tty1_ttyS0.txt -- 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/1016695 Title: add console=tty0 to cloud-image kernel boot parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1016695/+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 1016435] Re: remove btrfs recommendation
can at least one of all of you, saying "crashed badly", tell me what you exactly mean? I am looking into using Btrfs for data storage and ideally with Ceph, and I'd like to know what you mean by just the word "crash" and how current this state is :-) -- 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/1016435 Title: remove btrfs recommendation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1016435/+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 727837] Re: dhcp3-server fails to drop privileges properly
** Branch linked: lp:ubuntu/isc-dhcp -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in Ubuntu. https://bugs.launchpad.net/bugs/727837 Title: dhcp3-server fails to drop privileges properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dhcp3/+bug/727837/+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 914160] Re: [MIR] openvswitch
I am re-opening this bug because its needed for quantum ** Changed in: openvswitch (Ubuntu) Status: Won't Fix => Triaged ** Changed in: openvswitch (Ubuntu) Status: Triaged => In Progress ** Changed in: openvswitch (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/914160 Title: [MIR] openvswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/914160/+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-q-openstack-folsom] Openstack Next Steps
Blueprint changed by Chuck Short: Work items changed: Work items: [zulcss] Package nova for folsom: INPROGRESS [zulcss] Package swift for folsom: INPROGRESS [zulcss] Package horizon for folsom: INPROGRESS [zulcss] Package keystone for folsom: INPROGRESS [zulcss] Package glance for folsom: INPROGRESS [zulcss] Package quantum for folsom: INPROGRESS [zulcss] Package python-glanceclient: INPROGRESS - MIR for quantum: TODO + MIR for quantum: INPROGRESS MIR for libguestfs: TODO MIR for python-sendfile: TODO - MIR for openvswitch: TODO + MIR for openvswitch: INPROGRESS Evaluate and package cinder for universe: INPROGRESS Evaluate and package openstackclient for universe: TODO Evaluate and package ceilometer for universe: TODO Evaluate and package openstack-docs for universe: TODO [zulcss] Move nova configuration file to config object model: DONE Review upstart jobs for nova, swift, glance, quantum: TODO Write Hetrogenous scheduler for ARM: DONE Write instance architecture detection: DONE Add ceph support for nova volumes: TODO Add ceph support for glance: TODO Add SSL support fo nova api: TODO [smoser] upstream changes for config drive spec: TODO pull upstream config drive changes to ubuntu: TODO [smoser] upstream changes for public glance spec: TODO pull upstream glance changes for public glance to ubuntu: TODO [utlemming] public glance server / glance.ubuntu.com: TODO glance.ubuntu.com listed by default in packages: TODO -- Openstack Next Steps https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-openstack-folsom -- 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 727837] Re: dhcp3-server fails to drop privileges properly
This bug was fixed in the package isc-dhcp - 4.2.4-1ubuntu1 --- isc-dhcp (4.2.4-1ubuntu1) quantal; urgency=low * Merge from Debian. Remaining changes: (LP: #768171, LP: #841182, LP: #881558, LP: #872929, LP: #616809) - Use upstart jobs for isc-dhcp-server and isc-dhcp-relay. - Add IPv6 support to udeb dhclient-script (forwarded as Debian #635897). - Add an apport hook to isc-dhcp-client and isc-dhcp-server. - Add an apparmor profile to isc-dhcp-client and isc-dhcp-server. - Update default dhclient.conf to ask for IPv6 configuration. - Patches: + dhclient-fix-backoff + dhclient-more-debug + dhclient-onetry-call-clientscript + dhclient-safer-timeout + dhcpd.conf-subnet-examples + multi-ip-addr-per-if + onetry_retry_after_initial_success + revert-next-server * Set fqdn.fqdn to the result of gethostname(); (LP: #991360) * Replace old droppriv and deroot patches by use of --enable-paranoia and matching -user and -group parameters to dhcpd. (LP: #727837) * Allow read access to /etc/dhcp/ddns-keys/* for ddns. (LP: #341817) It's expected that people generate one key per zone and have it stored in both /etc/bind9 and /etc/dhcp/ddns-keys/ for security reason. * Fix apport hook to work with python3. isc-dhcp (4.2.4-1) unstable; urgency=low * New upstream release * debian/control: reformatted Uploaders so that dch doesn't think I'm making NMUs * debian/rules: do a clean between the LDAP-enabled build and the non-LDAP-enabled one, so that no LDAP-related artefacts are accidently incorporated into the non-LDAP build * debian/dhclient-script.*: conditionalise the chown/chmod of the new resolv.conf on the existence of the old one (closes: #595400) * debian/dhclient-script.linux: comply with RFC 3442 and ignore the routers option if the rfc3442-classless-static-routes option is present (closes: #592735) * debian/dhclient-script.kfreebsd: fix subnet mask handling (closes: #677985) isc-dhcp (4.2.2.dfsg.1-5) unstable; urgency=medium [ Andrew Pollock ] * debian/dhclient.conf: send the hostname (closes: #151820) [ Michael Gilbert ] * Fix cve-2011-4868: error in DDNS handling with IPv6 (closes: #655746) * Fix cve-2011-4539: error in regular expression handling (closes: #652259) * Make dependencies diff-able * Add myself to uploaders * Remove all automatically generated files in clean rule * Medium urgency for security updates isc-dhcp (4.2.2.dfsg.1-4) unstable; urgency=low * The "Zoe woke up at 4am and I couldn't get back to sleep so I had some extra time to work on this" release * patch the Makefile for the embedded BIND libraries so that autoconf is run so that the modification to configure.in to fix the FTBFS on kFreeBSD actually does something useful (closes: #643569) isc-dhcp (4.2.2.dfsg.1-3) unstable; urgency=low * debian/control: remove transitional packages * debian/rules: apply the intent of Pierre Chifflier's patch to enable hardening options (closes: #644413) * debian/control: also add inetutils-ping to the dependencies for isc-dhcp-client on hurd (closes: #648140) * Convert to 3.0 (quilt) source format: - debian/control: remove build-dep on dpatch - debian/rules: stop including dpatch.make - debian/rules: remove dpatch-related target dependencies - convert patches from dpatch to pure quilt - remove debian/README.source * debian/rules: cleaned up the target names a bit to reflect the lack of patching going on now * repack bind.tar.gz in upstream source tarball to patch configure.in for FTBFS on kFreeBSD and remove RFCs (closes: #643569, #645760) * debian/watch: add dversionmangle to deal with dfsg upstream tarball * Updated Dutch debconf template translation (closes: #651396) * Added Polish debconf template translation (closes: #659372) * Updated Brazilian Portugeuse debconf template translation (closes: #663494) * debian/control: bumped Standards-Version (no changes) isc-dhcp (4.2.2-2) unstable; urgency=low * debian/rules: use dpkg-buildflags to set CFLAGS, and export CFLAGS (closes: #643470) * debian/dhclient.conf: revert hostname setting behaviour to something equivalent to what upstream ships to avoid surprising people with unwanted hostname changes when changing networks (closes: #648676) * debian/dhclient-script.kfreebsd: apply patch from Robert Millan to resync dhclient-script with FreeBSD version (closes: #645502) * debian/control: add inetutils-ping to the dependencies for isc-dhcp-client on kfreebsd (closes: #648140) * Updated German debconf template translation (closes: #641843) * added harding-wrapper to build dependencies and invoke it in debian/rules (closes: #611192) isc-dhcp (4.2.2-1) unstable; urgency=low * New upstream release, includes security fixes for CVE-2011-2748 and CVE-2011-2749 (closes: #638404)
[Bug 1020166] Re: Patch socat on lucid to address CVE-2010-2799
The sync in bug 613761 fixed this in Maverick and beyond, so there's only Lucid and Hardy to consider. Note that socat is in universe. ** This bug has been flagged as a security vulnerability -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to socat in Ubuntu. https://bugs.launchpad.net/bugs/1020166 Title: Patch socat on lucid to address CVE-2010-2799 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/socat/+bug/1020166/+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-q-openstack-folsom] Openstack Next Steps
Blueprint changed by Chuck Short: Work items changed: Work items: [zulcss] Package nova for folsom: INPROGRESS [zulcss] Package swift for folsom: INPROGRESS [zulcss] Package horizon for folsom: INPROGRESS [zulcss] Package keystone for folsom: INPROGRESS [zulcss] Package glance for folsom: INPROGRESS [zulcss] Package quantum for folsom: INPROGRESS [zulcss] Package python-glanceclient: INPROGRESS MIR for quantum: TODO MIR for libguestfs: TODO MIR for python-sendfile: TODO MIR for openvswitch: TODO Evaluate and package cinder for universe: INPROGRESS Evaluate and package openstackclient for universe: TODO Evaluate and package ceilometer for universe: TODO Evaluate and package openstack-docs for universe: TODO [zulcss] Move nova configuration file to config object model: DONE Review upstart jobs for nova, swift, glance, quantum: TODO - Write Hetrogenous scheduler for ARM: TODO + Write Hetrogenous scheduler for ARM: DONE Write instance architecture detection: DONE Add ceph support for nova volumes: TODO Add ceph support for glance: TODO Add SSL support fo nova api: TODO [smoser] upstream changes for config drive spec: TODO pull upstream config drive changes to ubuntu: TODO [smoser] upstream changes for public glance spec: TODO pull upstream glance changes for public glance to ubuntu: TODO [utlemming] public glance server / glance.ubuntu.com: TODO glance.ubuntu.com listed by default in packages: TODO -- Openstack Next Steps https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-openstack-folsom -- 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 1020152] Re: Broken symlink /usr/lib/libnss_ldap.so in precise
Scrap that. Debian are already on top of it. The patch above would perhaps be suitable as the basis for a Precise SRU. It will also fix the problem in Quantal but a merge from Debian would be more appropriate since they have fixed it already. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in Ubuntu. https://bugs.launchpad.net/bugs/1020152 Title: Broken symlink /usr/lib/libnss_ldap.so in precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1020152/+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 1020152] Re: Broken symlink /usr/lib/libnss_ldap.so in precise
Debdiff for Quantal attached. Sponsors: I assumed that /usr/lib/ is where the symlink needs to be, pointing to /lib//libnss-ldap..., since that's what libc6-dev does with its nss modules also. Since this package is source format 1.0, uses cdbs and I can't depend on dh-exec since that's in universe in Precise (and we may want to SRU), I figured a fix by moving from dh_link to a cdbs override rule in debian/rules would be appropriate. We supplied the original multiarch patch to Debian, so I thought it would be appropriate for us to send a fix to them as well. I will send the fix now. Since they're in freeze, I don't know whether we should wait for them and merge or not? ** Patch added: "libnss-ldap-multiarch-symlink.debdiff" https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1020152/+attachment/3211757/+files/libnss-ldap-multiarch-symlink.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libnss-ldap in Ubuntu. https://bugs.launchpad.net/bugs/1020152 Title: Broken symlink /usr/lib/libnss_ldap.so in precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1020152/+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 925315] Re: [Patch][Precise]Enable LZO support
Both the client and the server should have a version installed which has LZO enabled. Is this the case? If it is, please create a new bug. You can cc me and I will take a look into it. LZO compression works fine for Terabytes of data for me. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/925315 Title: [Patch][Precise]Enable LZO support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/925315/+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 997978] Re: KVM images lose connectivity with bridged network
Christian, You are right, no need to add : in the xml ... modprobe vhost_net should be enough. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/997978/+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 997978] Re: KVM images lose connectivity with bridged network
Christian, I'm not really sure if just enabling vhost_net is enough... you may probably be right : it works well for you since 4 days ... Like I still do not understand where the bug is locate, I prefered to do everything to fix it quickly. Reading the bugzilla : https://bugzilla.kernel.org/show_bug.cgi?id=42829 they were also talking about event_idx='off' It seems to be patched now (I'm not sure basically): http://git.kernel.org/?p=linux/kernel/git/davem/net-next.git;a=commitdiff;h=4b727361f0bc7ee7378298941066d8aa15023ffb;hp=e1ac50f64691de9a095ac5d73cb8ac73d3d17dba Regards, -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/997978/+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 997978] Re: KVM images lose connectivity with bridged network
Stephane, ya, as a workaround (not to say: the better way), modprobe'ing "vhost_net" driver before actually starting the VMs works perfect. no incidents since 4 days now (tested on 30+ VMs). But is your driver-tag for? I did not need to do that, my libvirt-bin added the vhost=on parameter to qemu-kvm automatically - so what do I need this line for then? Regards, Christian. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/997978/+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 997978] Re: KVM images lose connectivity with bridged network
Ok just in cas it may help... It does work modprobing vhost_net and adding : on every nics definitions. Tested on more than 100 VMs. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/997978/+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 1020436] Re: Multiple filesystems cannot read superblock after fibre path failover
** Description changed: This might not be multipath-tools, but it's the likeliest candidate. If fibre channel connectivity is disrupted on an active path, I can see the multipath daemon rejuggling active paths as expected. However instead of utilising a new path, the server continues trying active i/o down the same path until it fails, and the superblock on the lun is marked unreadable. The luns simply cannot be remounted even after the paths are recovered. However, after a simple reboot, the luns are again readable _regardless_ of the visible path. (Eg I shut the active FC port then rebooted, and the storage was mountable per normal over a different path). I've replicated this behaviour using both xfs and ext4 filesystems, on multiple different luns presented to the server. The luns are visible over four FC paths, and the /dev/mapper/mpathX identity is used as the physical volume for an LVM2 volume group, into which the logical volume(s) and filesystem are created. root@:~# lsb_release -rd Description: Ubuntu 10.04.3 LTS Release: 10.04 As you can see here, the /dev/test and /dev/test2 volume groups are both active, yet showing i/o errors after a pathing fail. root@:~# lvscan - /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error - /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error - ACTIVE'/dev/test2/lvol0' [4.00 GiB] inherit - ACTIVE'/dev/test/lvol0' [4.00 GiB] inherit - ACTIVE'/dev/mvsan/san' [500.00 GiB] inherit + /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error + /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error + ACTIVE'/dev/test2/lvol0' [4.00 GiB] inherit + ACTIVE'/dev/test/lvol0' [4.00 GiB] inherit + ACTIVE'/dev/mvsan/san' [500.00 GiB] inherit root@:~# pvscan - /dev/test2/lvol0: read failed after 0 of 4096 at 4290707456: Input/output error - /dev/test2/lvol0: read failed after 0 of 4096 at 4290764800: Input/output error - /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error - /dev/test2/lvol0: read failed after 0 of 4096 at 4096: Input/output error - /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error - /dev/test/lvol0: read failed after 0 of 4096 at 4290707456: Input/output error - /dev/test/lvol0: read failed after 0 of 4096 at 4290764800: Input/output error - /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error - /dev/test/lvol0: read failed after 0 of 4096 at 4096: Input/output error - /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error - PV /dev/mapper/mpath2 VG test2lvm2 [4.00 GiB / 0free] - PV /dev/mapper/mpath1 VG test lvm2 [4.00 GiB / 0free] - PV /dev/mapper/mpath0 VG mvsanlvm2 [500.00 GiB / 0free] + /dev/test2/lvol0: read failed after 0 of 4096 at 4290707456: Input/output error + /dev/test2/lvol0: read failed after 0 of 4096 at 4290764800: Input/output error + /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error + /dev/test2/lvol0: read failed after 0 of 4096 at 4096: Input/output error + /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error + /dev/test/lvol0: read failed after 0 of 4096 at 4290707456: Input/output error + /dev/test/lvol0: read failed after 0 of 4096 at 4290764800: Input/output error + /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error + /dev/test/lvol0: read failed after 0 of 4096 at 4096: Input/output error + /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error + PV /dev/mapper/mpath2 VG test2lvm2 [4.00 GiB / 0free] + PV /dev/mapper/mpath1 VG test lvm2 [4.00 GiB / 0free] + PV /dev/mapper/mpath0 VG mvsanlvm2 [500.00 GiB / 0free] root@:~# multipath -ll - mpath2 (360060e80058a07008a070023) dm-7 HITACHI ,OPEN-V + mpath2 (360060e80058a07008a070023) dm-7 HITACHI ,OPEN-V [size=4.0G][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=4][active] - \_ 6:0:0:2 sdd 8:48 [active][ready] - \_ 6:0:1:2 sdg 8:96 [active][ready] - \_ 7:0:0:2 sdj 8:144 [active][ready] - \_ 7:0:1:2 sdp 8:240 [active][ready] - mpath1 (360060e80058a07008a07000e) dm-6 HITACHI ,OPEN-V + \_ 6:0:0:2 sdd 8:48 [active][ready] + \_ 6:0:1:2 sdg 8:96 [active][ready] + \_ 7:0:0:2 sdj 8:144 [active][ready] + \_ 7:0:1:2 sdp 8:240 [active][ready] + mpath1 (360060e80058a07008a07000e) dm-6 HITACHI ,OPEN-V [size=4.0G][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=4][active] - \_ 6:0:0:1 sdc 8:32 [active][ready] - \_ 6:0:1:1 sdf 8:80 [active][ready] - \_ 7:0:0:1 sdi 8:128 [active][ready] - \_ 7:0:1:1 sdo 8:224 [active][ready] - mpath0 (360060e80058a07008a0724
[Bug 1020436] [NEW] Multiple filesystems cannot read superblock after fibre path failover
Public bug reported: This might not be multipath-tools, but it's the likeliest candidate. If fibre channel connectivity is disrupted on an active path, I can see the multipath daemon rejuggling active paths as expected. However instead of utilising a new path, the server continues trying active i/o down the same path until it fails, and the superblock on the lun is marked unreadable. The luns simply cannot be remounted even after the paths are recovered. However, after a simple reboot, the luns are again readable _regardless_ of the visible path. (Eg I shut the active FC port then rebooted, and the storage was mountable per normal over a different path). I've replicated this behaviour using both xfs and ext4 filesystems, on multiple different luns presented to the server. The luns are visible over four FC paths, and the /dev/mapper/mpathX identity is used as the physical volume for an LVM2 volume group, into which the logical volume(s) and filesystem are created. root@:~# lsb_release -rd Description:Ubuntu 10.04.3 LTS Release:10.04 As you can see here, the /dev/test and /dev/test2 volume groups are both active, yet showing i/o errors after a pathing fail. root@:~# lvscan /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error ACTIVE'/dev/test2/lvol0' [4.00 GiB] inherit ACTIVE'/dev/test/lvol0' [4.00 GiB] inherit ACTIVE'/dev/mvsan/san' [500.00 GiB] inherit root@:~# pvscan /dev/test2/lvol0: read failed after 0 of 4096 at 4290707456: Input/output error /dev/test2/lvol0: read failed after 0 of 4096 at 4290764800: Input/output error /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error /dev/test2/lvol0: read failed after 0 of 4096 at 4096: Input/output error /dev/test2/lvol0: read failed after 0 of 4096 at 0: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 4290707456: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 4290764800: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 4096: Input/output error /dev/test/lvol0: read failed after 0 of 4096 at 0: Input/output error PV /dev/mapper/mpath2 VG test2lvm2 [4.00 GiB / 0free] PV /dev/mapper/mpath1 VG test lvm2 [4.00 GiB / 0free] PV /dev/mapper/mpath0 VG mvsanlvm2 [500.00 GiB / 0free] root@:~# multipath -ll mpath2 (360060e80058a07008a070023) dm-7 HITACHI ,OPEN-V [size=4.0G][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=4][active] \_ 6:0:0:2 sdd 8:48 [active][ready] \_ 6:0:1:2 sdg 8:96 [active][ready] \_ 7:0:0:2 sdj 8:144 [active][ready] \_ 7:0:1:2 sdp 8:240 [active][ready] mpath1 (360060e80058a07008a07000e) dm-6 HITACHI ,OPEN-V [size=4.0G][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=4][active] \_ 6:0:0:1 sdc 8:32 [active][ready] \_ 6:0:1:1 sdf 8:80 [active][ready] \_ 7:0:0:1 sdi 8:128 [active][ready] \_ 7:0:1:1 sdo 8:224 [active][ready] mpath0 (360060e80058a07008a072417) dm-5 HITACHI ,OPEN-V [size=500G][features=1 queue_if_no_path][hwhandler=0] \_ round-robin 0 [prio=4][active] \_ 6:0:0:0 sdb 8:16 [active][ready] \_ 6:0:1:0 sde 8:64 [active][ready] \_ 7:0:0:0 sdh 8:112 [active][ready] \_ 7:0:1:0 sdk 8:160 [active][ready] The dmesg output is very instructive, but still doesn't help with the root cause per se. I set the scsi-timeouts nice and high (90 seconds) to accommodate any potential delays in path failover. The path checks (test unit ready/TUR) occur about every 20 seconds. See below: [ 2192.891962] qla2xxx :24:00.0: LOOP DOWN detected (2 3 0). [ .820850] rport-7:0-0: blocked FC remote port time out: removing target and saving binding [ .821297] rport-7:0-1: blocked FC remote port time out: removing target and saving binding [ .827286] device-mapper: multipath: Failing path 8:112. [ .827369] device-mapper: multipath: Failing path 8:160. So this is all as expected. Then: [ .924665] sd 7:0:0:0: [sdh] Synchronizing SCSI cache [ .924696] sd 7:0:0:0: [sdh] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ .926071] device-mapper: multipath: Failing path 8:160. [ .976444] sd 7:0:1:2: [sdm] Unhandled error code [ .976446] sd 7:0:1:2: [sdm] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ .976449] sd 7:0:1:2: [sdm] CDB: Read(10): 28 00 00 7f e1 00 00 00 01 00 [ .976455] end_request: I/O error, dev sdm, sector 8380672 [ .980258] sd 7:0:1:2: [sdm] Unhandled error code [ .980260] sd 7:0:1:2: [sdm] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [ .980262] sd 7:0:1:2: [sdm] CDB: Read(10): 28 00 00 7f e1 70 00 00 01 00 [ .980267] end_request: I/O error, dev sdm, sector 8380784 [ .984139] sd 7:0:1:2: [sdm] Unhandled error code [
[Bug 988043] Re: nmap has no debian/watch file
** Changed in: nmap (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nmap in Ubuntu. https://bugs.launchpad.net/bugs/988043 Title: nmap has no debian/watch file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nmap/+bug/988043/+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