| sujeet_ | Hi | 04:48 |
|---|---|---|
| sujeet_ | Can we commission the script without rebooting the server (node)? | 04:49 |
| === frankban|afk is now known as frankban | ||
| mup | Bug #1619202 opened: [2.1] Upgrade doesn't remove old template files <MAAS:New for andreserl> <https://launchpad.net/bugs/1619202> | 09:27 |
| mup | Bug #1619202 changed: [2.1] Upgrade doesn't remove old template files <MAAS:New for andreserl> <https://launchpad.net/bugs/1619202> | 09:39 |
| === degville is now known as degville_ | ||
| === degville_ is now known as degville | ||
| mup | Bug #1619202 opened: [2.1] Upgrade doesn't remove old template files <MAAS:New for andreserl> <https://launchpad.net/bugs/1619202> | 09:42 |
| PCdude | I am having troubles with MAAS | 11:14 |
| PCdude | the nodes cannot get to the internet | 11:15 |
| PCdude | every apt command can indeed reach the internet. pings to the gateway succeed and dnslookups succeed too. ping an ip address outside the LAN fails and also to a hostname | 11:15 |
| PCdude | so the proxy through the controller does work | 11:15 |
| PCdude | but not for the other traffic | 11:15 |
| PCdude | is it possible to route other traffic through the proxy too or is there a misconfiguration? | 11:16 |
| sujeet_ | Hi | 12:00 |
| sujeet_ | can i commission the node without rebooting the node(server)? | 12:01 |
| mup | Bug #1619262 opened: [2.1, 2.0] Can't input dynamic range on "Enable DHCP" after I deleted the dynamic range <MAAS:New> <MAAS 2.0:New> <MAAS trunk:New> <https://launchpad.net/bugs/1619262> | 12:19 |
| mup | Bug #1619334 opened: Service monitor logs using full enum repr rather than name <MAAS:Triaged> <https://launchpad.net/bugs/1619334> | 14:43 |
| mup | Bug #1619337 opened: [vanilla] Logout page highlights the settings navigation not the logout navigation <vanilla> <MAAS:New> <https://launchpad.net/bugs/1619337> | 14:43 |
| mup | Bug #1619342 opened: maas-dhcp precondition fails (/var/lib/maas/dhcpd-interfaces does not exist) <canonical-bootstack> <MAAS:New> <https://launchpad.net/bugs/1619342> | 15:01 |
| mup | Bug #1619342 changed: maas-dhcp precondition fails (/var/lib/maas/dhcpd-interfaces does not exist) <canonical-bootstack> <MAAS:Invalid> <https://launchpad.net/bugs/1619342> | 15:19 |
| mup | Bug #1619342 opened: maas-dhcp precondition fails (/var/lib/maas/dhcpd-interfaces does not exist) <canonical-bootstack> <MAAS:Invalid> <https://launchpad.net/bugs/1619342> | 15:28 |
| mup | Bug #1619342 changed: maas-dhcp precondition fails (/var/lib/maas/dhcpd-interfaces does not exist) <canonical-bootstack> <MAAS:Invalid> <https://launchpad.net/bugs/1619342> | 15:31 |
| mup | Bug #1619368 opened: maas upgrade failed from 14.04+1.9 to 16.04+2.0 <MAAS:New> <https://launchpad.net/bugs/1619368> | 16:01 |
| sujeet_ | can i commission the node without rebooting the node(server)? | 16:20 |
| neith | PCdude: its the default behavior | 16:37 |
| sujeet_ | Hi roaksoax | 16:50 |
| === frankban is now known as frankban|afk | ||
| sujeet_ | Hi kiko | 17:52 |
| sujeet_ | kiko: can i commission the node without rebooting the node(server)? or is there any other way to do it? | 17:54 |
| kiko | hello sujeet_ | 18:16 |
| kiko | well | 18:16 |
| kiko | it's a good question | 18:16 |
| kiko | sujeet_, when you upload a commissioning script, it is set up to be run as part of commissioning | 18:17 |
| kiko | sujeet_, commissioning is a phase which boot into the ephemeral image | 18:17 |
| kiko | sujeet_, are you asking if you can "recommission" the node once it has already been deployed without rebooting? | 18:17 |
| natefinch | what's the opposite of deploy for a node? I deployed a node from the GUI, and now I want to undo that action | 18:45 |
| kiko | natefinch, release | 18:52 |
| kiko | natefinch, note that release doesn't wipe drives by default; you need to enable that feature in the GUI if you want it, but be aware it is VERY slow on HDDs | 18:52 |
| kiko | natefinch, it will get faster with 2.1 where we use ATA secure erase where supported | 18:52 |
| sujeet_ | kiko: once the node is deployed we can recommission the node without rebooting? | 18:54 |
| kiko | sujeet_, no, you can't | 18:55 |
| kiko | sujeet_, commissioning is done from the ephemeral environment | 18:55 |
| kiko | sujeet_, which obviously can't be used on a node running windows! | 18:55 |
| sujeet_ | ok, is there any other way to do without rebooting? | 18:57 |
| sujeet_ | i just want to communicate to the http server to get json data | 18:57 |
| kiko | sujeet_, you mean once the node is deployed? no, definitely not | 19:00 |
| kiko | sujeet_, are you clear on how MAAS works? | 19:00 |
| sujeet_ | yes | 19:00 |
| kiko | sujeet_, once you deploy the node runs the target OS, and we don't run an agent on it | 19:00 |
| sujeet_ | before deploying? | 19:01 |
| sujeet_ | still my node is in ready state | 19:01 |
| kiko | sujeet_, if your node is in ready state, it is powered off | 19:02 |
| sujeet_ | we are getting the info of drives, Ram,and so on | 19:02 |
| kiko | sujeet_, right | 19:02 |
| sujeet_ | no | 19:02 |
| kiko | no? | 19:02 |
| kiko | what do you mean? | 19:02 |
| sujeet_ | instead of getting again all the info of system, can we run the script? | 19:03 |
| sujeet_ | my http server will reside in BMC chip | 19:04 |
| sujeet_ | so i need to do some operation (firmware upgrade or secure erase) after the node is in ready state | 19:05 |
| kiko | you just run commissioning again | 19:05 |
| kiko | it will run your script, along with recollecting system information | 19:05 |
| sujeet_ | so without rebooting it wont work? | 19:06 |
| kiko | roaksoax, can a user script be run before we collect the hardware information? | 19:06 |
| kiko | sujeet_, I don't understand what you mean by "without rebooting" | 19:06 |
| kiko | sujeet_, when the node is in the ready state, it is powered off | 19:06 |
| kiko | sujeet_, when you tell it to Commission, MAAS boots the node | 19:06 |
| roaksoax | kiko: a commissioning script? no, they run after MAAS has done its thing | 19:06 |
| sujeet_ | ok | 19:06 |
| roaksoax | kiko: in this case, what do we need it for ? | 19:06 |
| kiko | roaksoax, we probably need to run then before MAAS does hardware probing | 19:06 |
| kiko | roaksoax, because if you are setting up HW RAID the drive details will change | 19:07 |
| kiko | otherwise you'll need to reboot or at least re-run the hardware probe multiple times | 19:07 |
| kiko | roaksoax, s/then/them | 19:07 |
| kiko | sujeet_, oh, I think I see what you mean | 19:08 |
| kiko | sujeet_, you want to be able to issue commands to the BMC while the node is powered off? | 19:08 |
| roaksoax | kiko: we could potentially look into doing commissioning scripts in such a way that they run on early or late stages | 19:08 |
| kiko | sujeet_, can you upgrade firmware while the node is off? what about set up drives? | 19:08 |
| roaksoax | kiko: but that would indeed require a bit of work | 19:08 |
| kiko | roaksoax, yeah, it's work for sure, but hopefully not too much | 19:08 |
| sujeet_ | ok | 19:09 |
| mup | Bug #1619435 opened: Images imported, but settings says "no usable release" <MAAS:New> <https://launchpad.net/bugs/1619435> | 19:23 |
| sujeet_ | 1->. I enlisted the node (after enlisting the state is power OFF). 2.->I commission the node (after commissioning the state is ON). 3-> i want to write the script to communicate to the BMC http server (on node power state ON) | 19:25 |
| kiko | sujeet_, 2 is wrong. after commissioning the state is off. | 19:26 |
| kiko | sujeet_, your script needs to run as part of step 2. | 19:26 |
| sujeet_ | ok , but after commissioning the state is ON in my setup, do you think there is some problem? | 19:29 |
| kiko | sujeet_, yes, there is a problem | 19:29 |
| kiko | sujeet_, when you commission there is an option to leave the node running, though -- have you enabled it? | 19:30 |
| sujeet_ | dont know, where is that option? | 19:30 |
| kiko | when you commission | 19:31 |
| sujeet_ | Kiko: i sent the screenshot of MAAS dashboard in your mail, can you please look at it? | 19:39 |
| kiko | sujeet_, is the machine actually on? | 19:54 |
| kiko | sujeet_, or is our power check failing? | 19:54 |
| sujeet_ | its on | 19:54 |
| kiko | sujeet_, okay, it's a bug. something is not finishing in the commissioning phase | 19:55 |
| kiko | sujeet_, I've forwarded the screenshot to andres, but if you can SSH into the node and collect the logs that would help | 19:55 |
| kiko | sujeet_, see privmsg | 19:56 |
| sujeet_ | ok | 19:57 |
| mup | Bug #1619477 opened: [ipv6] interfaces only show one subnet during commissioning <MAAS:New> <https://launchpad.net/bugs/1619477> | 21:53 |
| mup | Bug #1619435 changed: Images imported, but settings says "no usable release" <MAAS:Invalid> <https://launchpad.net/bugs/1619435> | 22:32 |
| mup | Bug #1619488 opened: 2.0.0 rack talking to 2.1.0(alpha) region results in rack errors <MAAS:New> <https://launchpad.net/bugs/1619488> | 22:32 |
| mup | Bug #1619493 opened: [2.1] rack needs to be more graceful about missing recommends <MAAS:Triaged> <https://launchpad.net/bugs/1619493> | 23:11 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!