/srv/irclogs.ubuntu.com/2013/10/05/#ubuntu-release.txt

slangaseksmoser, utlemming: how do the changes in cloud-init to cloudinit/sources/DataSourceSmartOS.py relate to the bugs in the changelog?00:05
smoseradjusting for the changes required for azure00:07
slangaseksmoser: what does 'availability-zone' have to do with azure?00:17
slangaseksmoser: also, isn't there a mismatch between 'availability-zone' and 'availability_zone'?00:18
smoserslangasek, crap. that isn't even necessary (as its taken care of elsehwere)00:55
smoser:-(00:55
smoserwell, the availability-zone -> availabilty_zone. something else handles either or on that.00:56
slangaseksmoser: so does this warrant a reupload?00:56
smoserwell, i assume utlemming put that in for some reason.00:56
smoserhe didn't need to put the 'availability_zone' portion in. the getter.00:57
smoserbut he did add it to SMARTOS_ATTRIB_MAP . and i'm assuming that that solved a problem for him. which unfortunately is not documented.00:57
smoserif you want me to re-upload i'll bug utlemming and do that on monday.00:57
smoseror you can let this in and we'll get a bug for it anyway.00:58
slangasekwell, since there's nothing about it in the changelog I'd rather not let it in as-is00:58
smoseri'll re-upload quikcly then with a changelog message.00:59
smoserplease NAK that one00:59
smoserand i'll add changelog entry00:59
slangasekok01:00
slangaseksmoser: but, what will the changelog message say if you don't know what this change was needed for...?01:02
smoseri know what the insertion into the map will do01:03
smoserand why he'd do that.01:03
smoserbut the other portion was not necessary01:03
slangasekok. are you backing that bit out then?01:04
slangasekor do we just trust that it's a no-op?01:04
smoserit is a noop01:06
smoserbut i'm backing out01:06
smoserand will upload01:06
smoserquickly01:06
slangasekokie01:07
smoserjust pushed01:08
slangasekinfinity: erm03:09
slangasekinfinity: the change in -0ubuntu5 is not SRU-worthy and should not hold up the SRU of the rest of the critical fixes03:10
infinityslangasek: Oh.  Seemed to me you'd want sbsigntool to also be able to verify sanely, but sure.  I can re-review and accept ubuntu4 from rejected.05:42
bkerensaslangasek: Ubuntu Docs is ready for a upload if you would like to sponsor :)06:50
ginggsHi all.  I've noticed some SRU bugs didn't get the usual message that they are in -proposed and needed verification e.g. LP: #1076414, LP: #100698807:44
ubot2Launchpad bug 1076414 in nvidia-settings-updates (Ubuntu) "Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings" [High,Invalid] https://launchpad.net/bugs/107641407:44
ubot2Launchpad bug 1006988 in inventor (Ubuntu Precise) "ivview application does not start" [Undecided,In progress] https://launchpad.net/bugs/100698807:44
=== brainwash_ is now known as brainwash
loolI've blocked unity8, unity-notifications, indicator-network to upload them together to saucy09:49
loolcjwatson: Not quite sure why the packageset is ubuntu-desktop here ^09:51
loolso we're reuploading unity-notifications + indicator-network + unity8, reverting the reverts for the first two and with proper fix for 3rd one09:58
cjwatsonlool: dunno, not going to investigate now :)10:15
loolcjwatson: fair enough, do you have a sec to review it from unapproved though?10:15
cjwatsonwas just doing so10:16
loolawesome10:16
cjwatsonlool: oh, it's in ubuntu-desktop because there's a manual exception, apparently10:21
* cjwatson pokes at history10:22
cjwatsonlool: http://bazaar.launchpad.net/~cjwatson/+junk/packageset/revision/6610:22
cjwatsonlool: So that's fairly old and if kenvandine no longer thinks that's necessary I can undo the indicator-network part of it10:23
cjwatsonMaybe it was in desktop installs at the time10:23
cjwatsonOr maybe they just needed upload privileges to it10:24
loolcjwatson: I'll write him a mail asking about it10:25
cjwatsonKen joined core-dev since then which might make a difference :)10:28
cjwatsonremember that it's an extremely recent thing to have being in a packageset have a negative effect (i.e. no auto-accept)10:28
cjwatsonbefore that it was generally an unrestricting kind of thing10:29
loolcjwatson: yup; I don't particularly mind, it just seems inconsistent with reality10:35
loolthanks for looking into it10:36
cjwatsonit does seem inconsistent - normally I only add that kind of manual exception when it widens permissions, e.g. when the package would otherwise be in core10:45
cjwatsonbut that isn't the case now for indicator-network, so the situation probably changed10:46
cjwatsonfor moving from unseeded to in a package set I would normally ask for a seed entry instead10:47
smartboyhwPlease ACK Bug 1235651 for us13:24
ubot2Launchpad bug 1235651 in ubuntustudio-meta (Ubuntu) "[FFe] Include ardour3 in ubuntustudio-meta" [Undecided,New] https://launchpad.net/bugs/123565113:24
slangasekinfinity: we don't rely on sbverify anywhere in the archive, it's only used by some QA tests, and the SRU isn't going to happen quickly enough to be a reasonable solution for those currently-failing tests.  So, thanks for the un-reject. :)16:54
loolit looks like britney didn't run for a couple of hours?17:13
loolcjwatson: FYI ^17:13
slangaseklool: I fear that's probably related to the mail Larry just sent out about jenkins private IP changing and firewall rules getting in the way of jobs from snakefruit + nusakan18:01
slangasekif britney can't talk to jenkins, it can't get ADT results18:01
slangasekso, RT #6504018:02
slangasekretoaded: is there a committment from IS to work on this ticket over the weekend?  saucy development is dead in the water until that firewall rule is fixed18:03
slangasekretoaded: so if the firewall isn't getting fixed until Monday, I think we need britney to be able to continue to reach jenkins on the old IP until then18:04
loolDropping him an email too to max chances of this being seen18:08
loolslangasek: it's a bit surprizing in terms of timing that it blocks now though18:08
slangasekI suspect this dependency was overlooked in the migration plan for magners, otherwise the RT would've been filed sooner than 9pm London time on a Friday18:09
loolI don't quite understand how when moving to a new IP we're not copying over all rules from the old IP18:10
loolperhaps because we're resplitting multiple services across different machines18:10
loolbut seems like we should be tracking dependencies between services better18:10
loolanyway18:10
loolwin 3318:12
loolups18:12
slangasekhmm, but now I'm doubting that the firewall is the issue18:17
slangasekat least, direct connection to both old and new IPs fails, as does connecting via the proxy18:17
loolslangasek: it happened in the past that britney got stuck18:17
slangasekI don't see evidence of that18:17
loolbut I think it's now running on a host that I'm not sure I have access to18:17
slangaseksnakefruit18:17
loolyeah, my public key isn't accepted there18:18
loolif you can check whether there's a stale britney process running for a long time there18:18
slangasekthere is not18:19
slangasekI think this *is* related to the jenkins move18:19
slangasekI just am not sure it's a firewall issue18:19
slangaseklool: so, running britney by hand appears to have succeeded18:24
slangasekbut only the third time I ran it18:24
slangasekand that doesn't explain the lack of attempts over the past 3h18:25
slangasekit's possible that britney didn't run because there were no new packages accepted into -proposed?  the britney run is guarded by:18:25
slangasekif release_changed "$DEVEL" || release_changed "$DEVEL-proposed"; then18:25
slangasek        background pids run-proposed-migration18:25
slangasekfi18:26
slangasekanyway, evidently my manual test of jenkins availability from snakefruit was flawed somehow18:26
slangasekretoaded: ^^ seems we're not as blocked as I was afraid we were18:26
loolslangasek: ah cool, I thought of this at first because it seemed to run less frequently over the week-end, but then I discarded the idea because it seemed a poor choice considering a) people might upload hints at any time and b) transitions might be held by autopkgtests19:35
infinityYeah, the 'if changed' logic stopped making sense when autopkgtesting was added to the mix.19:37
infinityWe could change the trigger from "release_changed" to "germinate_changed", but then britney will run later in the publisher cycle and miss the window to promote before the next run.19:41
infinityThe proper answer is to trigger it *from* ftpmaster, which we intend to do.19:41
infinityI guess we could run it on release_changed || germinate_changed.19:42
infinityThere.  Done.19:44
infinityWait, no.19:51
* infinity undoes.19:51
infinityHaving it promote twice in the same publisher cycle might be less than ideal.19:51
infinityI think we probably just want to fix this properly, with an SSH trigger.19:51
stgraberinfinity: I think what we discussed at the sprint was triggering from ftpmaster + every 5 or 10 minutes (if no ftpmaster trigger in between)21:25
stgraberthat was to workaround the case of a frozen archive with very little changes but required britney run to monitor autopkgtest and get things copied over21:26
infinitystgraber: A frozen archive still runs the publisher.21:29
infinitystgraber: So, it really just needs to trigger unconditionally, post-publish-attempt, even if no dirty pockets published.21:29
stgraberinfinity: wouldn't that mean running britney basically continuously given how often we run the publisher nowadays?21:30
infinitystgraber: Ish, but not quite.  britney still runs much faster than the publisher.21:30
slangasekright, but the cron trigger is set up to run every minute... which may be excessive frequency21:40
retoadedslangasek, ack22:03

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