chuckersjp / coreos-iso-maker Goto Github PK

Could you add some more detail to the README with regards to creating individual ignition files. Is there a link to documentation that we could use here or could there be some small description of the process?

Most baremetal UPI and IPI install docs show how to create the generic bootstrap, master, and worker ignition files, but this playbook seems to require an ignition for each individual node on a webserver.

Please make sure all .j2 file have a space after {% include 'arguments.j2' %} . It is important as the next charcater after the include is ignored.

Especially in isolinux.cfg-single.j2, where the End Of Line is ignored, making the menu list broken.

Sorry for the problematic pull request.

underscores are not allowed in host names. I had someone just change the domain piece of the host names in this role and it failed to install due to underscore in bootstrap_node. Recommend changing to either bootstrap.example.com

Hello,

I've worked on switching to the version 4.6 of OpenShift.
The solution is simple (but I didnt find a better way to send a message other than an Issue)
Please take a look at the fork on Its4u:
https://github.com/its4u/coreos-iso-maker

On the branch "v4.6", the solution is:
adding an option on the isolunix file (currently only on single-dhcp): coreos.liveiso=RHCOS-x86_64
because on the playbook: /usr/bin/mkisofs [...] -A 'RHCOS-x86_64' [...]

the coreos.liveiso should be the app id. On the iso, the default is rhcos-46.82.202010091720-0, but since the playbook create another iso, it is another app id.

Not related, but the repo on its4u present 3 fixes:
first (on the branch dhcp), a patch to use dhcp
and (on the branch path), a patch to use custom folder in the web_server to pull ignition file or image file

second (on the branch dhcpANDpath): both patch together
third (on the branch v4.6): using the dhcpANDpath patch, I've added the v4.6 patch.
(maybe some parameters on isolinux are useless, I've put them all just in case).
The grub.cfg file is also useless in 4.6 (at least I didnt need it)

Thanks for setting up this repo. Saved me a ton of time creating the ISO's for setting the static IPs.
Just wanted to point out that the param should be "ignition_url" in this line, not image_url

Hi,

The isolinux.cfg file does not change the boot params of the ISO's kernel. It seems like it's not honoring it and the default kernel params are shown.

However, I got it to work though by adding the "{{cmd_args}}" to the grub.cfg
Once the "cmd_args" were added to the grub.cfg I was able to see my static IP configuration and iginition_url and image_url in the boot params and everything was gravy.

It was working fine for 4.2. I will open a PR shortly.