#66 Update lorax templates for modular server
Closed: Fixed Opened by langdon.

Using a non-graphical installer requires changes to the server lorax templates


Metadata Update from @langdon:
- Issue assigned to asamalik

Note memtest86+ currently cannot be built (https://bugzilla.redhat.com/show_bug.cgi?id=1491023).
Unless we can drop it from the templates, this is also a blocker.

I'm blocked by RPM conflicts in the installer module.

I'm currently regenerating the installer module using the latest repodata and will submit a new build very soon.

Installer build is failing. I have created a separate issue for the installer and make it block this one.

Metadata Update from @hpopal:
- Issue priority set to: immediate

Now I need @psabata to sync it to stg and make me a compose so I'm able to test and tweak the lorax template. I will do that tomorrow.

The build is broken!

There are no anaconda packages in PDC https://pdc.fedoraproject.org/rest_api/v1/unreleasedvariants/?active=True&variant_id=installer&variant_version=master&page_size=1&page=2

..which means I didn't get them in the compose: https://kojipkgs.stg.fedoraproject.org/compose/branched/psabata/Fedora-Modular-Rawhide-20170915.n.1/

This issue is tracked here: https://pagure.io/fm-orchestrator/issue/660

As a workaround, I have downloaded all packages from the platform, host, hardware-support, installer, and perl modules locally, and created a local repo I could use with lorax.

The installer was missing a dependency and the platform module changed in the meanwhile. So I have regenerated the installer modulemd again and submitted yet another build: https://mbs.fedoraproject.org/module-build-service/1/module-builds/951

I managed to get a boot.iso using these lorax templates https://github.com/fedora-modularity/lorax-templates

I haven't been able to test it, so I'm not closing it.

Lorax templates appear to be correct now. However, the install is still failing. As a result, keeping this open until we know exactly where the problem is.

Closing this bug as lorax seems to be correct

Metadata Update from @langdon:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata