[00:58] seffyroff: what do you want to manipulate [01:09] I created a Windows VM and I want to convert it so that it cna be used with MAAS. What format do I covert it too? [01:22] Hey: it wont work with MAAS [01:26] roaksoax, I added the curtin files [01:27] actually, I am one step ahead.. I am using windows-opoenstack-imaging-tools to create the image === ackkk is now known as ackk === kukacz_ is now known as kukacz [14:40] roaksoax: I want to set the default domain. currently hosts are receiving .maas, and I don't want that [14:57] seffyroff: change the domain name over the API [15:04] roaksoax: I created a windows image customized it, sysprepped it, then cast it to a Hyper-v VM using WinPE. I then placed the curtin folder in the root. [15:05] The steps following this is to create an image that MAAS can use for BareMetal. [15:05] Do those steps look correct? [15:05] amd I missing anything? [15:24] Bug #1707563 changed: [2.2] no API document on /api/2.0/machines/{system_id}/ op=test === frankban is now known as frankban|afk [17:06] roaksoax: sure thing, that's what I've been wrestling with. I've tried using the python visceral stuff, the shell, the cli, rest calls via curl or postman, in each case i get different, generic errors [17:28] with curl and postman, I can't get oauth exchange to happen, so stuck before anything useful. With the cli I don't seem to be able to query dnsresources. Using the maas library from github, the profiles command seems to be missing [17:28] so the origin object doesn't get created in the shell [17:30] Bug #1759911 opened: [enhancement] during enlistment, when maas can't create a bmc user/password, node's bmc ip address is not reported [17:36] correction: the profiles command doesn't seem to include a login subcommand [18:19] seffyroff: maas domain update name= [18:19] seffyroff: this may also be helpful https://www.lucaswilliams.net/index.php/2016/10/02/maas-2-0-and-dns/ [18:21] roaksoax: thanks! - I'll take a look at the link and try out that cmd [18:25] argument COMMAND: invalid choice: 'domain' (choose from 'devices', 'files', 'machines', 'nodes', 'rack-controllers', 'region-controllers', 'version') [18:26] the admin profile doesn't have access to the domain [18:29] seffyroff: are you sure its a user ? [18:29] admin user* [18:31] admin is the user i login to the webui with. How can I determine it's perms? [18:32] you are on to something there though [18:32] if i use the guthub maas client i see: [18:32] ~/amc$ bin/maas users admin --profile admin [18:32] Error: argument --profile: invalid choice: 'admin' (choose from ) [18:33] guthub. Lol. Freudian slip there - I need a snack :D [18:35] seffyroff: use the older cli [18:35] seffyroff: not the one from python-libmaas [18:36] with that I get: argument COMMAND: invalid choice: 'domain' (choose from 'devices', 'files', 'machines', 'nodes', 'rack-controllers', 'region-controllers', 'version') [18:39] correction [18:39] I get argument COMMAND: invalid choice: 'domain' (choose from 'refresh', 'logout', 'list', 'login', 'apikey', 'createadmin', 'changepassword', 'admin') [18:43] hang on, i did a refresh and now it looks like I'm getting more options [18:45] it's working now! [18:50] right, so the name I want to change the maas domain to is another exisiting domain, which I can't delete as it has nodes using it. So next step is to batch change those nodes back to the maas domain. I can figure this out, maybe :D [18:54] separate issue (or maybe it's related?) i can pxe-boot a machine from the maas rack controller (I see it pulls dhcp from the rack controller's IP) but it doesn't then netboot, it just exits pxe [19:04] trying to pxe-boot it again whilst watching the logs [19:06] maasserver.region_controller.DNSReloadError: Failed to reload DNS; serial mismatch on domains lan, maas [19:33] ok, so i can't easily (via webui or cli) seem to remove dnsresource records [20:10] hm, in the GUI i see a bunch of resource records under the 'lan' domain, but when I do 'maas admin dnsresource-records read domain=lan' i get: [20:10] Success. [20:10] Machine-readable output follows: [20:10] [] [20:16] ok, so deleting all devices seemed to be the only way to remove dnsresource records [20:16] so i've done that [20:16] they will be re-discovered :/ [20:19] ok, successfully renamed the maas domain now [20:19] still seeing the DNS reload error though [20:21] 2018-03-29 20:20:24 maasserver.region_controller: [critical] Failed configuring DNS. [20:21] Traceback (most recent call last): [20:21] File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 393, in callback [20:21] self._startRunCallbacks(result) [20:21] File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 501, in _startRunCallbacks [20:21] self._runCallbacks() [20:21] File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 588, in _runCallbacks [20:21] current.result = callback(current.result, *args, **kw) [20:21] File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1184, in gotResult [20:21] _inlineCallbacks(r, g, deferred) [20:21] --- --- [20:21] File "/usr/lib/python3/dist-packages/twisted/internet/defer.py", line 1128, in _inlineCallbacks [20:21] result = g.send(result) [20:21] File "/usr/lib/python3/dist-packages/maasserver/region_controller.py", line 175, in _checkSerial [20:21] "on domains %s" % ', '.join(not_matching_domains)) [20:21] maasserver.region_controller.DNSReloadError: Failed to reload DNS; serial mismatch on domains lan [20:21] eek, sorry for the spam [20:24] here's a link to the log entry: http://termbin.com/znbl [20:33] my pxe-boot issue seems to have gone away. my new machine just successfully pxe-booted into enlistment [20:33] not sure what changed there :/ [20:52] Bug #1759944 opened: [2.4, UI] Changing the subnet's fabric/vlan over the UI has no effect [20:58] Bug #1759946 opened: [2.3+] Changing a subnet's fabric/vlan doesn't automatically update the interface model [21:03] i guess my next move, which is my default move with anything DNS related is 'wait an hour' and see if it corrects itself? [21:10] seffyroff: that's strange, what you are reporting [21:10] seffyroff: that said [21:10] seffyroff: if machines atomatically dhcp from MAAS they will have a dns record created to the, which you cannot remove [21:11] seffyroff: iirc, same when you deploy a machine [21:11] seffyroff: so the stuff that maas does automatically cannot be changed [21:14] well, that error spams every 30 seconds or so, and has been doing so all day, so prior to any machine deployment, and has continued even when I deleted all nodes [21:15] there is an upstream dns server on the lan, but i don't seen anything in its logs related to local dns lookups [21:15] my bind knowledge is fairly limited so not sure how to proceed. there's a set-serial command which might help, but it's unclear to me what to set it to [21:16] i can see in the /etc/bind/maas/* files refrences to serials in the zone files [21:17] so just pick an increment higher?? [21:17] seffyroff: i would reocmmend you file a bug and provide step by step instructions on how to reproduce it, as I just tried, and was unable to [21:18] ok, however I have done a bunch of stuff before reaching this point. I'm tempted to tear down and reinstall maas first. [21:19] which is non-trivial as the rackd is now providing dhcp to my lan [21:19] although not super difficult [21:19] i'll do that first. [21:24] seffyroff: sounds good [23:54] Hi all. Looking for assistance with curtin. Want to have different config files for different machines in maas; would I 'pin' them to tags? Or would I 'pin' them to domains? [23:54] thanks in advance. also if there's a better place to ask this (or to find previous questions) please lmk