[00:11] <mup> Bug #1730783 opened: maas 2.2 api returning malformed data <MAAS:New> <https://launchpad.net/bugs/1730783>
[00:56] <juanquy> hello there, guys I'm having issues with pxe booting , the box start the boot sec perfect Ubuntu 16.04 loading, I can even see the new node added on my MAAS dash but after a few sec the box shutdown
[00:58] <juanquy> any ideas please?
[01:11] <juanquy> hello
[01:44] <mup> Bug #1730799 opened: [2.3] Traceback when viewing controller commissioning scripts <MAAS:In Progress by ltrager> <https://launchpad.net/bugs/1730799>
[09:24] <mup> Bug #1730916 opened: Intermittent failure: snippets.tests.test_maas_run_remote_scripts.TestRunScripts.test_run_scripts  <MAAS:New> <https://launchpad.net/bugs/1730916>
[09:33] <mup> Bug #1730916 changed: Intermittent failure: snippets.tests.test_maas_run_remote_scripts.TestRunScripts.test_run_scripts  <MAAS:New> <https://launchpad.net/bugs/1730916>
[09:42] <mup> Bug #1730916 opened: Intermittent failure: snippets.tests.test_maas_run_remote_scripts.TestRunScripts.test_run_scripts  <MAAS:New> <https://launchpad.net/bugs/1730916>
[11:05] <the_questioner> hello maas channel on irc
[11:07] <the_questioner> i have never used maas before but it seems to be exactly what i need
[11:07] <the_questioner> i have a few questions on the subject
[11:08] <the_questioner> i have a firewall ssytem that serves dhcp on the network, also handles port forwarding to my current webserver
[11:09] <the_questioner> would this be an issue for a maas setup
[11:13] <the_questioner> also how the pods work. are the machines intalled from the shared pool or resources, shared resources across multiple systems? or are they single physical systems that are just added together in the pool.
[12:11] <externalreality> Hello, I followed some web instructions I found for setting up a VMAAS. The worked for the most part, however, commissioning nodes time out after 20 minutes according to the maas logs.
[12:12] <externalreality> The MAAS is able to power on the node and begin commissioning but always fails with a timeout.
[14:06] <mup> Bug #1730953 opened: [2.3rc2, UI] The arrow in the  domain dropdown is covered by the text <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730953>
[14:12] <mup> Bug #1730955 opened: [2.3rc2, UI] The Take action dropdown should follow the Vanilla padding guidelines <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730955>
[14:30] <mup> Bug #1730955 changed: [2.3rc2, UI] The Take action dropdown should follow the Vanilla padding guidelines <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730955>
[14:36] <mup> Bug # opened: 1730955, 1730960, 1730965, 1730967
[14:57] <mup> Bug #1730968 opened: [2.3rc2, UI] The cards should have the available metris even if the metrics don't have any data <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730968>
[14:57] <mup> Bug #1730969 opened: [2.3rc2, UI] Machine details secondary nav hidden at medium viewport <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730969>
[15:06] <mup> Bug #1730972 opened: [2.3qa, UI] When the contextual menu is open and I scroll down the menu is still open and sits on top of the header <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730972>
[15:24] <mup> Bug #1730972 changed: [2.3qa, UI] When the contextual menu is open and I scroll down the menu is still open and sits on top of the header <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730972>
[15:27] <mup> Bug #1730972 opened: [2.3qa, UI] When the contextual menu is open and I scroll down the menu is still open and sits on top of the header <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730972>
[15:27] <mup> Bug #1730973 opened: [2.3rc2, UX improvement]  "See results" links should link to specific results row <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730973>
[15:27] <mup> Bug #1730976 opened: [2.3rc2] The Volume groups have health information  <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730976>
[15:42] <mup> Bug #1730977 opened: [2.3rc2, UI] When removing a Volume group and RAIDs the menu item says remove disk which might be confusing  <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730977>
[15:42] <mup> Bug #1730979 opened: [2.3rc2, UI] In the Settings Section when I click Edit the edit button remains on the screen <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730979>
[15:51] <mup> Bug #1730977 changed: [2.3rc2, UI] When removing a Volume group and RAIDs the menu item says remove disk which might be confusing  <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730977>
[15:51] <mup> Bug #1730979 changed: [2.3rc2, UI] In the Settings Section when I click Edit the edit button remains on the screen <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730979>
[15:57] <mup> Bug #1730977 opened: [2.3rc2, UI] When removing a Volume group and RAIDs the menu item says remove disk which might be confusing  <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730977>
[15:57] <mup> Bug #1730979 opened: [2.3rc2, UI] In the Settings Section when I click Edit the edit button remains on the screen <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730979>
[15:57] <mup> Bug #1730983 opened: [2.3rc2, UI] In the storage card the type iof disk should come before the number and size <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730983>
[16:00] <mup> Bug #1730983 changed: [2.3rc2, UI] In the storage card the type iof disk should come before the number and size <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730983>
[16:09] <mup> Bug #1730983 opened: [2.3rc2, UI] In the storage card the type iof disk should come before the number and size <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730983>
[16:18] <mup> Bug #1730985 opened: [2.3rc2, UI] When failed testing has been overwritten for a machine use the notification pattern to notify the user   <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1730985>
[16:45] <mup> Bug #1730991 opened: Bond mode active/backup garp config <canonical-bootstack> <internal> <MAAS:Triaged> <https://launchpad.net/bugs/1730991>
[17:15] <mup> Bug #1731009 opened: [2.3rc2, UI] The column spacing in the storage tables needs to be specified <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1731009>
[17:21] <mup> Bug #1731009 changed: [2.3rc2, UI] The column spacing in the storage tables needs to be specified <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1731009>
[17:24] <mup> Bug #1731009 opened: [2.3rc2, UI] The column spacing in the storage tables needs to be specified <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1731009>
[17:24] <mup> Bug #1731011 opened: [2.3rc2, UI] The storage tags link you to the network discovery page <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1731011>
[17:40] <mup> Bug #1731011 changed: [2.3rc2, UI] The storage tags link you to the network discovery page <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1731011>
[17:46] <mup> Bug #1731011 opened: [2.3rc2, UI] The storage tags link you to the network discovery page <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1731011>
[17:46] <mup> Bug #1731017 opened: [2.3rc2, UI] When a property is Unconfigured it should be consistently presented in the UI <2.3qa> <ui> <MAAS:New> <https://launchpad.net/bugs/1731017>
[19:58] <dfin> Using MAAS I'm able to half-commission a machine on a different subnet that the one that the rack controller is sitting on (same VLAN in MAAS). The PXE process seems to go fine until I get to cloud-init, where I get a "Request Time Out" when talking to the MAAS server (attempting to the the preseed via http). Is there a limitation where there needs to be a Rack Controller in the subnet that is being managed?
[20:00] <dfin> Also, it seems like SSH is misconfigured after the failed preseed, so I cannot get into the box for debugging
[20:23] <roaksoax> dfin: check /etc/maas/rackd.conf doesn't point to localhost and points to the right IP the machine can communicate with
[21:03] <kukacz> hi, is there a way, how to tell MAAS to use a specific block device (not the first one) as root device yet before commissioning starts?
[21:14] <roaksoax> kukacz: no it is not unfortunately. May I ask what are you trying to achieve?
[21:16] <kukacz> roaksoax: sure, I'm setting up a series of servers which have the system drive presented as the last one. I'm using CLI for that
[21:16] <kukacz> anytime I create a machine, commissioning starts using the defaults values
[21:17] <kukacz> then I need to go and delete all the LVs, VGs, partitions and set the correct drive and re-run commissioning
[21:18] <kukacz> I'd like to have the work done without these unnecessary steps
[21:24] <roaksoax> kukacz: why do you need to re-run commissioning ? it doesn't seem like you need to
[21:24] <roaksoax> kukacz: commissioning will only discover disks. After that the machine is ready and you can configure your storage configuration
[21:24] <roaksoax> kukacz: if you want to re-run commissioning and want it to not mess with your storage configuration, there's an option for that which will prevent MAAS from overwriting your storage config
[21:24] <kukacz> ok, that was my wrong understanding then
[21:25] <kukacz> but how about those volumes placed on wrong drive?
[21:26] <roaksoax> kukacz: so this is what I did. 1. added a new machine, which was commissioned. After successfully doing that, the machine was in 'Ready' state
[21:27] <roaksoax> 2. the machine listed a root disk mounted on /, after which I removed it, and configured LVM on it
[21:28] <roaksoax> so at this point I have a machine in ready state with LVM configured as I need to
[21:28] <roaksoax> if I deploy the machine, it works just fine
[21:28] <roaksoax> I then release it, it goes back into 'ready', and the lvm configuration remains the same
[21:29] <roaksoax> kukacz: so, now, I 'commission' the machine *again*, and commissionning resets my LVM configurate
[21:29] <roaksoax> kukacz: so, now, I 'commission' the machine *again*, and commissionning resets my LVM configuration
[21:29] <roaksoax> kukacz: which is correct approach
[21:30] <roaksoax> kukacz: however, if I were to have selected "retain storage configuration" option, it wouldn't have reset the storage config. It would have kept it
[21:33] <kukacz> roaksoax: well, I'm defining a procedure for a group of operators and writing the docs. it seems really strange to define precisely all the steps to delete all objects which were created uselessly by a step (commissioning) which can not be prevented from run before correct parameters are set
[21:35] <kukacz> it would be better then if the comissioning had not created any disk layout. we would saved 3 steps at minimum
[21:38] <roaksoax> kukacz: maas just works the way it has worked way before the ability to define custom storage, this is what most users of maas use by default, hence maas takes a simple default
[21:38] <roaksoax> if you want to change the default, they you have the flexibility to do so when the machine is 'ready'
[21:40] <kukacz> hmm, perhaps we are a rare usecase, when using multiple disk drives with system volume being presented the last. it's common Dell server though
[21:46] <roaksoax> kukacz: you mean, the bios has the last disk as the disk that the machine will boot from ?
[21:47] <kukacz> roaksoax: yes
[21:47] <kukacz> roaksoax: that's because there are non-raid and raid-disks used at the same time. while the raid-disk (used for OS install) is presented last
[21:55] <mup> Bug #1722578 changed: Controller <> is running an older version of MAAS (less than 2.3.0) <cdo-qa> <foundations-engine> <MAAS:New> <https://launchpad.net/bugs/1722578>
[22:01] <mup> Bug #1731059 opened: [2.3, HWTv2] Machines changing states due to aborted operations may leave machines with 'pending' tests <MAAS:New> <https://launchpad.net/bugs/1731059>
[22:10] <mup> Bug #1731059 changed: [2.3, HWTv2] Machines changing states due to aborted operations may leave machines with 'pending' tests <MAAS:New> <https://launchpad.net/bugs/1731059>
[22:22] <mup> Bug #1731059 opened: [2.3, HWTv2] Machines changing states due to aborted operations may leave machines with 'pending' tests <MAAS:New> <https://launchpad.net/bugs/1731059>
[22:31] <mup> Bug #1731062 opened: [2.3, HWTv2] Incorrect overall status messages about failed tests <MAAS:Triaged by ltrager> <https://launchpad.net/bugs/1731062>
[23:18] <shadoxx> Hmm, running into a weird issue with Pods.
[23:20] <shadoxx> If I compose a machine, and leave it in the default zone, with the default domain (maas), the machine will comission fine. However, if I change either the domain or zone its in, it fails to PXE boot