[08:53] <pasasap_> I am back. I am running that on openstack of my team.
[08:53] <pasasap_> http://paste.ubuntu.com/24053660/ btw
[14:04] <pasasap_> If I pass to runcmd some commands, ie. Ansible, then even if I try to run as ubuntu user, then user is root. Can I force that cmd is launched as non root user?
[14:04] <smoser> pasasap_, what openstack ?
[14:05] <pasasap_> Neutron.
[14:06] <smoser> pasasap_, ok. so in that paste above 2453660
[14:06] <smoser> you have only Ec2 datasource enabled.
[14:06] <smoser> i suspect you possibly have a config drive attached.
[14:06] <smoser> and that cluod-init would/should get networking configuration from taht config drive.
[14:07] <smoser> then... either you have a broken metadata service (which used to be quite common on openstack with neutron)
[14:07] <pasasap_> It one time can get metadata, another time cannot.
[14:07] <smoser> or you have no metadata service.
[14:07] <smoser> in the log there, you have only configured cloud-init to look for Ec2.
[14:08] <smoser> do you have a config drive attached do you know ?
[14:08] <pasasap_> I dont know, possibly not.
[14:08] <smoser> ie, there might be a small disk attached.
[14:08] <smoser> so definitely  you need to fix cloud-init config so that it looks for OpenStack and ConfigDrive
[14:08] <pasasap_> That was installed with packstack if I remember.
[14:08] <smoser> (run dpkg-reconfigure cloud-init)
[14:09] <smoser> i dont know about packstack, i dont particularly have an interest in knowing about image building tools...
[14:09] <smoser> i generally think they're silly
[14:09] <smoser> we make images that "just work", and if they dont then we will fix them.
[14:09] <smoser> (i view building images the same way as I view building glibc or kernel... sure you can do it, but why?)
[14:10] <smoser> so i'd much rather focus on trouble shooting the official ubuntu images to start.
[14:10] <smoser> then you have somethign that works and you can compare.
[14:10] <pasasap_> I tried official image, xenial-server-cloudimg-amd64-disk1.img also  has the same problem.
[14:10] <smoser> with regard to running as non-root, cloud-init runs as root, so runcmd runs as root.  you can execute things as other users using 'su' or 'sudo'
[14:11] <smoser> here is 'my-userdata' that i launch vms with generally
[14:11] <smoser>  http://paste.ubuntu.com/24058888/
[14:11] <smoser> see 'as_def_user' for a way to run things as non-root
[14:12] <smoser> its more complicated then you need, but basically it goes looking for a user in a list (smoser , ubuntu, azuser....) and executes as that user... the reason for the searching is that some clouds have different default user and this just finds whatever that user is.
[14:12] <smoser> pasasap_, the official image may well have a problem for you, but it will have more than just the Ec2 datasource enabled.
[14:12] <smoser> so that is at least one problem that we can avoid trouble shooting.
[14:12] <smoser> that make sense ?
[14:13] <smoser> lets get *something* working, then you can have a reference that works and figure out the differences.
[14:16] <pasasap_> OK, but which datasources should be enabled?
[14:25] <smoser> well, in the official image, all of them are
[14:25] <smoser> but most likely you need ConfigDrive and OpenStack
[14:26] <smoser> but ... lets just go with the official image.
[14:26] <smoser> i suggest:
[14:26] <smoser>  a.) download that to an ubuntu system some where
[14:27] <smoser>  b.) backdoor it: (run backdoor-image --user=backdoor --password-auth --password=passw0rd your.image)
[14:27] <smoser>  http://bazaar.launchpad.net/~smoser/+junk/backdoor-image/files
[14:27] <smoser> then upload that.
[14:27] <smoser> then if it fails, you'll still be able to ssh in as 'backdoor' with 'passw0rd'
[14:28] <smoser> and then you can poke around that way and see what failed.
[14:43] <smoser> pasasap_, does that make sense ?
[14:44] <pasasap_> Yes.
[20:10] <rharper> smoser: around?
[20:10] <smoser> here
[20:10] <rharper> wanted to hangout for like 10 minutes to talk networkd during boot issues
[20:12] <rharper> https://hangouts.google.com/hangouts/_/canonical.com/hangout-rharper?authuser=1
[20:13] <smoser> ok
[20:13] <smoser> can i have 5 m inutes ?
[20:14] <smoser> htne meet
[20:14] <rharper> yeah
[20:24] <smoser> 3:30 (2:30 central)
[20:24] <smoser> i'll join then
[20:24] <smoser> rharper, https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/318282
[20:25] <smoser> if you want to take a read of that i'd appreciate it.
[20:25] <smoser> better commit messages needed, and some doc, and test :)
[20:25] <rharper> ok
[20:30] <rharper> smoser: I've got 5 mins then I'll be back at the top of the hour
[20:33] <rharper> I'll re-ping in 30
[20:33] <smoser> ok.s orry
[20:56] <rharper> https://hangouts.google.com/hangouts/_/canonical.com/hangout-rharper?authuser=1
[20:59] <rharper> smoser: ^^
[21:25] <smoser> rharper, https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1667735
[23:34] <stanguturi> I am trying to build cloud-init deb package and got 'Unmet build dependencies: python3-coverage' error. Any idea how I can get this resolved