[Bug 1306537] Re: LXC local provider fails to provision precise instances from a trusty host
For people still having trouble with this, you may want to look at http://askubuntu.com/questions/486542/upload-all-release-versions-of- tools-with-jujus-local-lxc-provider to see if it helps. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-quickstart in Ubuntu. https://bugs.launchpad.net/bugs/1306537 Title: LXC local provider fails to provision precise instances from a trusty host To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1306537/+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 1316017] Re: openssh client ignores -o Tunnel=ethernet option, creating an IP tunnel device instead of an ethernet tap device
** Tags added: regression-release -- 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/1316017 Title: openssh client ignores -o Tunnel=ethernet option, creating an IP tunnel device instead of an ethernet tap device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1316017/+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 1316017] [NEW] openssh client ignores -o Tunnel=ethernet option, creating an IP tunnel device instead of an ethernet tap device
Public bug reported: This is a regression from the version of the client in 14.04 compared to 13.10. I'm connecting to 12.04.4 for a server. Expected behaviour: Creating a connection with the option "-o Tunnel=ethernet" will create a layer2 ethernet tap device. Actual behaviour: New client creates a layer3 IP tunnel. The old version of the client that works properly (installed manually on 14.04): OpenSSH_6.2p2 Ubuntu-6ubuntu0.3, OpenSSL 1.0.1f 6 Jan 2014 The new version of the client that does not work properly: OpenSSH_6.6p1 Ubuntu-2ubuntu1, OpenSSL 1.0.1f 6 Jan 2014 The version of the SSH server I'm connecting to: openssh-server: Installed: 1:5.9p1-5ubuntu1.3 Candidate: 1:5.9p1-5ubuntu1.3 Version table: *** 1:5.9p1-5ubuntu1.3 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status 1:5.9p1-5ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages # Terminal output with the old version: ssh -p 38613 @ -w any -o Tunnel=ethernet -vvv OpenSSH_6.2p2 Ubuntu-6ubuntu0.3, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: auto-mux: Trying existing master debug1: Control socket "" does not exist debug2: ssh_connect: needpriv 0 debug1: Connecting to [] port 38613. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug3: Incorrect RSA1 identifier debug3: Could not load "/root/.ssh/id_rsa" as a RSA1 public key debug1: identity file /root/.ssh/id_rsa type 1 debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-16384 debug1: Checking blacklist file /etc/ssh/blacklist.RSA-16384 debug1: identity file /root/.ssh/id_rsa-cert type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: identity file /root/.ssh/id_dsa-cert type -1 debug3: Incorrect RSA1 identifier debug3: Could not load "/root/.ssh/id_ecdsa" as a RSA1 public key debug1: identity file /root/.ssh/id_ecdsa type 3 debug1: Checking blacklist file /usr/share/ssh/blacklist.ECDSA-521 debug1: Checking blacklist file /etc/ssh/blacklist.ECDSA-521 debug1: identity file /root/.ssh/id_ecdsa-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.2p2 Ubuntu-6ubuntu0.3 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1 Debian-5ubuntu1.3 debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1.3 pat OpenSSH_5* debug2: fd 3 setting O_NONBLOCK debug3: put_host_port: []:38613 debug3: load_hostkeys: loading entries for host "[]:38613" from file "/root/.ssh/known_hosts" debug3: load_hostkeys: found key type ECDSA in file /root/.ssh/known_hosts:24 debug3: load_hostkeys: loaded 1 keys debug3: order_hostkeyalgs: prefer hostkeyalgs: ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-rsa-cert-...@openssh.com,ssh-dss-cert-...@openssh.com,ssh-rsa-cert-...@openssh.com,ssh-dss-cert-...@openssh.com,ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-...@openssh.com,aes256-...@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se debug2: kex_parse_kexinit: hmac-md5-...@openssh.com,hmac-sha1-...@openssh.com,umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-ripemd160-...@openssh.com,hmac-sha1-96-...@openssh.com,hmac-md5-96-...@openssh.com,hmac-md5,hmac-sha1,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5-...@openssh.com,hmac-sha1-...@openssh.com,umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-ripemd160-...@openssh.com,hmac-sha1-96-...@openssh.com,hmac-md5-96-...@openssh.com,hmac-md5,hmac-sha1,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac
[Bug 1225695] Re: Node DNS does not stay updated
So far I haven't seen this come up again. I've had a lot more sucess having the various KVM machines managed by libvirt this time, and following http://askubuntu.com/questions/292061 /how-to-configure-maas-to-be-able-to-boot-virtual-machines so that MaaS can boot the machines at the right time. I wonder if me guessing when a machine needs to be started (and running the KVM command on the host running all these VM's) was sending extra DHCP requests and somehow throwing stuff off? If that is what was happening, I'm not sure if that is a bug or not (depends on if you want the MaaS system able to handle people walking through their datacenter and pressing the power button on some server that is off. I could see MaaS serving an image with instructions that basically say "go back to sleep"). I'm also using the 13.10 version for my MaaS controller, maybe that is what "fixed" it (so for, I hope, crossing fingers). I think I'll set this to incomplete for now since I don't know if this still happens. If it does happen again, I'll just set it back to new. ** Changed in: maas (Ubuntu) Status: New => Incomplete -- 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/1225695 Title: Node DNS does not stay updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1225695/+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 1225695] Re: Node DNS does not stay updated
I'm having it do it again. A restart did not fix it. I've tried using dig against the maas-dns comptuer's ip as the DNS server, and still get the wrong answer. ** Changed in: maas (Ubuntu) Status: Incomplete => 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/1225695 Title: Node DNS does not stay updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1225695/+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 1225695] Re: Node DNS does not stay updated
I think I got this going. I'm not sure what exactly fixed it. I rebooted the MaaS server (region controller and cluster controller in this case) and also changed the nameserver I was using so I wasn't asking an external server that couldn't reach the private IP of the MaaS DNS server to do recursive lookups for me (which would obviously fail). As you can see in the previous comment to this one, I looked up the DNS and it was wrong, but I was using the internal MaaS DNS server. So, maybe restarting did it? ** Changed in: maas (Ubuntu) Status: New => Incomplete -- 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/1225695 Title: Node DNS does not stay updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1225695/+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 1225695] Re: Node DNS does not stay updated
Oops, forgot to include a copy of what I was talking about in the last comment: erik@juju:~$ ssh ubuntu@192.168.10.161 The authenticity of host '192.168.10.161 (192.168.10.161)' can't be established. ECDSA key fingerprint is 4d:8e:fc:7b:1a:84:30:d3:e0:c7:ae:c5:a1:94:9b:e4. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.10.161' (ECDSA) to the list of known hosts. Welcome to Ubuntu 12.04.3 LTS (GNU/Linux 3.2.0-53-generic x86_64) * Documentation: https://help.ubuntu.com/ System information as of Sun Sep 15 11:32:54 EDT 2013 System load: 0.03 Processes: 69 Usage of /: 15.5% of 9.35GB Users logged in: 0 Memory usage: 22% IP address for eth0: 192.168.10.161 Swap usage: 2% Graph this data and manage this system at https://landscape.canonical.com/ Last login: Sun Sep 15 02:02:44 2013 from 192-168-10-115.vcluster.erikbandersen.com ubuntu@hjkdc:~$ logout Connection to 192.168.10.161 closed. erik@juju:~$ dig hjkdc.vcluster.erikbandersen.com a ; <<>> DiG 9.8.1-P1 <<>> hjkdc.vcluster.erikbandersen.com a ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41609 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 1 ;; QUESTION SECTION: ;hjkdc.vcluster.erikbandersen.com. IN A ;; ANSWER SECTION: hjkdc.vcluster.erikbandersen.com. 300 IN CNAME 192-168-10-162.vcluster.erikbandersen.com. 192-168-10-162.vcluster.erikbandersen.com. 300 IN A 192.168.10.162 ;; AUTHORITY SECTION: vcluster.erikbandersen.com. 300 IN NS vcluster.erikbandersen.com. ;; ADDITIONAL SECTION: vcluster.erikbandersen.com. 300 IN A 192.168.10.41 ;; Query time: 4 msec ;; SERVER: 192.168.10.41#53(192.168.10.41) ;; WHEN: Sun Sep 15 08:33:19 2013 ;; MSG SIZE rcvd: 125 -- 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/1225695 Title: Node DNS does not stay updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1225695/+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 1225695] Re: Node DNS does not stay updated
Ok, here's a better example. Since this is virtualized, I was able to do a packet capture on the "Nic" (tap device) of the machine I wanted to get into. I identified the IP that way, and then from there was able to login with an ssh key that I had earlier put into the MaaS Gui. -- 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/1225695 Title: Node DNS does not stay updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1225695/+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 1225695] Re: Node DNS does not stay updated
I ran this: # ps aux | grep dhcp dhcpd10556 0.0 0.1 19128 1100 ?Ss Sep14 0:02 /usr/sbin/dhcpd -f -q -4 -pf /run/maas/dhcp/dhcpd.pid -cf /etc/maas/dhcpd.conf -lf /var/lib/maas/dhcp/dhcpd.leases eth0 So, I'm going to attach the leases file. Maybe that will help. ** Attachment added: "dhcpd.leases" https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1225695/+attachment/3822185/+files/dhcpd.leases -- 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/1225695 Title: Node DNS does not stay updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1225695/+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 1225695] Re: Node DNS does not stay updated
** Attachment added: "var_log_maas.tar.gz" https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1225695/+attachment/3822194/+files/var_log_maas.tar.gz -- 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/1225695 Title: Node DNS does not stay updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1225695/+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 1225695] Re: Node DNS does not stay updated
Here's an example of what I'm seeing: dig hjkdc.vcluster.erikbandersen.com a ; <<>> DiG 9.8.1-P1 <<>> hjkdc.vcluster.erikbandersen.com a ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46503 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 1 ;; QUESTION SECTION: ;hjkdc.vcluster.erikbandersen.com. IN A ;; ANSWER SECTION: hjkdc.vcluster.erikbandersen.com. 300 IN CNAME 192-168-10-162.vcluster.erikbandersen.com. 192-168-10-162.vcluster.erikbandersen.com. 300 IN A 192.168.10.162 ;; AUTHORITY SECTION: vcluster.erikbandersen.com. 300 IN NS vcluster.erikbandersen.com. ;; ADDITIONAL SECTION: vcluster.erikbandersen.com. 300 IN A 192.168.10.41 ;; Query time: 0 msec ;; SERVER: 192.168.10.41#53(192.168.10.41) ;; WHEN: Sun Sep 15 08:06:31 2013 ;; MSG SIZE rcvd: 125 erik@juju:~$ ping 192.168.10.162 PING 192.168.10.162 (192.168.10.162) 56(84) bytes of data. >From 192.168.10.115 icmp_seq=1 Destination Host Unreachable >From 192.168.10.115 icmp_seq=2 Destination Host Unreachable >From 192.168.10.115 icmp_seq=3 Destination Host Unreachable ^C --- 192.168.10.162 ping statistics --- 5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 4024ms pipe 3 ** Attachment added: "zone.master" https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1225695/+attachment/3822191/+files/zone.master -- 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/1225695 Title: Node DNS does not stay updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1225695/+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 1225695] Re: Node DNS does not stay updated
** Attachment added: "zone.vcluster.erikbandersen.com" https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1225695/+attachment/3822195/+files/zone.vcluster.erikbandersen.com -- 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/1225695 Title: Node DNS does not stay updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1225695/+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 1225695] [NEW] Node DNS does not stay updated
Public bug reported: I'm using Ubuntu server 12.04 for my Region controller and cluster controller, which is on the same machine. I have been able to provision a few machines shortly after enrolling them. However, I am later unable to login to the machines using the DNS name. If I can find the machine's IP (say by nmap ping scan and some guessing) it appears to still be there. I've tried tailing the logs in /var/log/maas/ but can't see anything that looks wrong. I'm not exactly sure where to start to try to get more information, so just let me know any information that would be helpful. These machines are running on KVM with a tap device bridged/switched between them. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: maas-dns 1.2+bzr1373+dfsg-0ubuntu1~12.04.1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Sun Sep 15 07:46:06 2013 InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- 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/1225695 Title: Node DNS does not stay updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1225695/+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
