Satellie 6.1: provisioning of s390x build requires token

Solution Verified - Updated -

Issue

  • Satellite 5 provisioning / kickstart of s390x systems used a static kickstart line that was less than 80 chars. e.g.
    ks=http://sat.example.com/ks/cfg/org/1/label/rhel-6u6-zvm-s390x

  • Satellite 6 provisioning / kickstart of s390x systems uses a token that changes with every build / config change and is longer than 80 chars. e.g.
    ks=http://abc.example.com:80/unattended/provision?token=f50249fd-a7af-4c9d-a31d-0f23e4020850&static=yes

  • The token needs to be edited for rebuilds and the 80char limit of IBM CMS makes this very painful. In the environment, have one standard profile for all rhel66 builds. The token is not useful. Note there is no PXE booting in S390x world.

  • Please give option of a static ks build line as per Satellite 5.

  • The rhel66 s390x currently does not support pxe booting to my knowledge, only static kickstart image. Red Hat has s390x boot image that reliably & easily does pxe booting ?

Environment

  • s390x / zvm builds using Red Hat Satellite 6.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In