[01:50] why did our CI speed improve so much lxd 3.0? [01:51] Run speed before today: LTS: 9min 11s LTS integration: 8min 15s MAAS Compat: 19min 4s [01:52] run speed today: LTS: 2min 12s LTS integration: 2min 37s MAAS compat: 2min 41s [02:05] looks like 2 mins after cloud-init sbuild completed in https://jenkins.ubuntu.com/server/job/cloud-init-ci/970/consoleFull we were running ci-tests yesterday, https://jenkins.ubuntu.com/server/job/cloud-init-ci/964/consoleFull there was generally an 11 minute gap between sbuild completion and citest runs. [03:02] blackboxsw: rharper moved the storage file for lxd onto the nvme, sooo yeah :0 [03:03] in the past we have used zfs, which was fast as it, then moved to btrfs currently. [03:03] man that's fast [03:03] the move to the nvme will help everything [03:03] I wish all our systems had at least ssds in them === Beret- is now known as Beret === shardy is now known as shardy_mtg [14:08] powersj: hehe, will be nice when we can switch back to zfs on nvme === r-daneel_ is now known as r-daneel [16:19] powersj: blackboxsw: pylint will find it (need a pylint newer than what's on xenial, we do in our tox) ; but it needs some help; it doesn't know that the variable is a string: https://paste.ubuntu.com/p/YkP4QW9qwb/ [16:22] wow [16:23] well, the dver comes from a get on a yaml load; so I *think* I can understand that it doesn't know until runtime what the yaml parsing will return [16:43] weird [19:42] rharper: I'm updating the sru manual test scripts now. and I'll ping when I push them to https://github.com/cloud-init/ubuntu-sru/ [19:42] once I have the scripts updated, I'll hit up gce manual validation [21:15] blackboxsw: nice [21:15] I'm back, I can start on ec2 if that's ready [21:16] so far everything is queued for release, but still in unapproved state. https://launchpad.net/ubuntu/artful/+queue?queue_state=1&queue_text=cloud-init doesn't look like anyone is around to tick the done status for the upload to succeed into artful & xenial. [21:16] so that part will have to wait until tomorrow. [21:17] but yes we can start manual verification if you can build your own deb. launch-ec2 (from qa-scripts) could help make that easier on the cmdline [21:17] blackboxsw: did you ping the vanguard in #ubuntu-release ? [21:17] blackboxsw: do you have your .debs from the sbuild ? [21:17] rharper: I did, only vanguard today was robie or arges, [21:18] oh, huh [21:18] and robie was EOD and arges isn't in channel [21:18] no ? bummer [21:21] blackboxsw: where do you get your awscli ? deb or snap ? [21:22] rharper: I used a deb locally [21:23] on bionic ? [21:23] or xenial ? [21:23] awscli 1.11.13-1ubuntu1~16.04.0 [21:23] i [21:23] huh [21:23] either should work [21:23] I only had /usr/bin/aws [21:23] sorry paste fail [21:24] oh, I see, we really only need the ~/.aws/credentials as we're using boto3 [21:25] * blackboxsw wonders why I still have the deps check on awscli though [21:25] the package name ? [21:25] boto uses it maybe [21:25] maybe [21:26] had I written a helpful comment in the launch-ec2 script I'd know ;) [21:31] blackboxsw: do you have an example launch-ec2 command for testing one of these bugs ? [21:33] rharper: https://github.com/cloud-init/ubuntu-sru/blob/master/manual/ec2-sru-17.2.35.2.txt [21:34] nifty [21:34] * blackboxsw needs to stop trying to writeup the SRU regression upgrade process in qa-scripts/doc [21:35] I'll push what I have over there [21:35] thx [21:35] and the .deb as well [21:35] and I can start running through the list [21:35] ahh yes one min, will rebuild [21:41] rharper: scp sru@blackboxsw.com:*deb . [21:41] your lp id is imported there temporarily [21:41] k [21:42] % sha512sum cloud-init_18.2-4-g05926e48-0ubuntu1~16.04.1_all.deb [21:42] ea85001e818aefe6967626d78f45e816c5ded1be71a8b58cdebbdab6906e8113a201668afaaebd983e3090e0570ae95da76308c2931ccee84f68365a76f37a6d cloud-init_18.2-4-g05926e48-0ubuntu1~16.04.1_all.deb [21:42] blackboxsw: match ? [21:43] match ea85001e818aefe6967626d78f45e816c5ded1be71a8b58cdebbdab6906e8113a201668afaaebd983e3090e0570ae95da76308c2931ccee84f68365a76f37a6d [21:43] almost done w/ artful deb there [21:43] k [21:47] rharper: /home/sru/cloud-init_18.2-4-g05926e48-0ubuntu1~17.10.1_all.deb is avail there now too [21:47] 6d8c642c8cfb470a28d50e8a5e0e1c229b0ff173e579dddc6d53670179b374dba7cb9f634ed040b24d74d127b068056f78e571c71763502c7618048def655487 [21:47] * blackboxsw is going to test gce now [21:48] blackboxsw: snagged and matches [21:48] k [21:48] * rharper hits up ec2 [21:48] * blackboxsw kills the sru user [22:07] Unknown parameter in input: "AmazonProvidedIpv6CidrBlock", must be one of: DryRun, CidrBlock, InstanceTenancy [22:10] hrm [22:10] python3-boto3 1.2.2 [22:10] python3-boto3 1.2.2 [22:10] and python3-botocore 1.4.70-1~16.04.0 [22:10] same [22:11] anything special in your ~/.aws/config ? I've just output and region set [22:11] [default] [22:11] region = us-east-2 [22:12] huh [22:12] shrug [22:12] may be related to my account and it's vpc defaults [22:12] s/it's/its [22:13] it's what we pass to boto3's ec2.create_vpc [22:13] yeah, I saw that in the code, not sure why it doesn't like it [22:13] ec2 = boto3.resource('ec2', region_name=args.region); ec2.create_vpc( CidrBlock='10.41.0.0/16', AmazonProvidedIpv6CidrBlock=True) [22:14] yeah, hrm [22:14] checking boto3 docs [22:15] boto3 1.6.23 docs has it [22:15] http://boto3.readthedocs.io/en/latest/reference/services/ec2.html [22:19] blackboxsw: did up update the ubuntu-sru github ? [22:20] FYI when I run integration tests typically use tox, which pulls in boto3 1.5.9 or bionic's 1.4.2 [22:20] rharper, just qa-scripts now [22:29] rharper: just pushed ubuntu-sru [22:29] thx [22:29] need to tweak the manual scripts for 18.2.4 for each platform [22:29] I only copied 17.2.35.txt -> 18.2.4 as templates [22:30] I'm updating the readme to include markdown checklist items for this SRU now [22:35] * rharper is going to see about getting an up-to-date boto3 [22:59] rharper: tox -e citest -- {args}