[00:47] <jac_cplane> custom image no longer boots in 2.2.2 - works in 2.2.0
[00:48] <jac_cplane> i have two maas servers side by side.  one is 2.2.2 and one is 2.2.0.     I load the same custom image into both.   I can boot fine with 2.2.0 but get a image-not-found in 2.2.2
[00:48] <jac_cplane> any help?
[01:18] <roaksoax> jac_cplane: boot-resources instead of boot-resource
[01:18] <roaksoax> jac_cplane: and check that your machine doesn't have a minimum kernel set that's no longer available
[01:32] <jac_cplane> yes I figured out the typo
[01:32] <jac_cplane> where can I check min kernel
[01:34] <jac_cplane> no minimum kernel is selected
[01:34] <jac_cplane> i'm filling out a bug-report now
[01:36] <roaksoax> jac_cplane: two places, 1, the machine itsself, 2 the settings page
[01:36] <jac_cplane> please see Bug #1731709 r
[01:36] <jac_cplane> setting page is set to no min kernel
[01:36] <jac_cplane> nothing on the machine
[01:37] <jac_cplane> custom image works on 2.2.0  but not on 2.2.2
[01:37] <roaksoax> jac_cplane: i dont think this is an issue with the custom iamge. MAAS doens't pxe boot cusotm images. MAAS boots into ubuntu to deploy custom images
[01:38] <roaksoax> jac_cplane: i've seen that issue before i can't remember when
[01:39] <roaksoax> jac_cplane: are there no logs in maas.log or rackd.log that show why it failed to boot
[01:39] <roaksoax> ?
[01:39] <roaksoax> i think that what it shows is just a side effect
[01:39] <jac_cplane> i cannot see anhything in the logs
[01:42] <jac_cplane> I do this this error in maas.log
[01:43] <jac_cplane> Nov 11 16:44:10 MAAS maas.preseed: [info] MACH2: custom network and storage options are only supported on Ubuntu. Using flat storage layout.
[01:43] <roaksoax> that's not related though
[01:44] <jac_cplane> yes - i agree
[01:44] <jac_cplane> I have a 2.2.0 side by side with 2.2.2 - works fine with 2.2.0
[01:45] <jac_cplane> cannot find any other error in the logs.  but the boot console does show the error.  in the but report
[01:45] <jac_cplane> this appears after the error in maas.log
[01:45] <jac_cplane> Nov 11 13:46:56 MAAS maas.node: [error] MACH2: Marking node failed: Installation failed (refer to the installation log for more information).
[01:46] <jac_cplane> not sure where installation log is
[01:47] <jac_cplane> found it.
[01:47] <jac_cplane> Traceback (most recent call last):
[01:47] <jac_cplane>   File "/tmp/tmpa_i9n7t_/target/curtin/curtin-hooks.py", line 595, in <module>
[01:47] <jac_cplane>     main()
[01:47] <jac_cplane>   File "/tmp/tmpa_i9n7t_/target/curtin/curtin-hooks.py", line 537, in main
[01:47] <jac_cplane>     curthooks.write_files(cfg, target)
[01:50] <jac_cplane> AttributeError: module 'curtin.commands.curthooks' has no attribute 'write_files'
[01:50] <jac_cplane> Unexpected error while running command.
[01:50] <jac_cplane> this is the error
[01:50] <jac_cplane>   File "/tmp/tmpa_i9n7t_/target/curtin/curtin-hooks.py", line 595, in <module>
[01:52] <mup> Bug #1731709 opened: centos custom images won't boot MAAS 2.2.2 <MAAS:Incomplete> <https://launchpad.net/bugs/1731709>
[01:54] <roaksoax> jac_cplane: i've asked more questions on the bug
[01:54] <roaksoax> jac_cplane: when you provide all the info please mark it as 'new' again
[01:54] <roaksoax> jac_cplane: also, I think this is an issue with curtin, maybe they regressed somethign
[01:56] <roaksoax> jac_cplane: it seems it has, how did you create that custom image ?
[04:42] <jac_cplane> thanks  i will provide more details
[04:42] <jac_cplane> dont remember how we created the image.  it was created when we had maas 2.0
=== jac_ is now known as jac_cplane
[20:26] <jac_cplane> can anyone help with Bug #1731709
[20:28] <jac_cplane>   AttributeError: module 'curtin.commands.curthooks' has no attribute 'write_files'
[20:28] <jac_cplane> File "/tmp/tmpngh0fprp/target/curtin/curtin-hooks.py", line 537, in main
[21:26] <jac_cplane> please see https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1731805
[21:26] <jac_cplane> and  https://bugs.launchpad.net/maas/+bug/1731709
[21:26] <jac_cplane> who can help?
[21:48] <roaksoax> jac_cplane: where did you get that custom image?
[21:49] <jac_cplane> it was made from instructions from canonical
[21:49] <jac_cplane> the image is not the problem
[21:50] <jac_cplane> the image works with curtin 505 but not on curtin 532
[21:50] <roaksoax> jac_cplane: i see that now, but i need to understand where that image came from
[21:50] <roaksoax> jac_cplane: what version of the inage generator is the one you used to create the new image
[21:50] <jac_cplane> from our own repo.  I can put the instructions we used in the maas bug
[21:50] <roaksoax> ?
[21:50] <jac_cplane> maas 2.1
[21:51] <jac_cplane> it was created using maas 2.1
[21:51] <roaksoax> jac_cplane: right but did you use maas inage builder with instructions provided by a support engineer or did you manaully build that image yourself?
[21:51] <jac_cplane> the image was done based on this bug https://bugs.launchpad.net/juju/+bug/1646847
[21:52] <jac_cplane>     wget https://people.canonical.com/~iatrou/curtin-hooks-20170110.py.gz -O - | gunzip > curtin-hooks.py
[21:52] <jac_cplane>     wget http://images.maas.io/ephemeral-v2/daily/centos70/amd64/20160801_01/root-tgz -O centos7-root.tgz
[21:52] <jac_cplane>     mkdir centos7-root && cd centos7-root
[21:52] <jac_cplane>     sudo tar -zxvf ../centos7-root.tgz
[21:52] <jac_cplane>     sudo cp ../curtin-hooks.py curtin/
[21:52] <jac_cplane>     sudo chown root: curtin/curtin-hooks.py
[21:52] <jac_cplane>     sudo chmod 755 curtin/curtin-hooks.py
[21:52] <jac_cplane>     sudo tar -zcvf ../centos7-root-netfix.tgz .
[21:53] <jac_cplane> we created the image on the instruction from a canonical support engineer.  dont rmembe who.
[21:54] <roaksoax> jac_cplane: right so it seems you created an image from an unsupported path, which is a problem, that said curtin seem to have changed which is whats brraking you
[21:55] <roaksoax> jac_cplane: the wuickest fix is to change your image to ise futil from where it has been moved rather than where it is being imported
[21:55] <jac_cplane> those instructions were given to us by Michael Iatrou
[21:57] <jac_cplane> can you repeat your last comment. I don't understand
[21:57] <roaksoax> jac_cplane: please paste those instructions in yhe bug and ill deal with it tomorrow
[21:57] <jac_cplane> ok
[21:58] <jac_cplane> thanks
[22:03] <jac_cplane> done