[08:53] <MICROburst> I created a user X with homedir but 'lock_passwd: true' during install I get annoyed with "ci-info no authorized ssh keys fingerprints found for user X" - how do I get rid of this message?
[13:03] <Odd_Bloke> MICROburst: I'm not sure I follow, why do you want to get rid of that message?
[13:57] <MICROburst> Looks like a config problem. I want to be able to sudo to this user. As opposed to a system account it should have a homedir
[16:05] <MICROburst> is someone here using mounts: to add entries to /etc/fstab?
[16:11] <Odd_Bloke> MICROburst: The only way someone can know if they can answer your question is if you ask it. :)
[16:11] <Odd_Bloke> (Given that cloud-init devs including myself are active in here, someone should be able to!)
[16:17] <MICROburst> Odd_Bloke: Entries added via cloud-init simply do not work. For some reason cloud-init uses TABs in /etc/fstab *facepalm*
[16:19] <blackboxsw> hrm. man page for fstab "Fields on  each  line are separated by tabs or spaces."
[16:20] <blackboxsw> and true cloud-init does separate by tabs it seems https://github.com/canonical/cloud-init/blob/master/cloudinit/config/cc_mounts.py#L498
[16:21] <blackboxsw> MICROburst: I'd be curious about what distro you are running on
[16:22] <blackboxsw> if some distros don't support tabs in /etc/fstab we probably should adjust cloud-init to make the right white-space choice for those elements
[16:23] <MICROburst> It's ubuntu 18.04 Line added was "10.0.10.10:/volume1/backup    /net/backup nfs x-systemd.automount,noauto,comment=cloudconfig  0   0"
[16:24] <MICROburst> ubuntu cloud image.
[16:25] <Odd_Bloke> Yeah, tabs are supported in /etc/fstab AFAIK, so I don't know that that's the issue.
[16:26] <Odd_Bloke> MICROburst: So what does `mount /net/backup` in a shell do?
[16:27] <blackboxsw> uuuuum, so your user-data was this?    https://paste.ubuntu.com/p/YcbRJQzs34/
[16:27] <blackboxsw> MICROburst: I'm curious what the pasted mounts: specific output is when you run 'sudo cloud-init query user-data'
[16:28] <MICROburst> looks like, but I'm not Chad smith
[16:28] <blackboxsw> hehe :) that's me
[16:28] <MICROburst> :)
[16:32] <blackboxsw> soo stock cloud-image and nfs rings a bell. MICROburst is this the symptom you are seeing https://bugs.launchpad.net/cloud-init/+bug/1870370
[16:33] <blackboxsw> and Odd_Bloke's question about what does `mount /net/backup` in your shell do
[16:33] <MICROburst> works.
[16:34] <MICROburst> the odd thing is the other VMs with that config are working too. Very odd...
[16:35] <Odd_Bloke> https://github.com/canonical/cloud-init/pull/473 is the test refactoring PR I mentioned in stand-up this morning.
[16:35] <MICROburst> regarding the pointer to the launchpad: I don't use AWS yet.
[16:40] <blackboxsw> :/,   I think probably need to see a paste of your /var/log/cloud-init.log if possible . I'd expect we'd see a "mount -a" which should have mounted that nfs entry. I'm wondering if we hit something with nfs not responding during initial system boot?
[16:41] <blackboxsw> grabbing the PR Odd_Bloke
[16:49] <rharper> paride: my irc proxy got reset, not sure if you responded and I wasn't here on cloud_tests and lxd 4.0  ...
[17:00] <Odd_Bloke> rharper: I didn't see a response, but paride mentioned in stand-up that he was looking into issues we were seeing in Jenkins that he was anticipating might be the same as yours.
[17:04] <rharper> Odd_Bloke: ok, yeah, it seems to me that lxd image export seems to have changed ... it now expects a filename (not a dir) and it writes a tar.xz file and I think the metadata tarball .. so all of the image import/export bits need updating for 4.0
[17:04] <Odd_Bloke> Fun!
[17:05] <rharper> Odd_Bloke: what a PITA, I was writing a cloud_test for the chrony bug we worked through yesterday;  hoping to contribute an integration test while fixing the bug.    I might see if nocloud kvm is easier ... but need to figure out how to update releases.yaml to point to Centos images
[17:07] <Odd_Bloke> rharper: So I think a short-term resolution would be switching to the 3.x lxd channel while we work on updating the integration?
[17:08] <rharper> Odd_Bloke: ok;  I suspect I'll need to do that in a VM or something; I really loath messing with my existing install (it's a PITA already to get things "happy" )
[17:08] <Odd_Bloke> Or, actually, I'm on 4.2 so maybe even just going back to 4.1 would work?
[17:09] <Odd_Bloke> Or maybe we're on edge on Jenkins ATM, so even with 4.2 we might not be broken?
[17:11] <rharper> Odd_Bloke: well, let me just file a bug with details;
[17:11] <rharper> I'm on latest/stable ; 4.2
[17:14] <blackboxsw> Odd_Bloke: minor Change requested and we can land https://docs.pytest.org/en/2.9.2/example/markers.html#custom-marker-and-command-line-option-to-control-test-runs
[17:14] <blackboxsw> oops paste fail
[17:15] <blackboxsw> https://github.com/canonical/cloud-init/pull/473#pullrequestreview-441880118
[17:27] <rharper> https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1886080
[17:41] <Odd_Bloke> blackboxsw: Good catch on that nit, thanks!  Fix pushed up.
[17:43] <blackboxsw> Odd_Bloke: rharper lucasmoura and falcojr I'm off tomorrow and CDOqa just came in with cloud-init test results as success for SRU into ubuntu X, B , E, F. Upstream doesn't release on Fridays, but I'd like to ping the SRU vanguards in #ubuntu-release  as soon as CDO logs are attached to see if we can't get this approved for today. I'd need folks to be aware of the update/publish in case of bug reports tomorrow.
[17:43] <blackboxsw> does that sound good/
[17:43] <blackboxsw> or shall we wait for Monday
[17:45] <blackboxsw> I'm imagining a lot of US-based folks aren't going to be around tomorrow
[17:46] <Odd_Bloke> blackboxsw: We have and will only have CDO QA results for bionic, right?  Do we need to resolve that inconsistency with our SRU exception before asking for release?
[17:46] <Odd_Bloke> Yeah, I'd hold off regardless, given that tomorrow's a US holiday.
[17:47] <Odd_Bloke> (Speaking as someone who lives in Canada. ;)
[17:47] <blackboxsw> heh. ok will hold. and yes, I'll ping about xenial results, typically CDO qa doesn't do non-LTS (and I'm not certain where they are as far as focal)
[17:52] <blackboxsw> merged https://github.com/canonical/cloud-init/pull/473
[18:03] <rharper> blackboxsw: good luck with the release today;  Monday isn't terrible either