/srv/irclogs.ubuntu.com/2014/07/24/#ubuntu-release.txt

JackYujibel, hi, Ubuntu Kylin is ready for release. Will is the URL of Ubuntu release note? Do we need to prepare one for Ubuntu Kylin?03:49
infinityJackYu: I'm not sure individual announcements are really necessary for the point release, but if you want want to, you can.04:21
JackYuinfinity, I think so:)05:05
JackYuinfinity, so, I choose to share the Ubuntu one:).05:06
=== s8321414_ is now known as s8321414
jibeljamespage, hey, could you update the tracker with the results for the tests for 14.04.1 server images?08:29
jamespagejibel: I thought that was automated?08:31
jamespagejibel, I can certainly help with the iscsi testing as I normally do - beisner will be around later to co-ordinate the rest08:38
infinityjibel: I'll do server on the powerpcs and core on ppc and arm64 tonight.  How are we looking otherwise?09:27
infinitytgm4883: You good to go to mark mythbuntu ready?09:31
infinityelfy: Ditto for xubuntu?09:31
jibelinfinity, images are fine, upgrades are not so good. bug 1348067 , bug 1347964 (ubuntu-desktop fails to upgrade) and the failure with procps from saucy to trusty found yesterday09:37
ubot93bug 1348067 in update-manager "update-manager crashed with TypeError: pulse() takes exactly 1 argument (2 given)" [High,In progress] https://launchpad.net/bugs/134806709:38
ubot93bug 1347964 in ubuntu-release-upgrader "Precise w/Trusty HWE -> Trusty release upgrade fails critically" [High,Triaged] https://launchpad.net/bugs/134796409:38
infinityjibel: check.  Those are archive issues rather than image issues (not to downplay them, they need investigation, but shouldn't hold up the ISOs)09:40
jibeljamespage, tests are automated I'm just not sure if anyone look at the results09:40
infinityjibel: We saw a variation on your saucy->trusty issue a day or two before release and reverted something that made apt happy, but clearly not happy enough.  The real bug needs hunting and fixing. :/09:41
apwinfinity, oh is it _that_ one09:41
apwback to haunt us09:41
jibelinfinity, sure these upgrade issues don't affect the images themselves09:42
highvoltageIs there a wiki page that lists what have changed in the 14.04.1 point release?09:45
infinityapw: Yeah, looks like it's the same bug.09:56
jamespagejibel, looking at https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/ the server iso tests have not run for a bit now10:25
jibeljamespage, pfff, I'll talk to CI.10:26
* jibel clears the results on the tracker10:26
highvoltagejibel: hey there10:39
jibelhighvoltage, hi10:42
highvoltagejibel: I see you tested edubuntu 14.04.1 and passed ltsp, what hardware was that on?10:43
jibelhighvoltage, in VMs10:43
highvoltagejibel: kvm?10:43
jibelhighvoltage, no virtualbox, 1rst has 2 NICs (1 for external network and 1 for internal network) and 2nd VM has 1 NIC connected to the internal network10:44
highvoltagejibel: ok, thanks. I had some trouble with it under kvm, but my host was under load so I'll try again10:44
jibelhighvoltage, you must install vbox extensions to pxe boot the client10:46
highvoltagejibel: my kvm thin client boots, but ldm doesn't start, but I'll troubleshoot further in a bit...10:47
highvoltageweird, it works fine when I set my virtual display card to anything that's not 'cirrus'.10:56
xnoxi have no clue why cirrus is still the default, when it's that bad, and nobody has hardware like that any more.10:59
highvoltagexnox: yeah, strangely enough my host vm was also set to cirrus and that started X up just fine oO11:02
pfsmorigoinfinity: is there a way to get an "older" daily?11:23
pfsmorigolike 1 month old11:23
cjwatsonDailies are purged after a while; we don't have space to keep them for very long.11:25
pfsmorigocjwatson: I'm doing tests with the daily and the system seems to freeze during the first reboot after the installation11:34
pfsmorigocjwatson: talking about ppc64el here11:35
pfsmorigocjwatson: I want to test with some older versions after 14.0411:35
cjwatsonIt'll probably have to be investigated directly rather than by bisection, sorry.11:35
cjwatsonWe don't have the old dailies any more.11:36
infinitypfsmorigo: Is this on P7 or P8?  Real hardware or VM?11:37
infinitypfsmorigo: I was just about to test on a P7 VM.11:37
pfsmorigocjwatson: qemu11:37
pfsmorigoinfinity: ^11:37
pfsmorigoinfinity: do you have a powerkvm to test?11:37
infinitypfsmorigo: I do, yes.11:39
pfsmorigoinfinity: nice, so you just have to create a disk and install using the default options. the problem happens after the installation is over.11:40
infinitypfsmorigo: And if I fail to reproduce it?11:42
infinitypfsmorigo: Note that the kernel on the CD and the kernel you're rebooting into are identical, so it's curious if it's freezing on reboot. :/11:42
pfsmorigoinfinity, cjwatson: https://gist.github.com/pfsmorigo/1a9f21bc7d0b6a48d81811:42
pfsmorigoinfinity, cjwatson: it freezes after that11:43
infinitypfsmorigo: That's not frozen, that's a lack of console.11:43
pfsmorigoinfinity: hmm. how do I "fix" it?11:44
infinityI'm not sure how you broke it.11:45
infinityOF stdout device is: /vdevice/vty@3000100011:45
infinityOn every other SLOF install I've done, that's /vdevice/vty@3000000011:45
pfsmorigoinfinity: good point11:45
elfyinfinity: I somehow knew that I'd see a ping when I got in for lunch :p marked ours ready :)11:45
infinityelfy: Ta.11:46
elfyinfinity: you going to need release notes?11:46
infinityelfy: Hand't planned on extensive flavour notes, unless anyone really wants to do some of their own.11:46
infinityHadn't, even.11:47
elfyawesome - suits me perfectly tbh :)11:47
infinitypfsmorigo: So, I guarantee I won't be able to reproduce your issue on my VMs, where my SLOF defaults to a different console device.11:47
pfsmorigoinfinity: the bug reporter use virsh and his xml has serial set to 3000100011:47
infinitypfsmorigo: The question then is, is this a new version of SLOF, or some weird way you're invoking qemu?11:47
pfsmorigoinfinity: will try using 3000000011:48
infinitypfsmorigo: Oh, he's explicitly using a non-standard port? :(11:48
infinity*sigh*11:48
pfsmorigoinfinity: cool, isn't? :P11:48
infinitySo, we could very much improve the way we detect this, to be fair.11:48
infinityBut, if you just let qemu/slof do their default thing, it works fine.11:48
pfsmorigoinfinity: agree11:49
infinitypfsmorigo: A bug report that says "when I pick a non-standard serial setup, it all goes to poop" and some explanation of how to reproduce would be nice.11:49
infinitypfsmorigo: Reported against "finish-install".11:49
pfsmorigoinfinity: he just attached the xml that he used to test the distro. don't know why he uses a non-standard port11:50
infinitypfsmorigo: Because your testers like to confuse me. :)11:52
infinitypfsmorigo: It's definitely still a bug that we fail to detect that situation, just not a critical one, since I can't see how "normal" users would do that by accident.11:53
pfsmorigoinfinity: glad we solve it before it turns into a obscure kernel bug :P11:53
pfsmorigoinfinity: the serial/console in his xml is like this: https://gist.github.com/pfsmorigo/32ada7e5439ef80d8e5e11:55
infinityHave I ever mentioned how much I hate virsh/libvirt?11:56
infinityIf you just call qemu raw, you get a sane console on 0x30000000 which is, in fact, what you get when you boot a "real" openfirmware system via PowerVM or SLOF on bare metal too.11:57
pfsmorigoinfinity: I used qemu directly and had the same "freeze"12:28
infinitypfsmorigo: Testing independently here to see what I get.12:31
infinitypfsmorigo: Out of curiosity, where does SLOF report your console being?  And how did you call qemu?12:32
infinitypfsmorigo: An install and reboot went fine here.12:38
pfsmorigoinfinity: qemu-system-ppc64 -enable-kvm -M pseries -smp 4,cores=2,threads=4 -m 4G -nographic -device spapr-vscsi -device spapr-vlan,netdev=net0,mac=4C:45:42:45:06:41 -netdev bridge,br=br0,id=net0 -nodefaults -monitor stdio -serial pty -drive file=disk.img12:39
pfsmorigoinfinity: then: screen /dev/pts/xx12:39
infinitypfsmorigo: SLOF **********************************************************************12:40
infinityQEMU Starting12:40
infinity Build Date = Oct 15 2013 03:55:1012:40
infinity FW Version = mockbuild@(private build)12:40
infinity Press "s" to enter Open Firmware.12:40
infinityPopulating /vdevice methods12:40
infinityPopulating /vdevice/vty@7100000012:40
infinityPopulating /vdevice/nvram@7100000112:40
infinityPopulating /vdevice/l-lan@7100000212:40
infinityPopulating /vdevice/v-scsi@7100000312:40
infinity       SCSI: Looking for devices12:40
infinity          8000000000000000 DISK     : "QEMU     QEMU HARDDISK    1.6."12:40
infinity          8200000000000000 CD-ROM   : "QEMU     QEMU CD-ROM      1.6."12:40
infinityPopulating /vdevice/v-scsi@7100000412:40
infinity       SCSI: Looking for devices12:40
infinityPopulating /pci@80000002000000012:40
infinity Adapters on 080000002000000012:40
infinity                     None12:40
infinityScanning USB12:40
infinityUsing default console: /vdevice/vty@7100000012:40
infinity  Welcome to Open Firmware12:40
infinity  Copyright (c) 2004, 2011 IBM Corporation All rights reserved.12:40
infinity  This program and the accompanying materials are made available12:40
infinity  under the terms of the BSD License available at12:41
infinity  http://www.opensource.org/licenses/bsd-license.php12:41
infinityTrying to load:  from: disk ...   Successfully loaded12:41
infinity* finddevice /memory grub workaround *12:41
infinityerror: no suitable video mode found.12:41
infinityerror: failure writing sector 0x1044888 to `ieee1275/disk'.12:41
infinity* finddevice /memory grub workaround *12:41
infinity* finddevice /memory grub workaround *12:41
infinityPress any key to continue...12:41
infinityOF stdout device is: /vdevice/vty@7100000012:41
infinityPreparing to boot Linux version 3.13.0-32-generic (buildd@denneed04) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #57-Ubuntu SMP Tue Jul 15 03:50:31 UTC 2014 (Ubuntu 3.13.0-32.57-generic 3.13.11.4)12:41
infinityDetected machine type: 000000000000010112:41
infinityMax number of cores passed to firmware: 2048 (NR_CPUS = 2048)12:41
infinityCalling ibm,client-architecture-support... done12:41
infinitycommand line: BOOT_IMAGE=/boot/vmlinux-3.13.0-32-generic root=UUID=d3530761-1c4f-4858-a284-79190eb52841 ro splash quiet vt.handoff=712:41
infinitymemory layout at init:12:41
infinity  memory_limit : 0000000000000000 (16 MB aligned)12:41
infinity  alloc_bottom : 0000000004e1000012:41
infinity  alloc_top    : 000000003000000012:41
infinity  alloc_top_hi : 000000030000000012:41
infinity  rmo_top      : 000000003000000012:41
infinity  ram_top      : 000000030000000012:41
infinityinstantiating rtas at 0x000000002fff0000... done12:41
infinityprom_hold_cpus: skipped12:41
infinitycopying OF device tree...12:42
infinityBuilding dt strings...12:42
infinityBuilding dt structure...12:42
infinityDevice tree strings 0x0000000004e20000 -> 0x0000000004e2072712:42
infinityDevice tree struct  0x0000000004e30000 -> 0x0000000004e4000012:42
infinityCalling quiesce...12:42
infinityreturning from prom_init12:42
infinity -> smp_release_cpus()12:42
loolthis is going to take some time12:42
infinityspinning_secondaries = 712:42
infinity <- smp_release_cpus()12:42
infinity <- setup_system()12:42
infinityCF00001212:42
infinityCF000015ch12:42
infinityLinux ppc6412:42
infinity#57-Ubuntu SMP T * Starting Mount filesystems on boot                    [ OK ]12:42
infinity * Starting Populate /dev filesystem                                     [ OK ]12:42
infinity * Starting Populate and link to /run filesystem                         [ OK ]12:42
infinity * Stopping Populate /dev filesystem                                     [ OK ]12:42
infinity * Stopping Populate and link to /run filesystem                         [ OK ]12:42
infinity * Stopping Track if upstart is running in a container                   [ OK ]12:42
infinity * Starting Signal sysvinit that the rootfs is mounted                   [ OK ]12:42
infinity * Starting Initialize or finalize resolvconf                            [ OK ]12:42
infinity * Starting Signal sysvinit that virtual filesystems are mounted         [ OK ]12:43
infinity * Starting Signal sysvinit that virtual filesystems are mounted         [ OK ]12:43
infinity * Starting Bridge udev events into upstart                              [ OK ]12:43
infinity * Starting Signal sysvinit that remote filesystems are mounted          [ OK ]12:43
infinity * Starting Clean /tmp directory                                         [ OK ]12:43
infinity * Starting device node and kernel event manager                         [ OK ]12:43
infinity * Stopping Clean /tmp directory                                         [ OK ]12:43
infinity * Starting load modules from /etc/modules                               [ OK ]12:43
infinity * Starting cold plug devices                                            [ OK ]12:43
infinity * Starting log initial device creation                                  [ OK ]12:43
infinity * Starting Signal sysvinit that local filesystems are mounted           [ OK ]12:43
infinity * Stopping Mount filesystems on boot                                    [ OK ]12:43
infinityGAH.12:43
infinityWRONG MOUSE BUTTON.12:43
infinitypfsmorigo: http://paste.ubuntu.com/7847407/12:43
infinitypfsmorigo: So, I'm assuming '-serial pty' does something funky.  But this isn't new either, it would have been broken this same way since release (indeed, since we started the port).12:43
infinitylool: Sorry.  Middle click fail. :/12:43
infinitylool: Not sure how I didn't get kicked.12:43
pfsmorigoinfinity: https://gist.github.com/pfsmorigo/245ae92f1ff682f473db12:43
pfsmorigoinfinity: this is what I get in the screen12:44
xnoxlool: serial console over IRC is the best with rate limiting =)12:44
infinitypfsmorigo: Oh, kay, so you're getting a device we should be setting up correctly (the same one I just pasted).12:44
infinitypfsmorigo: Err, did you *install* with that setup, or are you rebooting an already broken install?12:45
pfsmorigoinfinity: second option12:45
infinitypfsmorigo: Kay, right.  So, broken.12:45
infinitypfsmorigo: The installer detects if it should set up a console on hvc[01] based on magic openfirmware nodes existing at install time.12:45
infinitypfsmorigo: So, if you run an install under that setup there, it'll work fine.12:46
pfsmorigoinfinity: ok, let me do some tests here12:46
infinitypfsmorigo: As you can see from my paste, which matches yours, but has a getty with a login prompt. :)12:46
loolxnox: yeah it felt like 100 bauds or something12:46
ogra_ls12:46
ogra_pwd12:47
loologra_: Password:12:47
pfsmorigolol12:47
ogra_12345612:47
ogra_oops !12:47
infinityogra_: That's the same combination I have on my luggage!12:47
ogra_lol12:47
loolhaha12:47
davmor2ogra_: I expect something more inventive from you like 123456!12:53
ogra_123456äöü12:53
ogra_;)12:53
davmor2ogra_: or hunter212:55
pfsmorigoinfinity: I found some tickets about this problem. https://bugs.launchpad.net/ubuntu/+bug/134796712:56
ubot93Launchpad bug 1347967 in ubuntu "ISST-KVM:Ubuntu14.04:LE guest failed to boot on its first reboot after installation" [Undecided,New]12:56
pfsmorigoinfinity: "From what I know, there is no difference/limitation between these two values to Libvirt, it just address assigned to the device. Althrough 30000000 is defined for VIO_ADDR_SERIAL specificly, both works fine as serial address."12:56
infinitypfsmorigo: Kay, so a Kimchi bug (and yes, also an Ubuntu bug)12:58
infinitypfsmorigo: For the record, the default in SLOF appears to be 71000000 (which we handle fine), and we also handle 30000000, but not 30001000.12:59
pfsmorigoinfinity: ok, got it12:59
infinitypfsmorigo: Going forward, I plan to try to rewrite this to detect things a bit more sanely but, for now, it might be nice if Kimchi wasn't doing silly non-standard things.12:59
infinitypfsmorigo: If there's already an install base of systems that will be trying 30001000 though, we can certainly fix the hardcoding in the installer to also look there for now.13:00
infinitypfsmorigo: Not for the point release, but for a later update.13:00
pfsmorigoinfinity: ok13:02
tgm4883infinity: yes Mythbuntu is good to go13:10
infinitytgm4883: \o/13:10
* infinity spins source ISOs.13:12
=== pete-woods is now known as pete-woods|lunch
highvoltageis there an estimated time for the release if everything goes well?13:34
=== chorrell is now known as chorrell-away
infinityhighvoltage: Not going to make estimates, but "today, in my timezone".13:36
infinityhighvoltage: Which gives you, uhm, 16.5 hours of wiggle room. :P13:36
highvoltageinfinity: *shrug*, good enough :)13:41
jibelinfinity, ubuntu looks good, server tests are done, I'm updating the tracker. The most critical bugs found are upgrade crashes mentioned earlier, someone from foundations will have to look at them.13:46
infinityjibel: Agreed, we'll have to make some time to take a closer look ASAP.13:48
infinityjibel: And possibly hold off on flipping the meta-release upgrade switch until we know WTF is going on.13:48
infinityjibel: Though, have you seen the issue with precise->trusty, or just saucy->trusty?13:49
jibelinfinity, +1 holding off flipping the switch13:50
jibelinfinity, I reproduced 134796413:50
jibelbug 134796413:50
ubot93bug 1347964 in ubuntu-release-upgrader "Precise w/Trusty HWE -> Trusty release upgrade fails : ubuntu-desktop fails to configure" [High,Triaged] https://launchpad.net/bugs/134796413:50
jibeltwice13:50
jibeland it leaves the system in a completely broken state, if you reboot you cannot even login13:50
infinityjibel: Oh, that's an entirely different bug, and probably a pure packaging issue.  But yes, that should also be fixed. :/13:56
mdeslaurinfinity: can the eglibc package be removed in utopic?13:59
infinitymdeslaur: Need to fix all the cross-buildy stuff, but that's the plan, yes.14:07
mdeslaurinfinity: ah, ok, thanks14:07
=== chorrell is now known as chorrell-away
=== pete-woods|lunch is now known as pete-woods
=== chorrell-away is now known as chorrell
mdeslaurinfinity: if you still care about the lucid sparc eglibc FTBFS, now would be the time to get me that patch you had14:22
infinitymdeslaur: Oh, is it security time?  Whee.  No need to do utopic, BTW, I'll merge with Debian (assuming it's the CVE covered in unstable a week or so ago).14:27
mdeslaurinfinity: yeah, that's the one14:27
infinitymdeslaur: I don't actually remember what the sparc issue was.  I'm not sure I remember even having the conversation. :)14:28
infinitymdeslaur: Oh, it was a breakage in the most recent security update.  Yeah, I think we pulled a patch or two for that in Debian.  Can I look tomorrow, or are you doing it Right Now?14:31
mdeslaurinfinity: https://launchpad.net/~ubuntu-security/+archive/ubuntu/ppa/+build/506825014:31
mdeslaurinfinity: yeah, you can look tomorrow14:31
infinity  * patches/any/cvs-CVE-2013-4237-alignment.diff: Fix alignment of the14:33
infinity    directory block in dirstream.h, fixing readdir regression on sparc.14:33
ubot93sysdeps/posix/readdir_r.c in the GNU C Library (aka glibc or libc6) 2.18 and earlier allows context-dependent attackers to cause a denial of service (out-of-bounds write and crash) or possibly execute arbitrary code via a crafted (1) NTFS or (2) CIFS image. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-4237)14:33
infinitymdeslaur: Looks like it would be that one.14:33
mdeslaurinfinity: thanks, I'll take a look when I work on lucid14:33
infinitymdeslaur: Possibly might also want to look at:14:33
infinity  * patches/any/cvs-CVE-2013-4332-memalign-2.diff: patch from upstream to14:33
ubot93Multiple integer overflows in malloc/malloc.c in the GNU C Library (aka glibc or libc6) 2.18 and earlier allow context-dependent attackers to cause a denial of service (heap corruption) via a large value to the (1) pvalloc, (2) valloc, (3) posix_memalign, (4) memalign, or (5) aligned_alloc functions. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-4332)14:33
infinity    address some remaining issues from CVE-2013-4332.14:33
infinitymdeslaur: If you have troubles hunting those down (cause they're likely merged upstream by now, and thus not patches in utopic), I can help you tomorrow.14:37
mdeslaurinfinity: thanks, I'll let you know14:37
mvo_could someone reject my upload for update-manager to precise-proposed please?15:07
infinitymvo_: Sure.15:17
mvo_tthanks infinity15:21
=== chorrell is now known as chorrell-away
mvo_and if someone could review the update-manger in precise-proposed that would be great - its for the hwe-support so would be good to get it in15:47
jibelinfinity, I published the testing report, is there a changes summary or a script to generate it like https://wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/ChangeSummary/12.04.4 ?15:58
cjwatsonjibel: I'm going to make a start on that in a bit16:02
infinityjibel: I think we can promise it'll be at the obviously guessable URL, and it can just 404 for now.16:03
jibelcjwatson, okay16:04
xdatap1Hi everybody17:46
xdatap1I'm from the Italian LoCo Team. We realese a localized version of Ubuntu. Is the 14.04.1 already out? Can we release our image?17:47
zulcan an archive admin promote python-hacking please (#1331490)18:50
Riddellinfinity: are we nearly there yet?20:50
Riddellzul: done21:38

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!