Description of problem: For some recipes, the valid generated kickstart is so big it doesn't fit into the database "rendered_kickstart" table "kickstart" column (of size 65535). beakerd tries repeatedly and fails repeatedly, the recipe stays in Scheduled state. How reproducible: Have a recipe with a huge kickstart, e.g. clone this one: https://beaker.engineering.redhat.com/recipes/7853762#installation Additional info: The kickstart of the linked recipe is so big because a) it is a group job, group having +- 70 members b) Beaker adds all the ssh keys of all the group members to the kickstart The ssh-keys portion of the kickstrat is 40k. beaker-server error log: http://pastebin.test.redhat.com/832120 pretty-printed part of the kickstart as parsed from the log message: http://pastebin.test.redhat.com/832123
Space usable for Kickstart is now 2 ** 24 - 1. In case you will breach even this limit, the job is aborted.
not fixed, see for details: https://projects.engineering.redhat.com/browse/BKR-4830?focusedCommentId=3017352&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3017352