When configuring ironic services with puppet, puppet-ironic needs to create ppc64le directories in the tftproot and configure ironic parameters such as min_command_interval, pxe_config_template_by_arch, and pxe/pxe_bootfile_name_by_arch.
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible. If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-". To add draft documentation text: * Select the documentation type from the "Doc Type" drop down field. * A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.
The docs associated with this bug are going to be delivered outside of the Errata process and are being tracked at: https://bugzilla.redhat.com/show_bug.cgi?id=1599782
Verified: Environment: puppet-ironic-12.4.0-2.el7ost.noarch Added to undercloud.conf: crudini --set undercloud.conf DEFAULT additional_architectures ppc64le crudini --set undercloud.conf DEFAULT ipxe_enabled false Then: (undercloud) [stack@undercloud75 ~]$ sudo md5sum /tftpboot/*/default 898c3d02968b64f3d86384f9311c7fe4 /tftpboot/ppc64le/default 898c3d02968b64f3d86384f9311c7fe4 /tftpboot/pxelinux.cfg/default sudo grep -Eir enable_ppc64le /etc/puppet /etc/puppet/hieradata/puppet-stack-config.yaml:ironic::pxe::enable_ppc64le: true /etc/puppet/hieradata/puppet-stack-config.yaml:ironic::inspector::enable_ppc64le: true ls /tftpboot/ chain.c32 ipxe.efi map-file master_images ppc64le pxelinux.0 pxelinux.cfg undionly.kpxe (undercloud) [stack@undercloud75 ~]$ sudo grep OPAL /etc/ironic-inspector/dnsmasq.conf # Client is ppc64le (OPAL) box and doesn't need a chain loader, but does need a custom config Note: The above didn't exist before adding the 2 entries to undercloud.conf.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2574