Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2076577

Summary: Overcloud node provision fails for OSP17 + RHEL9 in boot mode "bios"
Product: Red Hat OpenStack Reporter: Vijayalakshmi Candappa <vcandapp>
Component: rhosp-directorAssignee: OSP Team <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: David Rosenfeld <drosenfe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17.0 (Wallaby)CC: hakhande, mburns, morazi, ramishra, sbaker
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-20 22:35:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
tcpdump on the provision interface, during overcloud deploy none

Description Vijayalakshmi Candappa 2022-04-19 11:33:21 UTC
Created attachment 1873508 [details]
tcpdump on the provision interface, during overcloud deploy

Description of problem:

When trying to deploy Overcloud for OSP17+RHEL9 (boot mode "bios") node provision fails

Version-Release number of selected component (if applicable):
OSP17+RHEL9 (puddle: RHOS-17.0-RHEL-9-20220316.n.1)

How reproducible:
100%

Steps to Reproduce:
1. After underloud install, intropection is successful for all nodes (i.e openstack baremetal introspection)
2. When trying to deploy overcloud, it fails after DHCP provision -> tftp download of file "snponly.efi" (i.e openstack overcloud node provision)
3.

Note: The same steps and templates works for OSP17 + RHEL8.4 (eg. puddle RHOS-17.0-RHEL-8-20211208.n.1)

Actual results:
Playbook "/usr/share/ansible/tripleo-playbooks/cli-overcloud-node-provision.yaml"
and timesout 

Expected results:
Deploy should pass

Additional info:
The following log attached for more info:

1. eno2_provision_full.pcap.gz (tcpdump on the provision interface, during overcloud deploy)

Comment 1 Steve Baker 2022-04-20 04:58:38 UTC
Can you describe and/or provide screenshots of the console of the node during provisioning?

This could be a duplicate of bug #2072687 but we'd need to know more of what is happening on the node during provision/boot.

Comment 2 Steve Baker 2022-04-20 05:09:38 UTC
Also can you confirm if you are deploying overcloud-full or overcloud-hardened-uefi-full? Only the overcloud-full partition image will work with legacy BIOS boot.

Comment 4 Vijayalakshmi Candappa 2022-04-20 12:39:20 UTC
Hi Steve, 

   The deploy scripts uses the overcloud-full* images:

   (undercloud) [stack@undercloud-0 ~]$ ls images/
   ironic-python-agent.initramfs  ironic-python-agent.kernel  overcloud-full.initrd  overcloud-full.qcow2  overcloud-full.raw  overcloud-full-rpm.manifest  
   overcloud-full-signature.manifest  overcloud-full.vmlinuz
 
   (Attached the screenshot for one of the compute nodes which failed after node provision/boot)

Comment 5 Steve Baker 2022-04-20 22:35:45 UTC
I'm fairly certain this is a duplicate. Please keep an eye on bug #2072687 and try the overcloud-full artifacts when they are available with the fixes.

*** This bug has been marked as a duplicate of bug 2072687 ***