Hi Julia,

Thanks a lot for your responses and support.

To Update on the ongoing issue, I tried deploying the overcloud with your valuable suggestions i.e by passing "DhcpAgentNotification: true" in ironic-overcloud.yaml

The setup came up successfully, but with this configuration the IP allocated on the system is one which is being configured while creating the subnet in openstack.

The system is still getting the IP (172.23.3.212) from neutron. The subnet range was configured as 172.23.3.210-172.23.3.240 while creating the provisioning subnet.

The system gets stuck here and no action is performed after this.

Is there any way to resolve this and make successful  provisioning the baremetal node in TripleO Train Release (Since RHOSP 16 was on Train, so I thought to go with that version for better stability)

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2/html-single/release_notes/index

I have some queries:

1. Is passing "DhcpAgentNotification: true" enough or do we have to make some other changes as well?

1. Although there are some security concerns specified in the document, but Currently I am focusing on the default flat bare metal approach which has dedicated interface for bare metal Provisioning. There is one composable method approach as well. Keeping aside the security concerns, which approach is better and functional?
1. https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.2/html/bare_metal_provisioning/prerequisites-for-bare-metal-provisioning

1. Will moving to upper openstack release version make this deployment possible? 
1. If Yes, which release should I go with as till wallaby the ironic-overcloud.yml file has no option of including "DhcpAgentNotification: true" by default 
1. https://github.com/openstack/tripleo-heat-templates/blob/stable/wallaby/environments/services/ironic-overcloud.yaml

Looking forward for your valuable feedback/response.

Regards

Anirudh Gupta

On Fri, Feb 4, 2022 at 8:54 PM Anirudh Gupta <anyrude10@gmail.com> wrote:

Hi,

Surely I'll revert the status once it gets deployed.

Bdw the suspicion is because of Train Release or it is something else?

Regards

Anirudh Gupta

On Fri, 4 Feb, 2022, 20:29 Julia Kreger, <juliaashleykreger@gmail.com> wrote:

On Fri, Feb 4, 2022 at 5:50 AM Anirudh Gupta <anyrude10@gmail.com> wrote:

Hi Julia

Thanks for your response.

Earlier I was passing both ironic.yaml and ironic-overcloud.yaml located at path /usr/share/openstack-tripleo-heat-templates/environments/services/

My current understanding now says that since I am using OVN, not OVS so I should pass only ironic-overcloud.yaml in my deployment.

I am currently on Train Release and my default ironic-overcloud.yaml file has no such entry

DhcpAgentNotification: true

I suspect that should work. Let us know if it does.

 

I would add this there and re deploy the setup.

Would that be enough to make my deployment successful?

Regards

Anirudh Gupta

On Fri, 4 Feb, 2022, 18:40 Julia Kreger, <juliaashleykreger@gmail.com> wrote:

It is not a matter of disabling OVN, but a matter of enabling the dnsmasq service and notifications.

https://github.com/openstack/tripleo-heat-templates/blob/master/environments/services/ironic-overcloud.yaml may provide some insight. 

I suspect if you're using stable/wallaby based branches and it is not working, there may need to be a patch backported by the TripleO maintainers.

On Thu, Feb 3, 2022 at 8:02 PM Anirudh Gupta <anyrude10@gmail.com> wrote:

Hi Julia,

Thanks for your response.

For the overcloud deployment, I am executing the following command:

openstack overcloud deploy --templates \
    -n /home/stack/templates/network_data.yaml \
    -r /home/stack/templates/roles_data.yaml \
    -e /home/stack/templates/node-info.yaml \
    -e /home/stack/templates/environment.yaml \
    -e /home/stack/templates/environments/network-isolation.yaml \
    -e /home/stack/templates/environments/network-environment.yaml \
    -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic.yaml \
    -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-conductor.yaml \
    -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-inspector.yaml \
    -e /usr/share/openstack-tripleo-heat-templates/environments/services/ironic-overcloud.yaml \
    -e /home/stack/templates/ironic-config.yaml \
    -e /usr/share/openstack-tripleo-heat-templates/environments/docker-ha.yaml \
    -e /usr/share/openstack-tripleo-heat-templates/environments/podman.yaml \
    -e /home/stack/containers-prepare-parameter.yaml

I can see some OVN related stuff in my roles_data and environments/network-isolation.yaml

[stack@undercloud ~]$ grep -inr "ovn"

roles_data.yaml:34:    OVNCMSOptions: "enable-chassis-as-gw"
roles_data.yaml:168:    - OS::TripleO::Services::OVNDBs
roles_data.yaml:169:    - OS::TripleO::Services::OVNController
roles_data.yaml:279:    - OS::TripleO::Services::OVNController
roles_data.yaml:280:    - OS::TripleO::Services::OVNMetadataAgent
environments/network-isolation.yaml:16:  OS::TripleO::Network::Ports::OVNDBsVipPort: ../network/ports/vip.yaml

What is your recommendation and how to disable OVN....should I remove it from roles_data.yaml and then render so that it doesn't get generated in environments/network-isolation.yaml

Please suggest some pointers.

Regards

Anirudh Gupta

It seems OVN is getting installed in ironic

On Fri, Feb 4, 2022 at 1:36 AM Julia Kreger <juliaashleykreger@gmail.com> wrote:

My guess: You're running OVN. You need neutron-dhcp-agent running as well. OVN disables it by default and OVN's integrated DHCP service does not support options for network booting.

-Julia

On Thu, Feb 3, 2022 at 9:06 AM Anirudh Gupta <anyrude10@gmail.com> wrote:

Hi Team

I am trying to Provision Bare Metal Node from my tripleo Overcloud.

For this, while deploying the overcloud, I have followed the "default flat" network approach specified in the below link

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15/html/bare_metal_provisioning/sect-planning

Just to highlight the changes, I have defined the 

ironic-config.yaml 

parameter_defaults:
    ...

    ...
    IronicIPXEEnabled: true
    IronicInspectorSubnets:
    - ip_range: 172.23.3.100,172.23.3.150
    IronicInspectorInterface: 'br-baremetal'

Also modified the file ~/templates/network-environment.yaml

parameter_defaults:
  NeutronBridgeMappings: datacentre:br-ex,baremetal:br-baremetal
  NeutronFlatNetworks: datacentre,baremetal

With this I have Followed all the steps of creating br-baremetal bridge on controller, given in the link below:

https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15/html/bare_metal_provisioning/sect-deploy

  - type: ovs_bridge
     name: br-baremetal
     use_dhcp: false
     members:
     - type: interface
       name: nic3

Post Deployment, I have also create a flat network on "datacentre" physical network and subnet having the range 172.23.3.200,172.23.3.240 (as suggested subnet is same as of inspector and range is different) and the router

Also created a baremetal node and ran "openstack baremetal node manage bm1", the state of which was a success.

Observation:

On executing  "openstack baremetal node provide bm1", the machine gets power on and ideally it should take an IP from ironic inspector range and PXE Boot.

But nothing of this sort happens and we see an IP from neutron range "172.23.3.239" (attached the screenshot)

I have checked overcloud ironic inspector podman logs alongwith the tcpdump.

In tcpdump, I can only see dhcp discover request on br-baremetal and nothing happens after that.

I have tried to explain my issue in detail, but I would be happy to share more details in case still required.

Can someone please help in resolving my issue.

Regards

Anirudh Gupta