[Bug 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
Unfortunately, no, that doesn't seem to work either. I managed to compile qemu-kvm-1.0+noroms (required a few minor changes, linking with librt and a documentation difference) and the supporting bios and pxe files on Trusty. Migration now seems to work (Completed 100 %), but then the target libvirt spews out a kvm: Features 0x10d4 unsupported. Allowed features: 0x71000454 and the guest machine becomes non responsive (feels like a disk issue) - a hard shutdown (aka destroy) - on the target - is required, which makes the whole live migration effort a bit silly :-S -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+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 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
Ok, I understand. Please note that this was also an issue for 10.04 - 12.04, so it's definitely a good idea to have it fixed for future upgrades (aka trusty specific machine type). I'm not sure about the extra qemu. The next action after migration would be to install the real qemu, right? After which I should stop-start (as opposed to re-start!) all VM's to make sure they're under a trusty-compatible qemu? Or an I missing something here? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+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 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
Otoh, now we're facing a non-migrateable 12.04 in general, because you cannot move your VMs out of the way :-( Anyway, proper documentation is helpful in any case. Finally: there is no real workaround now, or is there? What would you do, having several 12.04 host machines? Just migrate everything with the VM's running? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+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 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
Hi, Adding qemu:commandline tags needs a namespace. What you do is: 12.04~# virsh edit machine Now add the namespace. The resulting first line of the domain xml-file should read: domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0' After that, adding qemu:commandline tags will work, but alas: # virsh start fhdhvalentijn error: Failed to start domain fhdhvalentijn error: internal error Process exited while reading console log output: char device redirected to /dev/pts/12 kvm: Property 'cirrus-vga.vgamem_mb' not found So 12.04 doesn't have the option. I even tried to trick the system into thinking it did have a cirrus-vga.vgamem_mb thing, by 1) leaving the option out; 2) starting fhdhvalentijn 3) virsh edit fhdhvalentijn and adding the cirrus-option; then migrating the thing, but that doesn't work either. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+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 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
Please note my comment #5: removing the vga adapter showed up a new mismatch, this time for the virtio network adapter. I did not look into that but you might want to check if there's more memory mismatches that should be addressed before you start adding code. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+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 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
Hi, is there anything I can do to help this bug's status? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+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 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
When you add a machine with virt-manager, the display setting is model type='cirrus' vram='9216' heads='1'/. I tried to set it to 10240 (which is 10mb) but that didn't help - the error is the same. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+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 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
BTW, that last test was with the regular qemu-kvm in trusty, which is 1.7.0+dfsg-3ubuntu6. I upgraded to the ppa-version again and ... it seems to do something. BRB. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+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 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
error: Unable to read from monitor: Connection reset by peer and the machine crashed :-( Next try, same as always: Length mismatch: vga.vram: 100 in != 80 That's a weird side effect, sometimes not only migration fails, but the machine on the source host crashes, too. Did you reproduce that as well? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+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 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
Hi, Installed qemu-common qemu-keymaps qemu-kvm qemu-system-common qemu-system-x86 qemu-utils from the ppa, same error: source (12.04): # error: operation failed: migration job: unexpectedly failed Log file on target (14.04, log_level = 1) says: 2014-03-13 07:03:56.550+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/kvm -name fhdhvalentijn -S -machine pc-1.0,accel=kvm,usb=off -m 2048 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid f46f2877-62b2-5c2c-0b76-f62e6773dbff -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/fhdhvalentijn.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -kernel /tmp/migrate/vmlinuz-2.6.32-53-generic -initrd /tmp/migrate/initrd.img-2.6.32-53-generic -append root=/dev/vda ro -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/mapper/OpenOffice-filmhuisrestorevalentijn,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=25 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:b3:d1:57,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:0 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -incoming tcp:[::]:49152 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 char device redirected to /dev/pts/1 (label charserial0) Length mismatch: vga.vram: 100 in != 80 qemu: warning: error while loading state for instance 0x0 of device 'ram' load of migration failed 2014-03-13 07:03:56.922+: shutting down -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+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 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
The 100 comes from vga.h in the source for qemu-kvm-1.0+noroms: #define VGA_RAM_SIZE (16 * 1024 * 1024) I could not find the 80 value - as far as I can see, vga ram size is not fixed anymore in the qemu-1.7.0+dfsg source - but I did not fully understand the code. Anyway, I tried something new and removed the video device from the machine. Now a new error pops up: Length mismatch: :00:03.0/virtio-net-pci.rom: 1 in != 2 Anything else I can check? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+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 1291321] [NEW] migration fails between 12.04 Precise and 14.04 Trusty
Public bug reported: We're trying to live migrate machine fhdhvalentijn to a server named ranja. This used to work perfectly when both systems ran 12.04 Precise. After upgrading the target machine (ranja) to Trusty, migration fails; sometimes, migration results in shutting down the VM. Command: virsh migrate --live --copy-storage-all --verbose vhdhvalentijn qemu+ssh://ranja/system Expected: live migration Result: error: operation failed: migration job: unexpectedly failed Logfile on server Ranja says: Length mismatch: vga.vram: 100 in != 80 qemu: warning: error while loading state for instance 0x0 of device 'ram' load of migration failed 2014-03-12 11:05:30.325+: shutting down Logfile on server Duikboot (the host) sometimes suddenly says: 2014-03-12 11:18:25.645+: shutting down and then the VM is no longer running. I also tried to start the migration from 14.04 (virsh -c qemu+ssh://duikboot/system migrate --live --copy-storage-all ...), and also tried to leave out --live (and tried various options like migrating with virt-manager). Also tried to migrate a virgin machine (i.e. a newly created machine with default options) - to no avail. I did not try to migrate directly with qemu - as I have no experience with that. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+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 1291321] Re: migration fails between 12.04 Precise and 14.04 Trusty
Yes, that's possible. Should I install the ppa on source, target or both? V. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1291321 Title: migration fails between 12.04 Precise and 14.04 Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1291321/+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 350936] Re: Should shut down domains on system shutdown
Hmm. If libvirt shuts down the virtual machines it monitors, then these virtual machines will also be shut down when updating libvirt. -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm 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 350936] Re: Should shut down domains on system shutdown
The proposals in this report (mine, John Morrissey's) all have a pre- stop shutdown of virtual machines in their Upstart conf-file. When you update libvirt-bin, dpkg will stop libvirt-bin before upgrading. As a result — if you have implemented the pre-stop shutdown — your virtual machines will all stop. -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm 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 350936] Re: Should shut down domains on system shutdown
While there's many solutions now to shutdown VM's, here's my 2 cents. Instead of a libvirt-bin.conf script, I made a separate script (/usr/local/sbin/shutdown-libvirt-hosts.sh). This script waits 120 seconds for all VM's to shut down. Then I'm running this script from two places; in libvirt-bin.conf: pre-stop script /usr/local/sbin/shutdown-libvirt-hosts.sh end script And also (as a link) from /etc/rc0.d/K10shutdown-libvirt-hosts (and from rc6.d alike) This way, the sendsigs script will only run if all VMs have terminated.?field.comment=While there's many solutions now to shutdown VM's, here's my 2 cents. Instead of a libvirt-bin.conf script, I made a separate script (/usr/local/sbin/shutdown-libvirt-hosts.sh). This script waits 120 seconds for all VM's to shut down. Then I'm running this script from two places; in libvirt-bin.conf: pre-stop script /usr/local/sbin/shutdown-libvirt-hosts.sh end script And also (as a link) from /etc/rc0.d/K10shutdown-libvirt-hosts (and from rc6.d alike) With a K10shutdown-libvirt-hosts script in place, the sendsigs script will only run after this script has ended, which is when all VMs have terminated. A few remarks: - shutting down the VM's twice is not a problem; to the VM, it just looks like pressing the power button twice. - to gracefully shut down, the VM's need the acpid package installed. - if the shutdown script searches for the word running (like mine does, but John Morrissey's script is affected, too), it must set LANG=C at the top, otherwise virsh will run in the local language. ** Attachment added: shutdown-libvirt-hosts.sh https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/350936/+attachment/1621772/+files/shutdown-libvirt-hosts.sh -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 350936] Re: Should shut down domains on system shutdown
libvirt-bin gets shutdown by Upstart, so when you try to shutdown from an init script, chances are that libvirt has shutdown already. So if you want to do this, you need to change /etc/init/libvirt-bin.conf as well, and have it wait for the VM's to shut down. -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 350936] Re: Should shut down domains on system shutdown
I'm still not sure, but doesn't the /etc/init.d/sendsigs script, combined with the Ubuntu 10.04 /etc/init/rc.conf, make up for a giant race condition? Where a shell script tries to find out which processes it should not kill? This is, at least, what I'm making of it, when running libvirt on a server that has no other services running (i.e. the sendsigs script is run almost right away). -- Should shut down domains on system shutdown https://bugs.launchpad.net/bugs/350936 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt 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 537978] Re: Lucid dhclient can't set hostname
The live-CD has an /etc/hostname set to ubuntu, so what do you want me to check? Apart from that, the /sbin/dhclient-script file is the same as above, so the logic to change the hostname does not work and is not conforming to the dhclient-documentation. -- Lucid dhclient can't set hostname https://bugs.launchpad.net/bugs/537978 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 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 523188] Re: Make it possible again to let dhcp server set the client hostname
Isn't this a duplicate for bug #482313? -- Make it possible again to let dhcp server set the client hostname https://bugs.launchpad.net/bugs/523188 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 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 523188] Re: Make it possible again to let dhcp server set the client hostname
We are perfectly able to set hostnames in Karmic; however, we have /etc/hostname explicitly set to '(none)', while (as far as I see in other reports), since Karmic, when /etc/hostname is missing, Ubuntu sets it to localhost, thus making dhclient not set the hostname. -- Make it possible again to let dhcp server set the client hostname https://bugs.launchpad.net/bugs/523188 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 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 482313] Re: dhclient-script ignores option host-name from DHCP-server
We have set /etc/hostname explicitly to '(none)'. Naturally, this is an illegal hostname, but since we use dhcp for our hostnames, the hostname is changed once the network is up. -- dhclient-script ignores option host-name from DHCP-server https://bugs.launchpad.net/bugs/482313 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 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 523188] Re: Make it possible again to let dhcp server set the client hostname
In Lucid, this is not fixed but it is in fact worse, see bug #537978 -- Make it possible again to let dhcp server set the client hostname https://bugs.launchpad.net/bugs/523188 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 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 537978] [NEW] Lucid dhclient can't set hostname
Public bug reported:
Until recently (up to and including Karmic), there was a set_hostname()
function in /sbin/dhclient-script, that said:
set_hostname() {
local current_hostname=$(hostname)
if [ -z $current_hostname -o $current_hostname = (none) ]; then
hostname $new_host_name
fi
}
Up to 9.04, this would work when there was no /etc/hostname. With 9.10
(Karmic), this changed: a missing /etc/hostname sets the hostname to
localhost and the dhclient-script will no longer set the hostname:
this bug is reported as bug #482313 and bug #523188 - see bug #482313
for the fix we have been using for years.
Now with Lucid, the whole thing goes wrong, as the set_hostname() function is
missing. There's only:
BOUND|RENEW|REBIND|REBOOT)
if [ -n $old_host_name -a -n $host_name -a \
$host_name != $old_host_name ]; then
hostname $new_host_name
fi
This is plain wrong for two reasons:
1) as far as I can see, the $host_name variable does not exist at all; there's
only an old_host_name and a new_host_name, but host_name does not exist -
which means the test will never be true.
2) if the test would be true at all, it would still only change the hostname if
there is a change in the *dhcp-server supplied hostname*, i.e. if the hostname
used to be foo and suddenly, the dhcp-server sends a hostname bar, then the
hostname will change.
This is also against the dhclient documentation, see man dhcp-options:
option host-name string;
This option specifies the name of the client. The name may or may
not be qualified with the local domain name (it is preferable to use
the domain-name option to specify the domain name). See RFC 1035
for character set restrictions. This option is only honored by
dhclient-script(8) if the hostname for the client machine is not
set.
This is no longer true: under Lucid, the hostname will not be set at
all, no matter what you try to do.
** Affects: dhcp3 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Until recently (up to and including Karmic), there was a set_hostname()
function in /sbin/dhclient-script, that said:
set_hostname() {
- local current_hostname=$(hostname)
- if [ -z $current_hostname -o $current_hostname = (none) ]; then
- hostname $new_host_name
- fi
+ local current_hostname=$(hostname)
+ if [ -z $current_hostname -o $current_hostname = (none) ]; then
+ hostname $new_host_name
+ fi
}
Up to 9.04, this would work when there was no /etc/hostname. With 9.10
(Karmic), this changed: a missing /etc/hostname sets the hostname to
localhost and the dhclient-script will no longer set the hostname:
- this bug is reported as bug #482313 and #523188 - see #482313 for the
- fix we have been using for years.
+ this bug is reported as bug #482313 and bug #523188 - see bug #482313
+ for the fix we have been using for years.
Now with Lucid, the whole thing goes wrong, as the set_hostname() function is
missing. There's only:
- BOUND|RENEW|REBIND|REBOOT)
- if [ -n $old_host_name -a -n $host_name -a \
- $host_name != $old_host_name ]; then
- hostname $new_host_name
- fi
+ BOUND|RENEW|REBIND|REBOOT)
+ if [ -n $old_host_name -a -n $host_name -a \
+ $host_name != $old_host_name ]; then
+ hostname $new_host_name
+ fi
This is plain wrong for two reasons:
1) as far as I can see, the $host_name variable does not exist at all;
there's only an old_host_name and a new_host_name, but host_name does not
exist - which means the test will never be true.
2) if the test would be true at all, it would still only change the hostname
if there is a change in the *dhcp-server supplied hostname*, i.e. if the
hostname used to be foo and suddenly, the dhcp-server sends a hostname bar,
then the hostname will change.
This is also against the dhclient documentation, see man dhcp-options:
option host-name string;
- This option specifies the name of the client. The name may or may
- not be qualified with the local domain name (it is preferable to use
- the domain-name option to specify the domain name). See RFC 1035
- for character set restrictions. This option is only honored by
- dhclient-script(8) if the hostname for the client machine is not
- set.
+ This option specifies the name of the client. The name may or may
+ not be qualified with the local domain name (it is preferable to use
+ the domain-name option to specify the domain name). See RFC 1035
+ for character set restrictions. This option is only honored by
+ dhclient-script(8) if the hostname for the client machine is not
+ set.
This is no longer true: under Lucid, the
[Bug 531854] [NEW] bind9 will not install on a clean system
Public bug reported: Binary package hint: bind9 apt-get install bind9 Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: bind9-doc resolvconf The following NEW packages will be installed: bind9 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/322kB of archives. After this operation, 1049kB of additional disk space will be used. Preconfiguring packages ... Selecting previously deselected package bind9. (Reading database ... 41267 files and directories currently installed.) Unpacking bind9 (from .../bind9_1%3a9.7.0.dfsg-1~build1_i386.deb) ... Processing triggers for ufw ... Processing triggers for ureadahead ... Processing triggers for man-db ... Setting up bind9 (1:9.7.0.dfsg-1~build1) ... md5sum: /etc/default/bind9: No such file or directory dpkg: error processing bind9 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: bind9 E: Sub-process /usr/bin/dpkg returned an error code (1) This is due to a logical error in the bind9.postinst file: [...] theirs=$(md5sum /etc/default/bind9) if [ -e /etc/default/bind9 ] \ [ $(cat /usr/share/bind9/bind9-default.md5sum) = $theirs ]; then So if /etc/default/bind9 does not exist, the script exits with an error (due to the set -e nature of the install scripts) This is Debian bug #572443 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572443 ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New -- bind9 will not install on a clean system https://bugs.launchpad.net/bugs/531854 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 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
