=== manjo` is now known as manjo [04:52] should i restart the box after configure network interfaces? http://vpaste.net/HQirT AFAIK im used to do /etc/init.d/networking restart or ifconfig eth0 down && ifconfig eth0 up, but it doesn't work === disposable3 is now known as disposable2 [08:55] Good morning. [09:32] cpaelzer: did you intend to drop the openldap merge from the blueprint? [09:38] rbasak: yeah it was a dup, check the second to last line [09:38] rbasak: I was updating mine and picked a few of the more simpler merges to fill into my qemu testing idle time slots [09:38] rbasak: and so I found a few things that were duplicates or not updated yet [09:39] rbasak: I hope there is no openldap != openldap magive that I'd have missed - did I ? [09:56] cpaelzer: ah OK. Just checking! [10:25] In what order [10:25] In what order I should install these packages http://dpaste.com/1Q388JC ? === synapse is now known as Guest89004 [13:15] coreycb: i uploaded a newer tempest last night btw [13:16] zul, ok thanks [13:42] coreycb: can you confirm that Openstack Kolla in not yet package for Openstack Newton in Ubuntu ? [13:44] zioproto, confirmed. although we were talking about packaging it. [13:52] ok, I am testing it at the moment, right now working with pip then [13:54] zioproto, hey [13:54] hey [13:54] zioproto, are you looking at kolla itself or one of the kolla-ansible/k8s deployment projects? [13:55] we have this problem here, that we dont feel like rewriting our puppet stuff from puppet3 to puppet4 [13:55] at the moment looking at kolla in stable/newton [13:55] that is still just kolla without the additional kolla-ansible repo [13:55] that starts in ocata [13:55] kolla-ansible repo only has a master branch [13:56] zioproto, ack [13:56] still did not look at Kubernetes [13:56] zioproto, ok so can I suggest a slight different approach to packaging kolla then ? [13:57] sure [13:57] I am all ears ! [13:57] zioproto, have you heard of snaps? [13:57] is k8s different from https://github.com/openstack/kolla-kubernetes ? [13:57] kubernetes == k8s [13:57] for folk like me that can't spell or be bothered to type a long name :-) [13:57] ok, so this is the same stuff ? https://launchpad.net/kolla-k8s [13:58] yah [13:59] so what different approach you would suggest ? [13:59] ah snaps [13:59] yes [13:59] zioproto, yeah [13:59] yes [13:59] zioproto, https://github.com/openstack-snaps/snap-rally [13:59] packaging distribution agnostic, right ? [13:59] yep [13:59] I hear of it [13:59] but I dont have experience [13:59] zioproto, we've been looking at it alot in the last few months [13:59] zioproto, have a mostly functional set of openstack snaps [14:00] actually is how we deploy RC packages on Cumulus Linux [14:00] I just raised the review to get rally and tempest snaps up under /openstack [14:00] jamespage: interesting, I'm working on rally today. Code available? [14:00] do you have a stable/newton openstack snap for Kolla that I can test ? [14:00] zioproto, not yet - I was going to suggest that you have a run at it [14:01] jamespage: are you coming to Milano to the ops meetup ? [14:01] they are pretty quick to write [14:01] zioproto, might be [14:01] zioproto, plans tbc [14:01] okay, so I will first give it a try with pip [14:01] joelio, https://github.com/openstack-snaps/snap-rally [14:01] thanks [14:01] is installable from the snap store - take a read of the README [14:01] Kolla is already new, and I cant introduce in the team 3 new technologies at the same time :) [14:02] zioproto, just think of it as a static wrap of pip [14:02] installable without infecting the rest of your install with pip-ness [14:03] joelio, fwiw I think you need the snapd from xenial-proposed for the rally snap - its a classic mode version [14:03] which is pretty new feature [14:04] joelio, 2.21 is the version [14:04] jamespage: yea, I'll take a look - I'd be keen to look at this for the cli tooling too, currently we provide a Vagrantfile for customers and a web interface, a snap would be cool too [14:04] joelio, oh I already have one in flight [14:04] ace :) [14:04] joelio, openstackclients [14:04] joelio, idea is that it provides all openstack project cli tools [14:04] brill, sounds ideal [14:05] the snap store is due to support series soon as well, so we can have a openstackclients aligned with each stable release of openstack [14:05] awesome [14:06] joelio, we're bootstrapping snap bits atm - if you wanted to join #openstack-snaps that's where most irc discussion is happening [14:07] jamespage: ack [14:07] zioproto, ^^ if you're interested as well :-) [14:13] ok ! I will try to join also there [14:13] so when I run commands like [14:13] sudo snapper create -d "Installing DHCPd pre-release fix" --command "dpkg -i ./isc-dhcp-*deb" [14:13] I am already use snap [14:13] is the same tool right ? [14:13] or snapper is yet another thing ? [14:31] zul: different, thats for snapshotting your local stuff.. this is more akin to an image registry/catalogue [14:31] zioproto: ^^ (sorry zul) [14:31] I just tested rally out, took less than a minute including setting up xenial-proposed, lgtm [14:35] dannf`, please feel free to verify bug 1640519 [14:35] bug 1640519 in curtin (Ubuntu Xenial) "arm64 xenial maas images don't include u-boot-tools package" [Medium,Confirmed] https://launchpad.net/bugs/1640519 [14:52] joelio: so we are talking about this ? http://snapcraft.io/ [14:52] yep [15:05] smoser: yep - i'll ask sfeole to try it in his setup === dannf` is now known as dannf [15:23] rbasak: could you run the importer on tgt ? [15:23] rbasak: currently old/new debian is still outdated so it needs an import anyway [15:23] rbasak: but I'm eager to see what it does since this already has a zesty merge [15:23] yet I'm considering a re-merge to pick up latest (and drop more delta IIRC) [15:26] zioproto, have you considered switching to charms from your current puppet approach for deployment of openstack? [15:27] mmm… no, not at all :) [15:31] cpaelzer: sure [15:32] thanks rbasak [15:36] cpaelzer: done [16:14] EmilienM, is ocata-proposed working ok for you know that webob is back to 1.6.2? [16:15] coreycb: I haven't tested [16:15] mwhahaha: ^ [16:15] no [16:15] we've got other issues [16:15] * mwhahaha hasn't had time to dig [16:15] but nova's broken [16:16] mwhahaha, in what way? [16:17] coreycb: http://logs.openstack.org/66/422766/4/check/gate-puppet-openstack-integration-4-scenario001-tempest-ubuntu-xenial-nv/790428e/console.html#_2017-01-24_15_07_22_546980 [16:17] https://review.openstack.org/#/c/422766/ if you want to follow along [16:18] mwhahaha, is there any chance that run has the old webob? [16:18] nope [16:18] mwhahaha, hmm [16:18] http://logs.openstack.org/66/422766/4/check/gate-puppet-openstack-integration-4-scenario001-tempest-ubuntu-xenial-nv/790428e/logs/dpkg-l.txt.gz [16:18] 1:1.6.2-2~cloud0 [16:19] mwhahaha, any details in the scheduler log as to why no valid host was found? [16:19] http://logs.openstack.org/66/422766/4/check/gate-puppet-openstack-integration-4-scenario001-tempest-ubuntu-xenial-nv/790428e/logs/ [16:20] like i said, i haven't looked deeply yet. there was a vif error that is saw when i took a few seconds [16:21] http://logs.openstack.org/66/422766/4/check/gate-puppet-openstack-integration-4-scenario001-tempest-ubuntu-xenial-nv/790428e/logs/nova/nova-compute.txt.gz#_2017-01-24_15_01_25_380 [16:27] mwhahaha, coreycb: hold a mo [16:27] I think that might be due to a os-vif incompat we had [16:27] Rebuilding amd64 build of nova 2:15.0.0~b2-0ubuntu2~cloud0 in ubuntu xenial RELEASE [16:27] just triggered that [16:27] jamespage, hmm [16:27] sorry that fell off my plate yesterday [16:28] * mwhahaha buys jamespage a bigger plate :D [16:28] :) [16:30] coreycb, mwhahaha: hmm [16:30] coreycb, mwhahaha: no I did do it yesterday [16:30] 2:15.0.0~b2-0ubuntu3~cloud0 [16:30] is the right version [16:31] we might have a general os-vif compat issue in that case [16:34] http://logs.openstack.org/66/422766/4/check/gate-puppet-openstack-integration-4-scenario001-tempest-ubuntu-xenial-nv/790428e/logs/nova/nova-conductor.txt.gz#_2017-01-24_15_00_57_582 [16:46] mwhahaha: [Errno 2] No such file or directory [16:46] looks like something fails on the compute node with regards to port creation [16:47] jamespage, yeah would be nice to know what that file or director is [16:47] 2017-01-24 15:01:52.220 4178 DEBUG oslo.privsep.daemon [-] u'brctl addbr qbr9926d47b-cb' failed. Not Retrying. out_of_band /usr/lib/python2.7/dist-packages/oslo_privsep/daemon.py:194 [16:47] brctl by the looks of things [16:48] http://logs.openstack.org/66/422766/4/check/gate-puppet-openstack-integration-4-scenario001-tempest-ubuntu-xenial-nv/790428e/logs/syslog.txt.gz [16:48] there's the syslog if you want to go looking [16:49] looks like there's a bunch of aodh errors too we'll need to cleanup at some point [16:50] mwhahaha, coreycb: indeed bridge-utils is not installed [16:53] mwhahaha, coreycb: ok looks like a dep change in libvirt is causing this [16:53] xenial libvirt has a hard depends libvirt-bin -> bridge-utils [16:53] in ocata uca [16:54] libvirt-daemon-system -> recommends bridge-utils only [16:54] pesky libvirt [16:55] if you're fixing deps, python-gabbi is also required by tempest. we fixed it in our testing since we don't use the packages but it wasn't getting pulled in [16:56] mwhahaha, ah ok we'll take a look at that [16:56] coreycb, we don't see this as juju install bridge-utils automatically on all units for container bridging and addresssing [16:56] but it does need a tweak [16:57] I'd suggest actually having the dep on neutron-openvswitch-agent or nova-compute - not quite sure which is best tbh [16:57] nova uses brctl directly I think [16:58] coreycb, prob nova-compute methinks [16:59] for what it's worth, rdo has nova-compute -> bridge-utils [16:59] https://github.com/rdo-packages/nova-distgit/blob/rpm-master/openstack-nova.spec#L144 [16:59] jamespage, mwhahaha: yeah seems to make sense to add as a dep for nova-compute [16:59] we only have it for nova-network atm [17:00] alright let me make those 2 updates [17:10] mwhahaha, it doesn't look like tempest uses gabbi. could it be a project-specific plugin? [17:11] it's possible [17:12] coreycb: ceilometer test [17:13] http://logs.openstack.org/48/422248/8/check/gate-puppet-openstack-integration-4-scenario001-tempest-ubuntu-xenial-nv/1c85705/console.html#_2017-01-20_22_23_32_199166 [17:30] mwhahaha, ok i'll add that dependency for ceilometer. these will build and i'll let you know when they're backported and promoted to ocata-proposed. [17:30] coreycb: thanks [17:40] Is there a way I can do my own live kernel patching without using canonical's livepatch service? ie looking to self host/maintain. [17:56] caribou, do you still have merges in progress for kdump-tools, clamav, and nut packages? thought i'd make sure they are still on your radar [17:57] oh, kdump-tools was for secureboot, not a merge [17:57] jgrimm: kdump-tools/makedumpfile is synced with Debian; clamav is awaiting on the MIR of tomsfastmath to become a sync [17:58] jgrimm: nut still needs to be completed afaik [17:58] cool enough, i was just going through the blueprint and checking in on INPROGRESS items [17:59] jgrimm: I'd like to get the kexec-tools done too depending on my b/w [17:59] ack [18:13] Hello All, nice to be part of the community! [18:19] Hello. I just upgraded to 16.10 and iscsitarget no longer exists. What is the replacement package? [18:33] i need assistance [18:34] Noname01x2, ask your question. don't ask for attention. [18:35] ok [18:36] so on my ubuntu server i have apparmor, which i need. and its not working. getting an error in the log. [18:37] im open to any solution to get rid of the error, although i would prefer not to remove mysql-server in the process. [18:37] please pastebin your DENIED entries [18:37] how do i do that? im no pro [18:38] i took a screenshot [18:39] saved it in paint [18:39] Noname01x2: dmesg | grep DENIED should do it [18:40] you could use the pastebinit program to automatically copy-and-paste that to a pastebin site [18:41] ctjctj: I don't know about _the_ replacement for iscsitarget, but there's a few choices.. both libsiscsi and tgt appear to be in main in 16.10: http://packages.ubuntu.com/source/yakkety/tgt http://packages.ubuntu.com/source/yakkety/libiscsi [18:41] hmm let me try that [18:41] tgt and libiscsi and I'm checking istgt now. All my google foo is pulling up iscsitarget references. THanks sarnold. [18:44] im in emergincy mode [18:45] Noname01x2, *grins* I understand. I've got 10+ devs that are grumping because we lost all of our iscsi targets. [18:46] owww [18:47] I'll blame you for the solution. [18:48] when devs are grumbling is probably not the ideal time to be doing research, but last time I looked into iscsiland, this table seemed useful http://scst.sourceforge.net/comparison.html [18:49] sending you a file, please accept sarnold [18:49] eh? [18:49] its a screenshot [18:49] why not just pastebin the dmesg | grep DENIED? [18:49] cant [18:49] let me try again [18:50] im in the emergency mode terminal thing [18:51] i coppied the msg [18:51] now what [18:52] noname01x3, if you don't have it installed, install pastebinit and use it to create pastebin documents. You'll get back a URL which you post here. [18:52] !pastebin [18:52] For posting multi-line texts into the channel, please use http://paste.ubuntu.com | To post !screenshots use http://imgur.com/ !pastebinit to paste directly from command line | Make sure you give us the URL for your paste - see also the channel topic. [18:53] im rebooting [18:53] ohh i get it [18:55] sarnold, are you around today? good afternoon [18:55] pastebin came up. now all i have to do is get the text....(still rebooting) [18:56] is there a problem with setting systemd-journald to persistent? [18:56] hey DammitJim :) I wouldn't have thought so, but in that bug report yesterday I got the impression that using it might lead to .. wel,l the exact issue you were facing yesterday [18:57] LOL [18:57] well, making it persistent has actually somehow helped and the server reboots just fine [18:57] dude [18:57] should I be concerned with leaving it the way it is? [18:57] just when I think I understand how things work.. [18:57] Right now I'm at "Welcome to emergency mode! After logging in, type "journalctl -xb" to view system logs, "systemctl" to reboot, "systemctl default" or ^d to try again to boot into default mode. Press Enter for maintenance. [18:57] LOL... same thing here... I mean, the log still says that it couldn't unmount /var [18:58] dammit, that means that there are more problems, huh? [18:58] DammitJim: it should be fine to keep it on persistent. your logging fielsystem may see twice the write rate that it had before, since now rsyslog -and- journald are logging, but for most people that really shouldn't be a burden. [18:58] ok, thanks [18:59] it's sad that one only has a limited amount of time and to get to the root of a problem sometimes one has to just skip it until later [18:59] whatever later is... [18:59] interesting [18:59] How to Stop any daemons that is listening on the default SMTP port. (Newbie Here!) [18:59] DammitJim: yeah. from that bug report it looks sort of like there's no real fix in sight, either [19:00] Noname01x2: so you're stuck in a rescue mode? o_O oy. that sounds like an annoying thing to sort out. [19:00] yeah [19:00] it boots into this mode and thats what I was trying to tell you guys. I cant even open any programs [19:01] how can I copy and paste the error if I cant even copy n paste [19:01] aha [19:01] I see a red Failed [19:01] Failed to start LSB: AppArmor initialization. at the end of the line. [19:02] everything else has a green OK [19:02] Fix it please. Thanks. [19:03] What about the packages? Can we do something with that? [19:06] noname01x3: what does dmesg | grep -i apparmor report? [19:07] Help ? How to Stop any daemons that is listening on the default SMTP port. (Newbie Here!) [19:07] JemalMoha: use netstat -anp | grep :25 to find whatever it listening on port 25, then either use systemctl stop to stop the thing (16.04 lts and newer), or 'stop name' to stop the thing (14.04 lts and older) [19:09] @sarnold thanks!! [19:10] sarnold it reports: { 0.001320] AppArmor: AppArmor disabled by boot time parameter [19:10] noname01x3: hrm, I wouldn't have expected that to cause the boot to fail. [19:11] [ 29.453556] system[1]: systemd 229 running in system mode. [19:11] its all ur fault. u broke it. :-) [19:11] fyi i made up that last line. [19:11] ..about u braking it... [19:12] also it says: (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK... [19:13] that bit just says that systemd was configured with support for all those different tools [19:13] Well the app armor is important. [19:13] oh [19:13] app armor is in red [19:13] hehe, yes, I feel the same way, I've been working on apparmor since 2000 :) [19:14] :-) [19:14] I'm confident you can help me. [19:17] noname01x3: are there better errors in the logs? /var/log/syslog for example? [19:17] how do i get that [19:18] less /var/log/syslog probably -- there's a chance that the things causing you trouble may not say 'apparmor' directly in the lines.. [19:18] I would live to give you all possible info. [19:18] ok a lot of info cam ein [19:19] jump to the end and then start scrolling backwrads.. [19:19] I have an ssh key with a passphrase, but Im not getting asked to put my passphrase in, why is this? Its for a local VM. [19:19] tyler3332: ssh-agent or a keyring daemon perhaps? [19:19] noname01x3, in case you did not know, you can use a slash (/) to start a search in less. So find your apparmor error, then use page up down to move up and see what was happing near there. You can use 'G' to go to the end of the file and '?' to search backwards. [19:19] how do I check? [19:20] tyler3332, ssh-add -L [19:20] yup there is a key there [19:20] is that ssh-agent? [19:21] That means you are connected to an ssh-agent. When the key is added to the agent you were asked to provide the passphrase. [19:21] ah ok [19:21] It is assumed that ssh-agent will take good care of your private keys. I.e. it wont leak them to just any old person. [19:22] ok thanks. [19:22] ssh-add is how you add (and remove?) keys from the agent. -l will give you finger prints and -L will give you the public key half. [19:22] do keys get added automatically? cause I didnt add it myself [19:23] When I'm dealing with clients lacking clues we'll get them to log in with a password verify that they have a working agent with ssh-add -l then have them give us the ssh-add -L output so that we can update "authorized_keys" and turn off password access. [19:24] definitely good idea [19:24] (reality is that we have a special VM with a guest account that the log into to runn ssh-add -L. That way we never allow password access to our servers to our clients. [19:24] DUDE [19:24] that's great :) [19:24] sarnold i cant tell what msg is good and whats bad [19:24] There is *exactly* one password on our servers. For root which I know for emergency access from the KVM console. [19:25] noname01x3: can you copy-and-paste it to paste.ubuntu.com? [19:25] I have no idea how. [19:26] maybe i should have booted into advanced mode [19:26] sarnold, take a look at pam_ssh_agent_auth for how to allow sudo access based on ssh keys. [19:26] noname01x3, use pastebinit like I pointed you at. [19:27] ctjctj: he's stuck in a rescue mode, no networking, no nothing :/ [19:27] sarnold, service networking start ? [19:28] worth a try [19:30] beisner, can you promote nova - 2:15.0.0~b2-0ubuntu4~cloud0 to ocata-proposed please? [19:31] i believe i have network access [19:31] it says starting raise network interfaces.... [19:31] ctjctj: pam_ssh_agent_auth.. that's odd. it's better than passwords for sudo but I'd be afraid that the ssh key lifetimes useful for logging in to hosts may not match sudo lifetimes very well :) [19:31] [OK]Started ifup for eth0. [19:32] sarnold, I don't follow. what do you mean by ssh key lifetimes? [19:32] ctjctj: well, back in the day I used to use ssh-add -t 300 [19:32] beisner, that should help get puppet CI back in order for mwhahaha [19:33] sarnold, ah, we don't we leave the key in for the duration of the session. [19:33] ctjctj: but then I started doing tasks on VMs that would take an hour, etc, so I wound up moving to ssh-add -t 3600 ... and then eventually the tasks got long enough that I gave up on -t entirely and just add keys to the agent that last -forever- [19:33] yep. [19:33] So the life time would be fine for sudo work. [19:33] but I certainly don't want more than ~five minutes of allowed sudo window [19:33] not that that's perfect [19:34] an open terminal is a disaster anyway [19:34] but still [19:34] sarnold, ah. I understand. I'm dealing with a bunch of Devs that are Drupal/Wordpress people. Teaching them to do anything safely is hard. [19:35] ctjctj: it certainly doesn't come naturally. :) [19:35] Maintenance mode [19:35] coreycb, ok, promoted. ye shall haz bridge utils. [19:35] beisner, awesome [19:35] My current favorite is that our "director of creative direction" has been giving out the company user name/password (.htpasswd) to clients instead of making them use their individual passwords) [19:35] ctjctj so if I have network access. then what [19:36] noname01x3: sweet. apt-get install pastebinit, and then pastebinit /var/log/syslog -- if it looks like something you'd want to share with the world [19:36] noname01x3, now you can do things like apt-get install pastebinit and use that to get us bits and bobs of what's going on in your system. [19:36] ctjctj: ouch. just .. ouch. [19:37] reading package [19:37] done [19:37] sarnold, yeah. Ouch is the word for this guy. He manged to make his way onto my s___ list about 6 months ago. Normally it takes about 2 weeks to work your way off. He is deeper on the list than when he was placed on it. [19:38] ctjctj: gotta hand it to him, he does sound -creative- [19:38] installed [19:38] so now what [19:38] im at root [19:38] pastebinit /var/log/syslog [19:39] Friday I get a client to agree to X,Y and Z. This makes things so much easier for what I'm developing. Monday he talks to the client and undid all of that client work. So now the project is in limbo for another two weeks until client reaches a decision, again. [19:39] sarnold it says: http://paste.ubuntu.com/23859388/ [19:39] noname01x3, *yes*! [19:39] noname01x3: great :) moment.. [19:40] Congrats to me. [19:40] This is fun [19:40] My boss will be unhappy if this isn't fixed, however. [19:40] noname01x3, sorry about that. Part of the problem is that we forget to specify everything. [19:41] ctjctj ok so thats ok. I get it. You didn't understand how low my skill level was. [19:41] VERY LOW. But I'm a smart guy. [19:41] sarnold, that looks like a desktop boot. I'm seeing boatloads of gnome-session stuff. [19:42] I sound like I'm almost not stupid. [19:43] I can't spot anything that looks like trouble ;( [19:43] sarnold A desktop boot? How dare you? [19:43] sarnold, would dmesg hold it? [19:43] I'm thinking that systemd might not be running yet. [19:43] syslogd [19:44] noname01x3, on that server: dmesg| pastebinit [19:44] uhh ok. let me see [19:45] ctjctj Http://paste.ubuntu.com/23859412/ [19:46] [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic.efi.signed root=/dev/mapper/BNY--VS--CA--vg-root ro security=selinux selinux=1 [19:46] no wonder apparmor init script isn't happy :) [19:46] noname01x3, translation. fix your boot command line. [19:47] selinux and aptarmor don't play well together (IIRC) [19:47] okay. how do we do that [19:47] indeed :) [19:47] maybe someday [19:47] but not this year [19:47] and probably not next year [19:47] Thats ok. We have time. [19:48] sarnold, apt-get purge selinux ? [19:48] But we need this up and running asap [19:48] lol [19:48] maybe with an * in there some place? [19:49] ctjctj someone doesn't like selinux. [19:49] ctjctj yes thank u. [19:49] noname01x3, you don't at this point. Or you can explain to "boss" why the system is down? *GRIN* [19:49] :-) [19:49] I'm waiting for sarnold to approve that line [19:49] good question, I don't know selinux packging well enough to know if they automatically add selinux=1 stuff to the kernel command line.. [19:49] apt-get purge 'selinux*' would be a decent starting point anyway [19:50] sarnold, I'd start with the purge, check /boot/grub.menu (or whatever it is this week) and if it is still bad we'll update it via grub stuff. [19:50] careful, that might match libselinux as well [19:50] sarnold will it give me a warning if it will do something i dont like? [19:50] noname01x3: not really [19:50] linux is like that [19:50] noname01x3, nope. It's unix. If you want to shoot yourself in the foot then it will ask you how big of a hole you want to make after the first shot. [19:51] it'll let you cut off your arms if you want [19:51] lol [19:51] sarnold, *laughs* great minds and low ethics think alike. [19:51] ok thanks for the tip. [19:51] lol [19:52] zul, yay python-statsd approved [19:53] I like the purge selunix idea. [19:53] I'm going to send a cuss word filled bug report to whomever wrote the option parsing for tgtadm '-y' is not allowed/supported. I ended up in the source code to find out that -y means --blocksize... [19:53] zul, that should unblock some things [19:53] coreycb: i saw [19:53] coreycb: oslo.middleware [19:53] -y means blocksize ??? [19:53] who thought that out [19:53] I have a backup checkpoint from this morning. [19:53] I can put it right back if it goes bad [19:53] ikonia, yeah. [19:53] or maybe I dont know what im talking about. [19:54] ctjctj: eww! [19:54] noname01x3, I'm glad you have that checkpoint. Means we don't have to worry about xxxbadcommamndXXX -rf / mean people. [19:56] ctjctj, thanks. Yeah I believe I can try it with no worries. And my boss is constantly asking me whats new and I would love to have an answer, other than repeating what you guys are saying, which causes him to ask "And". [19:57] noname01x3, what version of ubuntu are you running? 14.04LTS? [19:58] probably 16.04 lts, with kernel version 4.4.x [19:58] sarnold, ok. [19:58] 16.04 LTS [19:59] noname01x3, once you have the purge done: pastebinit /boot/grub/grub.cfg [19:59] ctjctj, ok i will do the purge now. [20:00] apt-get purge selinux [20:00] Done [20:00] waait it says click y to continue [20:01] noname01x3, wrong command. [20:01] apt-get purge 'selinux*' [20:01] pressed y [20:01]