[00:51] <keithzg> Well, still curious, but I found the fifth area where netboot settings lay in the motherboard firmware and seem to have convinced it to indeed use UEFI; failure apparently was due to attempting Legacy booting only over the network boot.
[01:17] <smoser> nacc, iscsi is fun!
[01:17] <smoser> interestingly, though, we do not see these issues in vmtest
[01:17] <smoser> and we do push through non-root iscsi
[01:17] <smoser> and in maas every day usage (in maas images) we push through iscsi root
[01:18] <smoser> but both of those cases have cloud-init in them which could be pushing a different shutdown order.
[01:35] <smoser> powersj, if your'e still arond
[01:35] <smoser> i think that centos6 migith be as easy as
[01:35] <smoser> https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/324585
[01:40] <smoser> fudge
[12:30] <teward> who's got Samba on their desk, from the Security team perspective?
[12:30] <teward> Server Team*
[12:30] <teward> if anyone
[12:35] <rbasak> ahasenack has been looking at it recently I think? ^
[12:35] <ahasenack> indeed
[12:35] <ahasenack> what's up?
[12:36] <rbasak> samba is a weird package though. Many samba issues are from a desktop, not server perspective. It sort of sits between multiple teams.
[12:36] <teward> ahasenack: just wanted to make sure CVE-2017-7494 was on the radar, and that a fix was included.
[12:37] <teward> rbasak: true, but in *this* case I'm fairly certain the RCE affects server-side Samba so...
[12:37] <ahasenack> teward: https://www.ubuntu.com/usn/usn-3296-1/
[12:37] <teward> ahasenack: not listed for Artful
[12:37] <teward> the question is Artful because https://people.canonical.com/~ubuntu-security/cve/2017/CVE-2017-7494.html showed on my radar on Ask Ubuntu
[12:37] <ahasenack> teward: correct
[12:38] <teward> just tryin to see if 17.10 is still vulnerable so I can edit the answer on Ask Ubuntu accordingly heh
[12:38] <ahasenack> usns are not issued for in-development ubuntu releases,
[12:38] <rbasak> Looks like it's stuck in proposed
[12:38] <ahasenack> artful has 4.5.8+dfsg-0ubuntu0.17.04.1 still
[12:38] <ahasenack> rbasak: I've noticed this lagging with other packages too
[12:39] <rbasak> There's a dep8 failure holding it in proposed
[12:39] <rbasak> Could be an unstable test. I'll give it another retry.
[12:40] <ahasenack> rbasak: mysql-server-5.7 is also stuck in artful's proposed
[12:41] <ahasenack> all other released distros have .18, artful has .17
[12:41] <rbasak> Yeah due to a diaspora-installer problem. Someone on the release team might be willing to allow that one through, but I can't do it :-/
[12:41]  * rbasak asked in #ubuntu-devel earlier
[12:42] <ahasenack> it's been like that since may 15th at least, when I first asked :)
[12:42]  * rbasak asks again
[12:42] <ahasenack> teward: what was the askubuntu question?
[12:45] <rbasak> dep8 passed this time. Hopefully it'll migrate on the next publisher run.
[13:09] <ahasenack> nice
[13:11] <ahasenack> geez, another samba failed-to-install-upgrade apport bug
[13:12] <ahasenack> it's always the same, restart failed for some reason
[13:12] <ahasenack> but systemd doesn't provide any logs by default
[13:13] <ahasenack> is there a way to have apport include /var/log/samba/log* in these reports? I see it includes other samba bits
[13:14] <fallentree> ahasenack: makes you wanna cry, amirite?   /zing
[13:15] <ahasenack> heh
[13:31] <teward> ahasenack: https://askubuntu.com/questions/918776/re-latest-bug-when-will-ubuntu-be-updating-samba-v4-3-11
[13:31] <teward> sorry my commute to work took so long :P
[13:33] <ahasenack> :)
[13:36] <rbasak> FWIW, samba has migrated to the artful release pocket now.
[14:12] <paxatron4034> anyone here have experience with corosync?
[14:28] <Ussat> you know untill the update there is a REAL simple fix
[14:29] <Ussat> just add nt pipe support = no to smb.conf
[14:29] <Ussat> restart samba, done
[14:37] <daveomcd> I'm fairly new to managing an ubuntu server.  I use my to host a rails app.  I've not installed security & non-security updates in some time.  I was going to go about doing that, but wasn't sure if there are some best practices or things I should consider before just running "sudo apt-get update && sudo apt-get upgrade" after taking a snapshot of the server in case something goes wrong with the updates?
[15:21] <jushur> daveomcd: make a backup before?
[16:43] <tomreyn> daveomcd: as long as you don't make use of third party apt sources / packages or non-packaged software, only installing patches (which is what the commands you typed above would do), update issues are *really* rare.
[18:47] <jonfatino> Does anyone have an updated guide to load ubuntu 16.04 from pxe without using nfs. The issue here is squashfs and how to load it. I am ok with putting it inside initrd but need some help.
[18:47] <jonfatino> https://ubuntuforums.org/showthread.php?t=2074035