[00:16] I am new to lxd and want to configure the networking to be a true bridge in that I want my guests to get v4 addresses via DHCP and v6 addresses via SLAAC [00:16] once I get this working I'm planning on having multiple interfaces on my host that binds to different VLANs (and thus multiple bridges, I would assume). [00:18] I created a test guest and it created a vethDMY03 interface, but the guest doesn't have a v4 or a v6 address [00:23] I went into the guest and set inet dhcp and inet6 auto in interfaces.d/50-cloud-init.cfg [00:54] Hi, all. Not sure if there's a better room to reach the team that handles Ubuntu cloud images, but `vagrant box add ubuntu/xenial64` is currently failing with a 404 when fetching the box. [00:54] Odd_Bloke: --^ not sure if that is the same issue you were helping with earlier [01:11] runelind_q: did you create your own br0 bridge device, add your eth0 to it and tell lxd to use that br0? [01:12] runelind_q: this is a little dated, but may help: http://jrwren.wrenfam.com/blog/2015/11/10/converting-eth0-to-br0-and-getting-all-your-lxc-or-lxd-onto-your-lan/ [01:17] hi [01:18] why loop [01:18] , lp and [01:18] rtc are missing from /etc/modules? [01:18] on ubuntu 16.04? [01:19] why loop, lp and rtc modules are missing from /etc/modules on ubunut 16.04? [01:23] jrwren: i thought lxdbr0 was the new hotness? [01:24] runelind_q: it is, but that is a nated bridge interface which serves dhcp from a private range via dnsmasq. [01:24] runelind_q: your question made it sound like you wanted to bridge to your local lan. [01:24] i did [01:25] ok, i will use a regular bridge [01:36] Guys, how can I run some command automatically on every boot? [01:37] let me count the ways [01:37] you want to run it as root or a regular user? [01:37] Yuri4_: a crontab entry with @reboot isntead of `m h dom mon dow` works well [01:38] that's what I was going to recommend. [01:38] runelind_q, as root [01:38] sudo crontab -e [01:38] then do what jrwren recommended. [01:38] jrwren, I'm very new to linux. [01:38] Wher do I put that entry? [01:40] Hmmm. Google says that crontab is timebased [01:40] I only need it run once after boot [01:40] Is this good solution? [01:43] Guys? [01:48] yeah, if you set it to @reboot instead of a time, it will run the script on boot [01:49] runelind_q, but it will run only after user logins? [01:50] I'm on server and need to run that command when server restarts [01:50] no, it will run during the boot process, even before a user logs in. [01:50] jrwren: I'm assuming I want to swap eth0 for ens160 which is my actual interface name when I make changes to /etc/network/interfaces [01:50] ? [01:51] runelind_q: yes. [01:51] runelind_q, I'm new to linux. So how do I execute on every boo, let's say "sudo mount_folder_x"? [01:51] boot* [01:51] oh, if you want to mount something, you want to edit /etc/fstab [01:52] runelind_q, no, I absolutely don't want to do that [01:52] it already broke to servers [01:52] two* [01:53] I just want to run it on every reboot [01:53] https://help.ubuntu.com/community/CronHowto [01:53] And if it fails it doesn't break servers [01:53] learn how to do it without "breaking" the servers ;] [01:53] look into the part about @reboot [01:53] jrwren, I did everything correctly. I belive there is a bug in service I'm usuing [01:53] probably not [01:54] jrwren, I'm very new to linux and can't understand that manual. I've been reading it for 10 min. Could you provide an example, how to do it, please? [01:54] I don't uderstand how to do it [01:54] the link I provided is very thorough. [01:56] runelind_q, It is thorough, but I'm a noob. I don't understand what it saying [01:56] could you just give an example, please? [01:56] I'm windows sysadmin, not linux [01:57] Yuri4_: sorry, i've been doing this for 20yrs, if the docs at https://help.ubuntu.com/community/CronHowto aren't readable, I'm afraid i cannot help. [01:57] sudo crontab -e [01:57] then @reboot /path/to/script [01:57] runelind_q, thank you! [01:57] jrwren, see how it's done? [01:57] runelind_q, you are the best! [01:57] I do see. [01:57] Thanks. [02:09] runelind_q, I did sudo crontab -e then added @reboot /home/prouser/startup/command [02:09] but it doesn't execute [02:10] did you set chmod +x /home/prouser/startup/command ? [02:10] runelind_q, no [02:11] runelind_q, thank you [02:15] jrwren: ok, my guest gets a v6 address, but I can't ping6 it. [02:15] I set v6 forwarding =1 [02:18] runelind_q, I added 2 commands for @ reboot. sudo mount -t cifs //myaccountname.file.core.windows.net/mysharename ./mymountpoint -o vers=3.0,username=myaccountname,password=StorageAccountKeyEndingIn==,dir_mode=0777,file_mode=0777 - this doesn't work [02:18] runelind_q: a routable address, not just link local? [02:18] but sudo mkdir - works [02:19] jrwren: yeah, routable [02:19] runelind_q: I'm not familiar with SLAAC. I only use radvd [02:19] jrwren: SLAAC is the autoconfigured addresses from radvd [02:20] Yuri4_: put it into a script, run chmod +x on the script, then manually execute the script to make sure it works. [02:20] put the full path to all commnds [02:20] like /bin/mount instead of mount [02:21] remix_tj, yeah it's full path. 1 command works and anothe doesn't [02:21] how do I mannualy execute the script? [02:24] runelind_q, when I do it mannualy both command works [02:24] but on boot only 1 works [02:25] this one doesn't sudo mount -t cifs //myaccountname.file.core.windows.net/mysharename ./mymountpoint -o vers=3.0,username=myaccountname,password=StorageAccountKeyEndingIn==,dir_mode=0777,file_mode=0777 [02:26] you don't do sudo, just mount, since it runs as root [02:26] and make sure you have /bin/sudo in there. [02:26] and this should really really really really be done in fstab [02:27] runelind_q, when I do it in fstab my serve stops booting [02:27] server* [02:33] runelind_q, still doesn't work [02:33] I hade sudo mkdir though and it executed fine [02:34] I dunno man. [02:34] sounds like you need to hire someone to come over. [02:39] runelind_q, that's me who have been hired to do that [02:39] is there another option to do that on each boot? [02:39] not cron? [02:40] nope, hire someone else as a subcontractor. [02:42] did you add the _netdev flag? [02:43] Hi all. Sorry if anyone responded recently. I had to travel some. Any word on the ubuntu xenial64 vagrant images being missing? [02:49] net.ipv6.conf.all.forwarding=1 [02:49] net.ipv6.conf.br0.accept_ra=2 [02:49] net.ipv6.conf.default.forwarding=1 [02:50] guest gets a v6 address, but I can't ping it. [02:56] runelind_q, I fiexed it by adding sleep 30; before the command [02:56] thank you for the help! [02:56] must be a dns issue [02:56] patdk-lap, maybe some durty hack to change server IP after boot? [02:57] when I put it into FSTAB it broke both my server that took 8 hours to set up [03:13] I need to install fure-utils on ubuntu 16.04, any help? [03:13] fuse-utils sorry [04:00] furry-utils [05:37] FYI, I filed https://bugs.launchpad.net/cloud-images/+bug/1590647 just so this isn't lost [05:37] Launchpad bug 1590647 in cloud-images "xenial64 vagrant boxes are unavailable from Atlas" [Undecided,New] === gms is now known as Guest98013 === Guest98013 is now known as _gms === stikky is now known as _gms [06:58] hi all, i've got sssd+ad working for ssh, login & sudo, but for the life of me i cant get "smbclient -k" or automount to work for any passwordless access to smb fileserver. just get a timeout. all ok if i skip the '-k' and manually enter password, but automount won't work, and multi-user access in fstab requires a passwordless method. anyone have this working? [07:41] Is there a significant difference between Debian partitioning and Ubuntu partitioning, as my debian preseed file used on ubuntu 16.04lts keeps on asking me to confirm the partitions manually [07:49] nacc: Thanks for the pointer to that Vagrant bug. :) [08:00] is there any way to prevent the installer from asking me to confirm manually the partition setup layout if it is already defined in an expert layout? [08:05] toshywoshy: this is what we use for our trusty and xenial nodes: http://paste.ubuntu.com/17138951/ [08:06] frickler: thanks, in the second partition you have '-1' as the maximum value, is that better than having '1000000000'? [08:08] toshywoshy: IIUC it will use the maximum available size, I'm not sure what happens if you use a value too large for your current disc [08:11] toshywoshy: I did some searching on the net to get that part together some years ago, most of the rest of the file is still the original https://github.com/puppetlabs/razor-server/blob/master/tasks/ubuntu.task/preseed.erb [08:18] frickler: I solved it based upon your preseed file, the solution was adding "d-i partman-auto-lvm/guided_size string max", which is wat the installer was nagging me about to confirm manually, thanks again [08:21] toshywoshy: yw === _degorenko|afk is now known as degorenko [08:41] so, is uptrack really necessary / makes sense on a private server which host various public services with >100 users? [08:52] hello [08:52] anybody wake? [08:54] Teme_, It's lunch time here man :) [08:54] aah, sorry to be a bother then ;) [10:03] coreycb, ddellav: ok so updated oslo.messaging to 5.2.0 - needed for keystone [10:03] fixed versions for keystone; should build through shortly [10:03] there where some network connectivity issues overnight - so re-ran some failing builds that got impacted by that [10:04] also pushed a small fix to pkgos-generate-snapshot to deal with .0b1 correctly -> will map to ~b1 for package version compatibiltiy [10:05] still tripping on some networky type problems but almost clean [10:05] I also took a look at the nova-lxd failure - its due to some missing mocking [10:30] jamespage: regarding https://bugs.launchpad.net/bugs/1564812, the main issue is that there is one log-file generated per rootwrap command executed, i.e. one file every 2 seconds for some neutron agents. and they never get cleaned up it seems. [10:30] Launchpad bug 1564812 in nova (Ubuntu) "Disable sudo io logging for rootwrap" [Wishlist,Triaged] [10:31] frickler, a file per command? [10:31] or a log entry per command? [10:32] jamespage: no, each sudo invocation generates a new file [10:32] * jamespage checks an install [10:33] frickler, I'm not seeing that on a openstack install we have for QA [10:33] all sudo calls go to /var/log/auth.log [10:33] jamespage: you need to add "Defaults log_output" to your /etc/sudoers to trigger the issue, default installation doesn't log anything [10:35] frickler, well the default logs all commands and output to /var/log/auth.log [10:36] frickler, no you are right - output is not logged by default [10:36] only input [10:37] jamespage: yes, but as part of our hardening, we add the above options, so that everything a user does e.g. within a "sudo -i" session, can be looked at afterwards with sudoreplay [10:37] frickler, ok so your proposed change does not alter the logging of commands to /var/log/auth.log [10:38] it just stops the creation of the individual files that log_input and log_output turn on? [10:38] if that's the case I misunderstood the problem - apologies... [10:38] * jamespage thinks [10:40] jamespage: at least that is my understanding of the impact of the change, yes [10:41] Wouldn't turning off output by default be surprising to others who turn it on globally and expect all commands to follow? [10:41] It seems to me that it would be less surprising for people who choose to turn global logging on to also disable it for specific cases where it is not wanted. [10:43] rbasak: the problem is that you have to do it on the same line, so we would have to patch again this after every package update [10:43] frickler: it's a conffile. Your modifications should be maintained by packaging. You'll only have to handle it if the packaging changes the conffile it ships. [10:44] frickler: even if that weren't true, the right fix would be to have some better override features in sudo. [10:45] I just think that this kind of change just prompts another bug report saying the opposite. It's not the default configuration, so the fix should be to make it easier to get the behaviour you want, rather than changing the default for something that isn't even a default. [10:45] But anyway, up to jamespage. [10:48] hence my last /me thinks [10:49] ;0) [10:51] rbasak, frickler: this is tricky - I would tend to think it might be better set overrides per user that needs to be excluded [10:52] Can sudo take that instruction from a separate .d file? In that case that would be the perfect solution - no changes in packaging needed and frickler can add it locally without much concern for what happens on packag eupdates. [10:53] rbasak: it can [10:53] I've often used seperate files, eg: normal.rules webowners.rules etc etc [10:53] just make sure they don't conflict as ordering is not good [10:54] The files would have rules that overlap. Hence my question. [10:54] rbasak, looking now [10:54] that can cause a problem then, I believe the most restrictive rule is honoured [10:56] something like: [10:56] Defaults:nova !requiretty,!log_input,!log_output [10:56] might work ok [11:00] yes that does work fine - so I still can set global log_ouput, log_input, but nova/neutron whatever gets excluded [11:00] but still included in auth.log [11:00] frickler, ^^ that might fit your requirement [11:02] you can skip !requiretty as well as that's set in the pkg provided sudoers [11:05] commented on bug as well [11:08] rbasak, you'll have an opinion on https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1585794 just as I do [11:08] Launchpad bug 1585794 in nova (Ubuntu) "dpkg unable to configure nova-common if user nova is in ldap" [Undecided,New] [11:10] system users in ldap sounds like bad karma to me... [11:11] however that's not the actual bug here... [11:12] * rbasak looks [11:15] jamespage: is the bug caused by there being a system user in LDAP, or just some normal user in LDAP that happens to be called "nova"? [11:16] jamespage: the pattern in that postinst is the normal one. If something needs changing, it'd probably need change across the board (ie. a wider collective decision). [11:16] rbasak, this issue is that the postinst tries todo usermod on the nova user for a switch in group way back before 12.04 [11:16] nobody -> nova [11:16] jamespage: ah. That I did question but didn't realise it was relevant. [11:16] that won't work with an ldap provided user [11:17] that said I think ldap for system users is a little bonkers... [11:17] jamespage: I'd do that on an upgrade path only (compare to $2 etc) [11:17] I didn't think of that from an LDAP perspective though, just a "stepping on the user's customisations unnecessarily" perspective. [11:19] Always good for upgrade path code to be conditional on the required upgrade versions since then it can be dropped eventually and make things simpler, as well as reduce the likelyhood of some kind of unpredicted conflict when the upgrade path code isn't needed. I guess this is one of those cases. [11:19] rbasak, tbh that all applied to day 0 packaging anyway [11:19] I agree that an LDAP system user is pretty broken though, but that's not my justification. [11:20] Most packaging I've seen would work with an LDAP system user though, if the user knows what he's doing. In that postinsts just leave it alone in that case, and silently accept failure to remove on postrm I think. [11:20] jamespage: not sure what you mean? [11:21] rbasak, all of the part of the maintainer script was due to mistakes made prior to 12.04 release... [11:21] that's pretty much the earliest point we support upgrades from now [11:21] jamespage: ah, I see. So you could just drop the usermod? [11:22] just did :-) [11:23] :-) === iberezovskiy|off is now known as iberezovskiy [11:39] jamespage, ddellav: all of the newton b1 core packages from our end are backported [11:40] jamespage, still need this to land I believe before testing right? https://review.openstack.org/#/c/326597/ [11:55] coreycb, is that the keystone one? [11:55] jamespage, yep === JanC is now known as Guest27912 === JanC_ is now known as JanC === sarthor_ is now known as sarthor [12:59] stupid question [12:59] but how do I allow access to apache only from my internal network [12:59] no external access [13:11] ddellav, testing for bug 1546116 is complete. can you tag the bug as verification-done and verification-liberty-done? [13:11] bug 1546116 in manila (Ubuntu Wily) "[SRU] manila share process init script is missing" [Undecided,Fix committed] https://launchpad.net/bugs/1546116 === JanC_ is now known as JanC [13:16] nacc: do you want bug 1590623 sponsoring? [13:16] bug 1590623 in php7.0 (Ubuntu) "Drop dh-php from Recommends to Suggests" [Undecided,New] https://launchpad.net/bugs/1590623 [13:26] coreycb ok, i'll try [13:30] coreycb, ddellav: nova branch build failed fixed; patch accepted upstream! [13:31] jamespage, that must have landed quick [13:31] over a week [13:31] it was just some assert call badness [13:31] https://review.openstack.org/#/c/318568/ [13:35] jamespage, ah that one [13:35] coreycb, have fix up for nova-lxd as well as soon as rockstart or zul are around... [13:35] rockstar rather.. [13:35] doh [13:35] jamespage, oh awesome [13:36] jamespage: yeah no one can approve patches yet [13:36] zul, ha [13:36] zul, just ask someone in -infra to add you and rockstar to the groups [13:36] unless you have already done that... [13:36] yolanda is alway a good egg :-) [13:36] jamespage: i think rockstar already has [13:36] oh ok [13:38] coreycb, jamespage: hey [13:38] can I try to deploy newton on xenial? [13:38] sure [13:38] how? [13:38] EmilienM, ppa:openstack-ubuntu-testing/newton [13:39] ok cool [13:39] jamespage: did you deploy already? [13:39] b1 is working its way into the UCA - but that PPA has branch builds for most projects [13:39] EmilienM, yes [13:39] cool [13:39] EmilienM, you'll probably trip over the changes we've made to the keystone package for wsgi/apache2 support [13:39] well you might [13:39] /etc/apache2/sites-enabled/keystone.conf [13:40] jamespage: ok so I use ppa but in a close future I can use uca, right? [13:40] * jamespage crosses fingers... [13:40] EmilienM, coreycb or ddellav will email the openstack-dev ML once its all up and verified [13:41] ok [13:41] coreycb, btw I'm going to push all of newton staging -> proposed right now [13:42] jamespage, +1 [13:42] we may as well test proposed as no one else is just yet... [13:43] jamespage: so should I wait that you push and then I test it? [13:43] well, let's try the ppa this morning and ping me when you pushed in proposed I'll test it too [13:43] EmilienM, up to you - will take several hours to work through [13:43] ahhhh [13:43] ppa :) [13:43] if you want to start now use the PPA [13:44] EmilienM, we've done a bit of rejig in the openstack-dashboard packaging as well; the ubuntu theme is just installed alongside the other themes, and is end user selectable. [13:44] DEFAULT_THEME='xxxx' to switch the default between options - default|ubuntu|material [13:45] mhh ok [13:45] iberezovskiy: ^ fyi [13:45] * EmilienM take notes on https://etherpad.openstack.org/p/puppet-openstack-xenial [13:46] jamespage: so you put a default vhost for keystone, right? [13:47] EmilienM, yah - for admin and public endpoint ports [13:47] mhh ok [13:47] it's a bit annoying [13:47] EmilienM, is based on the one keystone provides in httpd [13:47] for people using deployment tools like chef/puppet/ansible [13:47] https/wsgi-keystone.conf [13:47] most of people deploy their own vhost [13:47] why not in site-available? [13:47] it would be better imho [13:48] EmilienM, for those not using puppet/chef/ansible [13:49] it's like zigo does, forcing stuffs [13:49] I don't like it... but that's my opinion... [13:49] our keystone module already manage vhost with the capacity of configure the vhost [13:49] so we'll have to drop this file... [13:49] and chef/ansible will have to do the same [13:49] people should be able to enable the vhost themselves I think [13:50] it's very intrusive to add a vhost & enable it by default [13:50] jamespage, why did you decide to change this behavior? it always was at sites-available as I know [13:50] degorenko, iberezovskiy: FYI I updated https://etherpad.openstack.org/p/puppet-openstack-xenial with the notes I took from ^ [13:50] right, this change is not cool [13:51] what are we talking about [13:51] keystone vhost [13:54] keystone has never shipped a sites-avaliable; as there is no longer a eventlet based daemon, we have to provide an enabled daemon in someway [13:54] * jamespage ponders this... [13:55] I just say, that most of people won't use this vhost in production, because everybody does vhost tunning. In puppet-keystone, we allow such tunning since you can configure everything in the vhost (SSL, workers, etc) [13:56] so you better disable it by default and people will enable it before starting apache2 [13:56] I appreciate that... [13:56] I think providing a vhost is awesome [13:56] it really helps people to easily deploy keystone [13:56] but enabling it by default is a bit too much and I think most of people know how to enable a vhost, and if they don't lol. Don't continue OpenStack deployment :) [13:57] providing of vhost is good, but please do not force to use it [13:57] I'm actually considering whether we should do the same with the dashboard as well - we should be consistent... [13:57] anyway, I kicked off a CI job with PPA, I'll give you feedback as soon as jobs finish [13:57] coreycb, what do you think? [13:58] jamespage, we provide init scripts by default, so it seems like a default vhost makes sense [13:58] jamespage, I think we'll get complaints either way [13:59] I just hope the packaging does not start apache by default [13:59] ie: apt-get install keystone [13:59] EmilienM, yes it does [13:59] ... [13:59] because it installs apache2 [13:59] EmilienM, just like horizon [14:00] ansible/chef/puppet folks will have big issues [14:00] for orchestration [14:01] this is really about which expectations we break [14:01] I mr end user install keystone, and nothing is running [14:01] unlike pretty much everything else in the archive.. [14:01] * jamespage ponders this some more... [14:04] EmilienM, ftr I think 'big issues' is over egging it a bit - disabling a site is not that hard :-) [14:05] yes you will have to make a change to adapt to the changes in packaging behaviour... [14:07] my concern is that ubuntu packaging is getting more and more intrusive [14:08] I don't think production deployments need you to start apache, they have orchestration tools and they need to decide when they start services [14:08] but anyway, yeah we can workaround all-the-things, I just say it's getting worse over the releases. [14:08] EmilienM, do you have examples? [14:08] coreycb: containers [14:09] coreycb: or people who use puppet/ansible/chef/whatever [14:09] EmilienM, containers where? [14:09] they want to wait before starting apache, maybe they need to add more vhosts before [14:09] EmilienM, do you have examples of where we're getting worse? [14:09] coreycb: keystone is the right example I guess [14:10] as it's a core service that everyone use [14:10] EmilienM, enforced starting of services is a core part of the debian packaging requirements since over a decade ... thats not an ubuntu thing at all [14:10] has been like that forever for debian packages [14:10] great, if everyone likes it then I'm wrong [14:10] * ogra_ didnt say he likes it, but it is simply like that forever and it is a debian requirement, not an ubuntu one [14:11] it's not because it's here forever that we can't change [14:11] RDO packaging was a mess a few years ago [14:11] (RDO = Red Hat OpenStack packaging) [14:11] what i'm saying is that you have to change debian [14:11] and we changes lot of things, and now things are much better [14:12] anyway, I'm trying to satisfy OpenStack community as a Project technical lead of Puppet modules [14:12] EmilienM: puppet is broken wrt. starting daemons. It takes over running services; it should use policy-rc.d. [14:12] and as a PTL I'm trying to engage work with other communities to make things better [14:12] our CI deploys Ubuntu jobs so I'm here [14:13] EmilienM: and if it did, then a default enabled or disabled "site" would make no difference. Your puppet module would just force it one way or other before starting the service. [14:13] sure, we'll adapt [14:13] just giving feedback, take it it's free ;-) [14:14] We can't have defaults one way for interactive users and the other way for automation. It makes sense for automation to override things as needed rather than the user because that can be...well, automated. [14:15] Debian provides the hook necessary to do it. Automation should use it. [14:20] rbasak: just pushed the new merge.v1 tag [14:26] caribou: thanks! I'm out of time before meetings and EOD today. I'll try to look tomorrow. [14:26] rbasak: no worry & thanks for looking at it [14:56] stgraber: FYI, bug 1590747 - is CI broken somehow? [14:56] bug 1590747 in lxd (Ubuntu) "images.linuxcontainers.org Debian sid image is broken" [Undecided,New] https://launchpad.net/bugs/1590747 [14:56] rbasak: if you could, that would be great, just added ~sponsors (re: 1590623) [14:57] Odd_Bloke: np, just figured the context was similar enough (re: vagrant bug) [14:58] nacc: Yep, much appreciated! [14:59] nacc: done [14:59] rbasak: we don't test those images, so CI isn't broken, Debian most likely is :) [14:59] rbasak: thanks! [15:00] rbasak: that error seems to indicate that debootstrap succeeded but didn't give us a rootfs with a working /sbin/init :) [15:00] stgraber: one might argue that not testing the images means that CI is broken :) [15:00] But fair enough. [15:06] root@dakara:/var/lib/lxd/containers/foo/rootfs# ls /sbin/init -l [15:06] lrwxrwxrwx 1 root root 20 May 12 05:39 /sbin/init -> /lib/systemd/systemd [15:06] root@dakara:/var/lib/lxd/containers/foo/rootfs# ls -lh lib/systemd/systemd [15:06] ls: cannot access 'lib/systemd/systemd': No such file or directory [15:06] rbasak: ^ [15:06] so yeah, looks like Debian sid is busted today [15:06] kinda surprised that debootstrap succeeded though :) [15:07] stgraber: you checked your host for existence of /sbin/init, not the guest. But yeah, it's broken :) [15:08] s/guest/image/ [15:08] rbasak: oops [15:09] root@dakara:/var/lib/lxd/containers/foo/rootfs# ls sbin/init -l [15:09] ls: cannot access 'sbin/init': No such file or directory [15:09] it's even worse than I thought :) [15:09] how the hell is debootstrap succeeding without an init system :) [15:09] stgraber: well now at least you see the same behaviour I do :) [15:10] confirmed that debootstrap didn't feel like picking an init system, no error reported during bootstrap... https://jenkins.linuxcontainers.org/view/All/job/lxc-template-debian/arch=amd64,release=sid,restrict=lxc-priv,variant=default/986/console [15:11] so yeah, that might surprise a few people :) [15:14] Hmm. deboostrap hasn't changed recently. === HouseMD is now known as HugeEgoSorry [15:50] coreycb, we need to not backport packages which have not changed since xenial (it creates conflicts in the UCA sync) [15:51] jamespage, oops, ok [15:52] jamespage, does anything need fixing? [15:52] coreycb, deleting offenders now [15:52] jamespage, thanks === HugeEgoSorry is now known as GitGud === GitGud is now known as TheRealGitGud === degorenko is now known as _degorenko|afk [16:25] For reasons I will keep to myself :) I want to install Mitaka OpenStack components on Xenial without tooling. But, the cloud archive says only Trusty is supported. What methods can I use, short of building from source? [16:26] zul: Can you help me with this Q? ^ [16:37] mrjazzcat: what do you mean by "without tooling"? mitaka packages are part of plain xenial, no need to use any cloud archive anymore [16:38] frickler: ah, I see. the packages are already on my machine (or VM)! Thank you! [16:39] Is it possible to mount.cifs so the files and folders belong to www-data:user1 ? [16:47] Yuri4_: That would be done on the server, by setting default user and group in the smb.conf [16:48] genii, I don't have access to that server. Some person at #linux advices me how to do it through mount parametrs now [16:48] Yuri4_: the mount parameters they mean is on the server [16:49] genii, meant on SMB server [16:49] of course I have access to the server where I mount it [16:52] Yuri4_: on the client, mount with "-o uid=www-data,gid=user1" [16:52] sdeziel, cool! [16:52] thank you [16:52] gonna try [16:54] Yuri4_: Here is what my fstab entry looks like: //smb/share /data/share cifs vers=3.0,rw,noauto,credentials=/etc/samba/simon.secrets,_netdev,nodev,nosuid,noexec,uid=simon,gid=users 0 0 [16:54] sdeziel, eh fstab [16:54] already broke my server when I put wrong space [16:54] Yuri4_: there is more than what you asked but it shows how the auth creds are decoupled from the local UID/GID mapping [16:55] sdeziel, I just crontab it [16:55] Yuri4_: the noauto should allow you to manually test before rebooting :) [16:55] crontab rocks [16:55] @reboot [17:04] sdeziel, is uid = :x:33: [17:04] or just 33? [17:04] Yuri4_: just 33 or www-data [17:05] sdeziel, does that command look right? sudo mount -t cifs //myaccountname.file.core.windows.net/mysharename ./mymountpoint -o uid=33,gid=1000 vers=3.0,username=myaccountname,password=StorageAccountKeyEndingIn==,dir_mode=0777,file_mode=0777 [17:05]