[00:05] <guest____> hello there
[00:38] <dpb1> o/
[01:55] <rharper> paulmey: so os.path.exists('/sys/module/ntfs')  is one; and typically there should be a mount.$fstype binary in $PATH; so we have /sbin/mount.ntfs ;  mount -t $sf is going to invoke a mount.$fs binary to handle it;
[01:56] <smoser> rharper: i just uploaded .. slight change to your MP.
[01:56] <smoser> we had not added chagnelog entries for the commits on the ubuntu/devel branch
[01:56] <smoser> so i added them.
[01:59] <smoser> its https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text= now
[14:16] <rharper> smoser: ok; is that change that should be in qa-scripts new-upstream-snapshot ?
[14:25] <smoser> rharper: i'm not sure. that might be possible.
[14:25] <smoser> but what I had always been doing is when i commit to the ubuntu/devel branch (or any ubuntu/* branch)
[14:26] <smoser> to "queue" the commits for next
[14:26] <smoser> i would 'dch -i'
[14:26] <smoser> and make a commit with 'git commit -m "update changelog"' debian/changelog
[14:27] <smoser> i guess we could traverse the ubuntu branch since merge also and grab those commits to write the entry.
[14:28] <smoser> kind of weird to have new-upstream-snapshot do it though as those commits/entries-in-changelog are not from the new-upstream-snapshot. they were from commits to the ubuntu/ branch
[14:28] <smoser> woudl be nice though to have something doing that / envforcing it.
[14:29] <rharper> I didnt mean for it to do it, but just printing of the steps
[14:30] <rharper> I just need a reminder
[14:30] <smoser> oh. well, they're kind of supposed to be done *befor* you run new-upstream-snapshot
[14:30] <smoser> ie, when we commit to that branch
[14:30] <rharper> heh
[14:30] <smoser> we should do it
[14:30] <rharper> hrm
[14:30] <rharper> nothing new is committed ot ubuntu devel until we do the snapshot, right ?
[14:30] <rharper> I'm confused (as you already knew)
[14:44] <smoser> rharper: see 85ff391b29ec8ea2168371498ffe083c51258ef3
[14:45] <smoser> we have packaging only on the ubuntu branches
[14:45] <smoser> so those commits have to go to that branch
[14:46] <smoser> i prefer commits like that to be in one commit that makes the change, and one commit that updates the changelog ("git commit -m 'update changelog'")
[14:46] <smoser> that way they can be easily cherry-picked to other ubuntu/ branches
[14:46] <smoser> as debian/changelog changes are going to always conflict
[14:46] <rharper> oh, I see
[14:47] <rharper> that hit master, but should ahve been ubuntu/devel only
[14:54] <smoser> rharper: well we fixed in on master too
[14:54] <smoser> in master its just for the bddeb work flow
[14:54] <rharper> ok
[14:54] <rharper> right
[14:55] <smoser> i really only noticed that because I knew wer were explicitly looking for those 2 fixes
[14:55] <smoser> (isc-dhcp-client and iproute2)
[15:15] <blackboxsw> smoser: you setting up the Bionic update ?
[15:21] <smoser> blackboxsw: yeah, i'll file a bug now
[15:21] <blackboxsw> ok then I'll poke at IBM xenial a bit
[15:32] <smoser> blackboxsw: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1767412
[15:33] <rharper> smoser: blackboxsw and I were discussing if there was a way to keep the ConfigDrive -> softlayer detection in the xenial/artful only branches so bionic didn;t have to have that logic; but there is that gnarly hard-coded datasource list in /etc/cloud/cloud.cfg.d/ that's present which restricts what ds-identify looks for;
[15:34] <smoser> um... what detection is that ?
[15:34] <rharper> I don't think we have a way to tell ds_check on a particular datasource that it's really a different one;
[15:34] <rharper> there's a datasource_list: [NoCloud, ConfigDrive, None] list in those images, that's what blackboxsw found on the xenial instance
[15:34] <smoser> right
[15:34] <rharper> which means that after upgrade, ds-identify still won't "See"  softlayer
[15:35] <rharper> hoping to somehow transition to the softlayer datasource but that sort of means either nuke or re-writing , or somehow overriding it
[15:35] <rharper> which I'm not sure how we can do that reasonably
[15:37] <smoser> it should nto "see" softlayer
[15:37] <smoser> thats the plan
[15:38] <smoser> it shoudl go on using the datasource on disk.
[15:39] <smoser> separately we can/should discuss with CPC for them to start making new images on IBM in the same way they make bionic images.
[15:39] <smoser> so as to not have the slop that is there.
[15:41] <danMS> @rharper thanks for taking a look at the ntfs bug (1767002), i saw your comments from yesterday, you asked if there are further checks that can be done, but I’m not sure what further checks can be done? Many of the distro’s on the platform do not support ntfs in the images.
[15:42] <rharper> danMS: generally, is there a kernel module loaded (ntfs); and are there tools (mount.ntfs, fsck.ntfs, mkfs.ntfs); would be two other indicators (specically mount.ntfs)
[15:42] <rharper> that would allow modified centos/rhel images which have those tools to work rather than banning the distro entirely
[15:42] <rharper> if that makes sense
[15:45] <smoser> danMS: maybe another way out of this would be to just allow this configurable
[15:45] <smoser> and have RH and SuSE build images with "support_ntfs: false"
[15:45] <smoser> or what not.
[15:46] <smoser> hten dont worry at all about blowing away data on an ntfs partition.
[15:46] <smoser> rharper: http://paste.ubuntu.com/p/GYsxMyTR2F/
[15:46] <smoser> blackboxsw: ^ that is what i was thinking is the fix
[15:47] <rharper> smoser: but how would the softlayer ds get added to the datasource_list ?
[15:48] <smoser> it wont
[15:48] <smoser> and thats fine.
[15:48] <rharper> smoser: I was hoping to transition into the softlayer datasource
[15:48] <rharper> oh
[15:49] <rharper> so, once launched on a ConfigDrive, it would stay that way through upgrade and dist-upgrade  to bionic ?
[15:50] <smoser> yeah.
[15:50] <rharper> that has some asymmetry w.r.t things checking what ds was used;  not sure if that's a big issue or not
[15:50] <smoser> if the user removed the entry from the 99networklayer.cfg and dpkg-reconfigure, then they'd transition just as a new instance had been created.
[15:50] <rharper> right
[15:51] <blackboxsw> sure on pastebin smoser though maybe we can fold in the is_ds_enabled check inside is_ibm_cloud in ds-identify
[15:51] <blackboxsw> because we also have that check in dscheck_NoCloud
[15:53] <blackboxsw> I also just noted that our DataSourceNoCloud doesn't have a comparable filter for ibm too
[15:53] <blackboxsw> like ds-identify does
[15:53] <smoser> blackboxsw: yeah, you could potentially do that. but the fact that something is or is_not ibm cloud is not specifically related to whether or not hte datasource is in that list
[15:53] <smoser> so.. i just wrapped. but yeah, i dont have a real good reason to not do what you did.
[15:54] <smoser> uyeah..that was kidn of why i dropped the check in NoCloud
[15:54] <smoser> (in my diff)
[15:54] <smoser> if you have a Nocloud, then thats your issue. (and ours since we have aofficial images with it... )
[15:57] <danMS> thanks guys, will chat with paulmey
[15:58] <smoser> rharper: i'm going to force push the ubuntu/devel branch back to before we merged you.
[15:58] <rharper> smoser: ok
[15:58] <smoser> and then i'm going to make a bionic branch
[15:59] <rharper> sure
[16:26] <smoser> rharper: you want to do this or wnat me to ?
[16:27] <rharper> which ?
[16:27] <rharper> or what
[16:27] <smoser> ubuntu/bionic is now in a state that you can run new-upstream-snapshot
[16:27] <smoser> and it will all "just work"
[16:27] <smoser> one change to new-upstream-snapshot that i just pushed
[16:27] <rharper> I can run it again, but likely faster for you to do it
[16:27] <smoser> and your bug nuber is dch --release --distribution=bionic
[16:27] <smoser> oops
[16:27] <smoser> bug number is 1767412
[16:27] <smoser> ok. i can just do it.
[16:28]  * rharper looks at git log to see what's different
[16:32] <rharper> smoser: nice change to new-upstream-snapshot
[16:32] <smoser> rharper: it should differ only in the changelog
[16:32]  * smoser verifies that is true :)
[16:33] <rharper> from what to what ?
[16:34] <smoser>  7609065fd30c3a02122bded6ab213ebc3912584b
[16:34] <smoser> is raharper/ubuntu/devel/newupstream-20180426
[16:34] <smoser> what you had proposed
[16:34] <smoser> and diff current ubuntu/bionic -> that
[16:34] <smoser> you get
[16:34] <dpb1> smoser: upload good now?
[16:35] <smoser> http://paste.ubuntu.com/p/ScfhfhXvBP/
[16:35] <smoser> yeah, i just uploaded
[16:35] <rharper> yes
[16:35] <smoser> i shoudl have reversed the order there
[16:35] <smoser> but good.
[16:35] <rharper> smoser: that looks right (minus the order)
[16:36] <rharper> http://paste.ubuntu.com/p/DbqJ945jMh/
[16:36] <rharper> I put that here: raharper/ubuntu/devel/newupstream-20180427
[16:36] <smoser> just uploaded
[16:37] <rharper> \o/
[16:37] <smoser> https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text= shows it.
[16:42] <jocha> blackboxsw: Hey, just following up on merge request: https://code.launchpad.net/~jocha/cloud-init/+git/cloud-init/+merge/344192 :)
[16:42] <blackboxsw> jocha: thanks sorry for the delay, if I can't get to it today, it will be tomorrow. (was on vacation yesterday)
[16:43] <jocha> no worries! I understand that you must have a lot on your plate
[16:44] <smoser> blackboxsw: did you get sorted on launch ?
[16:44] <blackboxsw> smoser: I'm currently trying to use the UI for it. I'll try again cli and really look at the traceback to see what gives
[16:46] <blackboxsw> smoser: this is what I hit https://pastebin.ubuntu.com/p/Vq7fw5S2tf/
[16:50] <blackboxsw> ahh got it smoser
[16:50] <blackboxsw> it's because of how I set up my account
[16:50] <blackboxsw> to automatically inject my ssh key.
[16:50] <blackboxsw> adding a check in launch-softlayer now
[16:57] <blackboxsw> ok have a fix. pushing now
[17:10] <blackboxsw> pushed, testing a potential SL fix now
[17:35] <smoser> blackboxsw: i just pushed another on top there.
[17:35] <smoser> make sure it still works for you
[17:35] <smoser> i just verified emptying my keys and having it add one for me and then matching too.
[18:13] <smoser> blackboxsw: you make progress ?
[18:13] <smoser> i booted xenial on IBMCloud, upgraded, put this chagne in place
[18:13] <smoser>  http://paste.ubuntu.com/p/cRPzBt3Qg7/
[18:14] <smoser> (by hand)
[18:14] <smoser> and then rebooted and came up ok.
[18:16] <blackboxsw> smoser: I used the original changeset and tried a ds-identify run and saw an error on line 616
[18:16] <blackboxsw> DS_LIST param not set
[18:16] <smoser> yeah. i fixed taht
[18:16] <smoser> DI_DSLIST
[18:16] <smoser> is the name
[18:16] <blackboxsw> yeah
[18:18] <blackboxsw> smoser: the issue I think I'm seeing with that fixed is that xenial was originally ds-id'd as ConfigDrive but now returns NoCloiud
[18:18] <blackboxsw> hrm, wait a sec
[18:18] <blackboxsw> need to recheck that
[18:18] <blackboxsw> :q
[18:20] <blackboxsw> n/m strike that, it was originally detected NoCloud, not ConfigDrive. ok so logic remains intact
[18:20] <smoser> well,. remember 4 scenarios
[18:20] <smoser> with user-data and without, template and os_code
[18:22]  * blackboxsw is waiting on reboot and reboot clean
[18:23] <blackboxsw> even though the clean reboot isn't really an intended upgrade path.
[18:29] <smoser> their apt  mirror is nice
[18:29] <smoser> Fetched 83.1 MB in 2s (28.2 MB/s)
[18:30] <rharper> suggests IO is decent as well
[18:30] <smoser> well, eatmydata helps with the io
[18:31] <smoser> and i dont run apt-get any other way :)
[18:31] <rharper> lol
[18:57] <paulmey> rharper: re "is there an ntfs kernel module", I propose to run 'modinfo ntfs" (rc=0) to check that is true and I'll run a util.which on 'mount.ntfs' to see if that exists in $PATH
[18:58] <paulmey> does that sound like the right path?
[18:59] <rharper> paulmey: yes;
[21:31] <paulmey> alright, I'll make it so...
[21:45] <smoser> blackboxsw: I did get the datasource list rioght in ConfigDrive
[21:45] <smoser> 2018-04-27 20:52:41,219 - DataSourceConfigDrive.py[DEBUG]: devices=['/dev/xvdh'] dslist=['ConfigDrive', 'NoCloud']
[21:46] <smoser> yeah, and then as i think....
[21:46] <smoser> your case enabling IBMcloud on a template image without user-data on xenial
[21:46] <smoser> hm.. maybe not
[21:46] <smoser> i htought i had a thoguht on it.
[21:47] <smoser> buti have to go now.
[21:47] <smoser> later.
[21:47] <blackboxsw> later
[21:47] <blackboxsw> yeah and going through the motions here