Provisioning hosts using Red Hat Satellite 6 Capsule Server fails when download policy for kickstart repos are set to On Demand

Solution Verified - Updated -

Issue

  • Provisioning hosts using Satellite Capsule Server fails when the Satellite kickstart repos are set to On Demand and the Capsule Server synchronization is also set to On Demand.

  • The Satellite Server is able to provision successfully, but provisioning using Capsule Server fails when the kickstart repositories have the On Demand download policy.
    Example, when provisioning a RHEL8.3 vm from the capsule, where the RHEL8.3 Kickstart repo is set to download policy "On Demand", dracut captures below logs during provisioning:

[   17.516924] rhel83test dracut-initqueue[1141]: anaconda: successfully fetched stage2 from http://cap6.example.com/pulp/repos/my_org/baseline_2020/RHEL_8_x86_64/content/dist/rhel8/8.3/x86_64/baseos/kickstart/
[   17.633120] rhel83test kernel: loop: module loaded
[   17.656135] rhel83test dracut-initqueue[1141]: losetup: /tmp/curl_fetch_url1/install.img: Warning: file does not fit into a 512-byte sector; the end of the file will be ignored.
  • Capsule Server fails to provision hosts due to vmlinuz not being found.

Environment

  • Red Hat Satellite 6
  • Red Hat Capsule 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content