=== frankban|afk is now known as frankban
[09:08] <mup> Bug #1591093 opened: 3rd party HP drivers (archive hostname renamed) - deployment fails <canonical-bootstack> <MAAS:New> <https://launchpad.net/bugs/1591093>
[10:28] <manolas> hello! how can I set the same date/time on all nodes?
[10:45] <manolas> anyone? :)
=== zz_CyberJacob is now known as CyberJacob
[11:53] <olavgg> I'm trying MAAS for the first time here, but I have a problem. When I boot a machine with PXE from MAAS. It hang during boot with the following error message "no url to host". It is like the client gets no internet connection. Is there something specific I need to configure for that to work?
[11:53] <olavgg> sorry, the error message says: "no route to host"
[13:41] <smoser> olavgg, do you get to a linux boot ?
[13:41] <smoser> or is this the pxe environment erroring
=== arturt__ is now known as arturt
[15:33] <mup> Bug #1591250 opened: 1.9.3 changelog information missing from maas.ubuntu.com/docs1.9/changelog.html <cdo-qa> <MAAS:New> <https://launchpad.net/bugs/1591250>
[16:03] <mup> Bug #1502253 changed: Partition table should be deleted after all partitions have been removed <storage> <MAAS:Fix Released> <https://launchpad.net/bugs/1502253>
[16:03] <mup> Bug #1590866 changed: [2.0b6] Cannot deploy Windows Server 2012 R2  <jujuqa> <MAAS Image Builder:Triaged> <https://launchpad.net/bugs/1590866>
=== frankban is now known as frankban|afk
[17:16] <jhobbs> I have a bunch of physically identical nodes that I want to have the same storage configuration
[17:16] <jhobbs> what's the best way to do that? do i need to just configure each one the same way one by one?
[17:22] <roaksoax> jhobbs: yes
[17:23] <roaksoax> jhobbs: if it is custom, you can only do it on one by one basis
[17:23] <jhobbs> ok, thanks roaksoax
[18:06] <abi_> hi
[18:52] <mup> Bug #1583349 changed: ESXi VM fails to commission after adding VMware chassis : no image ubuntu/amd64/hwe-x/trusty/no-such-image/boot-kernel <oil> <MAAS:Invalid by newell-jensen> <https://launchpad.net/bugs/1583349>
[19:52] <mup> Bug #1534942 changed: Failed curtin install: An error occured handling 'sda': ValueError - no disk with serial '<diskserialnumber>' found <landscape> <oil> <curtin:Invalid> <MAAS:Invalid> <https://launchpad.net/bugs/1534942>
[19:52] <mup> Bug #1591336 opened: MAAS allows formatting /dev/sda as one big ext4 filesystem, but that doesn't work <v-pil> <MAAS:New> <https://launchpad.net/bugs/1591336>
[20:01] <mup> Bug #1591346 opened: [2.0b7] maas createadmin fails <MAAS:New> <https://launchpad.net/bugs/1591346>
[20:46] <mup> Bug #1591364 opened: disks not renamed on deployed systems following renaming on maas UI <oil> <curtin:New> <MAAS:New> <https://launchpad.net/bugs/1591364>
[21:16] <mup> Bug #1246626 changed: WAKE_ON_LAN power method cannot power off a node. <power> <wol> <MAAS:Won't Fix> <https://launchpad.net/bugs/1246626>
[21:46] <mup> Bug #1591364 changed: Can't use new dname on trusty deployed systems following renaming on maas UI <oil> <curtin:Invalid> <MAAS:New> <https://launchpad.net/bugs/1591364>
[22:25] <mup> Bug #1590846 changed: [2.0b6] Installation log of a failed install not sent back to MAAS <curtin:New> <MAAS:Invalid> <https://launchpad.net/bugs/1590846>
[22:25] <mup> Bug #1591395 opened: [arm64] some arm64 systems need ipmi_ssif module instead of ipmi_si <MAAS:New> <https://launchpad.net/bugs/1591395>