[Bug 1486696] [NEW] lxc-create -B btrfs fails if lxc.lxcpath is not on the same filesystem as /var/cache/lxc (not a configurable option)
Public bug reported: ## Version Description:Ubuntu 15.04 Release:15.04 lxc: Installed: 1.1.2-0ubuntu3.1 Candidate: 1.1.2-0ubuntu3.1 Version table: *** 1.1.2-0ubuntu3.1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 1.1.2-0ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages ## Config changes from default cat /etc/lxc/lxc.conf lxc.lxcpath = /srv/vservers/lxc ## Mount details /var/cache/lxc in on root filesystem /srv/vservers/lxc is a btrfs mount point ## Command used (sample) sudo lxc-create -B btrfs --name test-bt -t ubuntu -- -r trusty ## Error (sample) Copy /var/cache/lxc/trusty/rootfs-amd64 to /srv/vservers/lxc/test-bt/rootfs ... Copying rootfs to /srv/vservers/lxc/test-bt/rootfs ... Transaction commit: none (default) Delete subvolume '/srv/vservers/lxc/test-bt/rootfs' Create a snapshot of '/var/cache/lxc/trusty/rootfs-amd64' in '/srv/vservers/lxc/test-bt/rootfs' ERROR: cannot snapshot '/var/cache/lxc/trusty/rootfs-amd64' - Invalid cross-device link lxc_container: lxccontainer.c: create_run_template: 1108 container creation template for test-bt failed lxc_container: lxccontainer.c: container_destroy: 2056 Error destroying rootfs for test-bt lxc_container: lxc_create.c: main: 274 Error creating container test-bt ## Thoughts Maybe this is the expected behavior, if so a Documentation update stating something to the effect of If you change the lxcpath to a different filesystem than the one where /var/cache/lxc livs you cannot create a btrfs backed container. -or- Let /var/cache/lxc be configured via lxc.conf and have the documentation note that they should reside on the same filesystem. ** Affects: lxc (Ubuntu) Importance: Undecided Status: 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/1486696 Title: lxc-create -B btrfs fails if lxc.lxcpath is not on the same filesystem as /var/cache/lxc (not a configurable option) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1486696/+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 1394759] [NEW] https health checks by ldirectord fail
Public bug reported: Package: ldirectord Description:Ubuntu 14.04.1 LTS Release:14.04 See debian bug 770349. https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=770349 For https health checks to succeed, the verify_hostname option for LWP must be disabled. If an IP address is used for the real server (which as far as I know is recommended), the hostname in the request will not match the name in the SSL certificate. Newer LWP versions will check that these match unless they are told not to. The upstream fix was committed here: https://github.com/mcnewton/resource- agents/commit/68fad38326b7c04efd6434e736e32fe395eafe02 I am awaiting another maintenance window before I can verify that this patch fixes the problem I encountered. ** Affects: resource-agents (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to resource-agents in Ubuntu. https://bugs.launchpad.net/bugs/1394759 Title: https health checks by ldirectord fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1394759/+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 1394759] Re: https health checks by ldirectord fail
I have verified in a lab environment that the patch fixes the I encountered when trying to replace a CentOS 5 load balancer with one running Ubuntu 14. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to resource-agents in Ubuntu. https://bugs.launchpad.net/bugs/1394759 Title: https health checks by ldirectord fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1394759/+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 1315791] [NEW] package bridge-utils 1.4-5ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: This was from the CAE Linux live CD ProblemType: Package DistroRelease: Ubuntu 10.04 Package: bridge-utils 1.4-5ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-34.77-generic 2.6.32.44+drm33.19 Uname: Linux 2.6.32-34-generic x86_64 Architecture: amd64 Date: Sat May 3 23:31:21 2014 ErrorMessage: subprocess installed post-installation script returned error exit status 1 LiveMediaBuild: CAELinux2011 - Release amd64 SourcePackage: bridge-utils Title: package bridge-utils 1.4-5ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ** Affects: bridge-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lucid -- 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/1315791 Title: package bridge-utils 1.4-5ubuntu2 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/bridge-utils/+bug/1315791/+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 1026621] Re: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances
Michael, Thank you for taking a look at this and creating the new bug for changing the way libvirt virtualizes the hardware clock for Windows vs. Linux. I believe this to be the root cause for the bug defined here because of the way Windows handles DHCP renewals. ===DHCP=== As for DHCP, I am not sure anything is wrong with having a very short DHCP lease time of 120 sec as the default for nova. I was more curious what the reasoning behind this was. My understanding is that the DNSMasq default is 12 hours. I found this message also asking about the nova default - https://lists.launchpad.net/openstack/msg24200.html I also wanted to say that the DHCP lease time of 120 seconds does not really exacerbate the issue as I stated above. What is does is make the issue present faster. ==Windows DHCP lease renewal behavior=== This is my understanding of why we are seeing a lose of IP address for Windows 2008R2 (my reproducible issue) 1. Windows instance boots up on KVM with the hardware clock set to UTC (expects localtime) 2. The instance gets it's DHCP lease. (2 min) it logs the obtained time and expire time for the lease Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : novalocal Description . . . . . . . . . . . : Red Hat VirtIO Ethernet Adapter Physical Address. . . . . . . . . : FA-16-3E-23-D2-8E DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::d420:7346:d258:ffa2%11(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.200.25(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Thursday, September 26, 2013 5:17:06 PM Lease Expires . . . . . . . . . . : Thursday, September 26, 2013 5:47:06 PM Default Gateway . . . . . . . . . : 192.168.200.1 DHCP Server . . . . . . . . . . . : 192.168.200.1 DHCPv6 IAID . . . . . . . . . . . : 251270718 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-D6-86-9A-FA-16-3E-23-D2-8E DNS Servers . . . . . . . . . . . : 192.168.200.1 NetBIOS over Tcpip. . . . . . . . : Enabled 3. NTP time sync happens, in my timezone PST (windows default), this sets the instance clock back 7 hours and updates the DHCP lease information as follows Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : novalocal Description . . . . . . . . . . . : Red Hat VirtIO Ethernet Adapter Physical Address. . . . . . . . . : FA-16-3E-23-D2-8E DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::d420:7346:d258:ffa2%11(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.200.25(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Monday, August 20, 1877 10:48:50 AM Lease Expires . . . . . . . . . . : Thursday, September 26, 2013 10:47:09 AM Default Gateway . . . . . . . . . : 192.168.200.1 DHCP Server . . . . . . . . . . . : 192.168.200.1 DHCPv6 IAID . . . . . . . . . . . : 251270718 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-D6-86-9A-FA-16-3E-23-D2-8E DNS Servers . . . . . . . . . . . : 192.168.200.1 NetBIOS over Tcpip. . . . . . . . : Enabled 4. Windows now thinks it's DHCP lease obtained time is in the future and resets the obtained time to some time way in the past (year 1877) but adjusts the expire time to be the same amount of time from current time as it was before the NTP update. In the above example 30 min. 5. When the DHCP expire time is reached Windows releases the IP address and does not try and do a DHCP renewal. From what I can tell this has been in issue in Windows for a very long time and and has not been addressed. In a hardware case this would be a one time problem until the time is updated and a manual DCHP renewal is done. But for unattended virtual machines the issue is much more of a problem. As the above message states Michael has created a new bug for the Widows issue and has already coded a fix! -- 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/1026621 Title: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1026621/+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 1026621] Re: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances
===DHCP=== While I do agree that It would make sense to ping an IP before its lease is deleted as a extra safety measure. This would not have help this specific Windows issue as the IP is released by the instance. -- 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/1026621 Title: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1026621/+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 1026621] Re: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances
Hey Jay, Funny you posted this. I was about to post the same. after a bunch of testing and comparing how CLoudStack deals with the Hardware Clock for Windows with how Openstack is configured by default we also noticed that the Nova VM template uses a hardware clock with a UTC offset. This is a standard for Linux but not for Windows. The reg key you listed does allow Windows to deal with a UTC offset hardware clock. In my looking into this I do see that this change is not without issue, as some things will not work correctly. But for the most part on server OS I think it should be fine. CloudStack manages this issue by having a OS_Type for each image and for images that are windows it local time rather that the UTC offset for the hardware clock. This then does not require an image side change for Windows images. Currently we do not see an easy way to implement the same kind of solution as the best we can do is set advanced metadata properties on an image in glance, but then having Nova key off this and use a Windows specific template would require some additional work. I think another aspect of this is that the DHCP leases are set for 120 seconds on OpenStack by default. I think this exacerbates the issue because the lease time is shorter that the time offset. Does anyone know why the DHCP lease times are so short for OpenStack? CloudStack configures the leases to not expire which would also make this issue not happen. -- 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/1026621 Title: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1026621/+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 1015207] Re: juju setup fails, ERROR Invalid SSH key - 12.04 LTS
I think Ondrej is on to something I had problems earlier attaching nodes to maas by trying to read between the lines on the instructions instead of doing literal. One problem on my setup of nodes is i didnt set pxe as first boot order instead just left the default. So it would pxe boot the initial install but not commission gracefully. Further on at the juju step i too manually powered the unit on as well as still not using pxe as first boot order. I think maybe the bug is on documentation not telling us what we shouldnt be doing correcting us from thinking we know what we are doing. It just seems like its a id10t error on my part by not doing a step right or more likely over complicating something. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1015207 Title: juju setup fails, ERROR Invalid SSH key - 12.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1015207/+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 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
should I capture packets for the broken samba or the one from your ppa that works. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
your samba from your ppa works well without crashing -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 185729] Re: nautilus is unable to copy folders from samba
it's working on hardy for me now too. thanks everyone. -- nautilus is unable to copy folders from samba https://bugs.launchpad.net/bugs/185729 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 185729] Re: nautilus is unable to copy folders from samba
hey I test tested this out with ubuntu intrepid ibex 8.10 alpha2 and copying folders with samba works. also why is bug marked as incomplete. -- nautilus is unable to copy folders from samba https://bugs.launchpad.net/bugs/185729 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 185729] Re: nautilus is unable to copy folders from samba
the directory name is pic. those weird asian letters show up by themselves. also there is no way to set the domain name on this nas. ** Attachment added: screen shot of nas setup http://launchpadlibrarian.net/14069788/Screenshot-Net%20Disk%20Setup%20-%20Mozilla%20Firefox%203%20Beta%205.png -- nautilus is unable to copy folders from samba https://bugs.launchpad.net/bugs/185729 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 185729] Re: nautilus is unable to copy folders from samba
tried it a couple different ways here is the output: [EMAIL PROTECTED]:~$ smbclient //STORAGE/public -N -c 'recurse; mget pic/'Domain=[ȇ] OS=[] Server=[���] ERRDOS - ERRbadfile (File not found.) listing \pic/ [EMAIL PROTECTED]:~$ smbclient //STORAGE/public/ -N -c 'recurse; mget pic' Domain=[ȇ] OS=[] Server=[���] Get file 椀挀? y ERRDOS - ERRbadfile (File not found.) opening remote file \椀挀 -- nautilus is unable to copy folders from samba https://bugs.launchpad.net/bugs/185729 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
