/srv/irclogs.ubuntu.com/2018/08/10/#cloud-init.txt

smoserblackboxsw: i dont know what that error checkign signature is.03:35
smosermaybe you dont have trusted your own key?03:35
smoseri do not set BIN_NMU_TIMESTAMP03:35
smoserI think this is the only things i have"03:35
smoserhttp://paste.ubuntu.com/p/gYKS7skDGd/03:36
blackboxswYeah I hadn't earlier verified my key in launchpad. I have since pushed and verified.13:33
blackboxswsmoser: forgot to ask about the lintian error that I saw which complained about debian/cloud-init.templates not having po translation files15:40
blackboxswE: cloud-init source: untranslatable-debconf-templates cloud-init.templates: 615:40
blackboxsw16:13 E: cloud-init source: not-using-po-debconf15:40
blackboxswdo we care?15:40
blackboxswenough to ignore the lint on that template file? or setup the pot files instead15:41
smoseroh yeah... ENOCARE :)15:41
blackboxswexcellent15:41
smoseri'd like to get rid of it, but...15:41
smosernot a big deal.15:41
smoserwe could and arguably should add potential translations for that i guess.15:42
blackboxswSoy increíble en la traducción15:50
smosermy keyboard doesn't have one of those funny i or o keys15:50
blackboxswjust a couple of curls away against google.translate15:50
smoser:)15:51
blackboxswsmoser: or rharper if there is a chance today for the azure branch landing, then I can easily re-upload cloud-init :) https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/35266016:20
blackboxswshameless self-interest on that branch :)16:20
smoserblackboxsw: i had asked about 'remove_ubuntu_network_config_scripts' in _get_data()16:25
smoserand suggested in .activate16:25
blackboxswSmoser I responded I thought that activate was too late as we are generating network config in init local timeframe and we would collide with the cloud image's seeded netplan file16:32
blackboxswSo we need something to clean out the /etc/netplan/90-azure-hotplu.yaml before we kick netplan16:36
smoseroh. ok. yeah, that is why we should talk on the MP :)16:36
smoserrahter htan me asking out of band16:36
smoser:)16:36
blackboxswYeah... and me deleting the original merger proposal broke that :/16:36
blackboxsw... bad solution to a stale  visual diff with merge conflict markers 《《16:37
smoserblackboxsw: respondoned16:58
blackboxswrharper  one of smoser's comments on my branch which adds the ds-identify detect_Azure logic to DataSourceAzure._is_platform_viable was that the following test is not really valid  has_fs_with_label "rd_rdfe_*" && return ${DS_FOUND}20:04
blackboxswI just validated that adding data diskss on azure instances resulted in the following partitions and labels20:05
blackboxswsudo python3 -c 'from cloudinit.util import blkid; print(["%s:%s" % (k, v.get("LABEL", "")) for k,v in blkid().items()])'20:05
blackboxsw['/dev/sda1:cloudimg-rootfs', '/dev/sda15:UEFI', '/dev/sdb1:', '/dev/sdc1:', '/dev/sda14:']20:05
blackboxswubuntu@SRU-worked:~$20:05
blackboxswso most disks have empty labels.  /me wonders about the initial dvd/cdrom that shows up on azure during first boot... maybe it had that label20:06
blackboxswmy question was...20:06
blackboxswif we thinkg the re_rdfe_* prefix is not valid for DataSourceAzure._is_platform_viable, should I also drop it from ds-id20:06
blackboxswif we are thinking the re_rdfe_* prefix is not valid for DataSourceAzure._is_platform_viable, should I also drop it from ds-id20:06
blackboxswthe thing that stinks about irccloud is that if my browser is sucking wind, it timesout on keyboard character input20:07
rharperblackboxsw: that's prolly a question for the MS folks w.r.t  cdrom20:08
rharperblackboxsw: can you confirm if /dev/sr[0,1] has anything in it ?20:08
rharperI don't think we can yet drop it until we know that it's invalid;  we usually have a collection of information that jointly confirms which platform we're on20:09
smoserblackboxsw: so the dvd/cdrom definitely used to start with 're_rdfe_'20:15
smoserits possibly obsolete now.20:17
smoserand i recall bein told that it might be.20:17
smoserbut as in the 'dscheck_Azure' function "header", you can see that is where it came from20:18
rharperblackboxsw: AFAICT the check is still valid; we don't know of another cloud where there are (iso) filesystems with such labels;  they may not be in used in your instance20:21
rharperbut it's possible in other azure deployments (AZ, or private)20:21
rharperit may still be used20:21
rharperblackboxsw: what was smoser objecting to w.r.t the label check being invalid ?20:21
smoserwell, butthat only ever gets considered if azure asset tag is not present.20:21
rharpera fallback20:21
rharpersure20:21
smoserand we really should have azure asset tag present everywhere.20:21
rharperyes20:21
rharperthat makes sense20:22
blackboxswSo smoser should I drop that filesystem prefix check from ds-id or leave our fallback in both places20:52
smoserand if not... well, i think its completely unrelated to your changes.20:55
smoserso if you want you can do that in a separate MP and we can just take that in first.20:56
blackboxswwoot! +1 . let's do that as I'm itching to get an upload in20:57
smoserhttps://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/35292120:57
smoserthats my no-unit test oracle ds20:57
blackboxswnice smoser will play with it20:57
blackboxswsmoser: I'll pull out the prefix check from the python is_viable_platform20:58
blackboxswthen we only have it in one place to remove20:58
blackboxswI won't touch ds-id logic until we confirm otherwise20:59
blackboxswok pushed my branch. it can sit until monday as it's EOW for you gents21:05

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