Unable to log into overcloud BM instance when using OVN

[Harald Jensås]

cloud-init-output.log:2019-05-10 18:45:49,439 - url_helper.py[WARNING]: Calling 'http://192.168.24.1/latest/meta-data/instance-id' failed [101/120s]: request error [HTTPConnectionPool(host='192.168.24.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f28a44d8390>, 'Connection to 192.168.24.1 timed out. (connect timeout=50.0)'))]
cloud-init-output.log:2019-05-10 18:46:07,460 - url_helper.py[WARNING]: Calling 'http://192.168.24.1/latest/meta-data/instance-id' failed [119/120s]: request error [HTTPConnectionPool(host='192.168.24.1', port=80): Max retries exceeded with url: /latest/meta-data/instance-id (Caused by ConnectTimeoutError(<urllib3.connection.HTTPConnection object at 0x7f28a44d8ba8>, 'Connection to 192.168.24.1 timed out. (connect timeout=17.0)'))]

Ironic service deployment have always enabled force_config_drive because with baremetal the config drive is required. (see: deployment/nova/nova-ironic-container-puppet.yaml#L80)

Since the switch to OVN, the ovn service disables force_config_drive when OVNMetadataAgent is enabled.

There are usecases when operator wants to talk to metadata API from config-drive script (e.g. using curl to get data from metadata). That means it makes sense to have OVN Metadata Agent deployed while forcing config-drive to be used.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/660689
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=7ac8e67d82e688382c3ea13c48b0cb55f759117b
Submitter: Zuul
Branch: master

commit 7ac8e67d82e688382c3ea13c48b0cb55f759117b
Author: Jakub Libosvar <email address hidden>
Date: Wed May 22 13:47:37 2019 +0200

    Set force_config_drive only when OVNMetadata is disabled

    There are usecases when operator wants to talk to metadata API from
    config-drive script (e.g. using curl to get data from metadata). That
    means it makes sense to have OVN Metadata Agent deployed while forcing
    config-drive to be used.

    This patch sets force_config_drive to true only when OVNMetadataEnable
    is set to false. If it's set to true then it doesn't touch
    force_config_drive option, leaving it up to environment to define it.
    (The default for force_config_drive is false.)

    Closes-Bug: #1830179
    Change-Id: Ib956ff2f521b9853c58eaa5500836c692dd9321d

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/stein
Review: https://review.opendev.org/661023

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/661023
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=5c014c674087ef45b3c86d1440b977ce91852306
Submitter: Zuul
Branch: stable/stein

commit 5c014c674087ef45b3c86d1440b977ce91852306
Author: Jakub Libosvar <email address hidden>
Date: Wed May 22 13:47:37 2019 +0200

    Set force_config_drive only when OVNMetadata is disabled

    There are usecases when operator wants to talk to metadata API from
    config-drive script (e.g. using curl to get data from metadata). That
    means it makes sense to have OVN Metadata Agent deployed while forcing
    config-drive to be used.

    This patch sets force_config_drive to true only when OVNMetadataEnable
    is set to false. If it's set to true then it doesn't touch
    force_config_drive option, leaving it up to environment to define it.
    (The default for force_config_drive is false.)

    Conflicts:
        deployment/ovn/ovn-controller-container-puppet.yaml

    Closes-Bug: #1830179
    Change-Id: Ib956ff2f521b9853c58eaa5500836c692dd9321d
    (cherry picked from commit 7ac8e67d82e688382c3ea13c48b0cb55f759117b)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 11.0.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 10.6.0 release.

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/851345

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/851345
Committed: https://opendev.org/openstack/tripleo-heat-templates/commit/6c0410c74cee6e8809239f7a7877279723efec56
Submitter: "Zuul (22348)"
Branch: master

commit 6c0410c74cee6e8809239f7a7877279723efec56
Author: yatinkarel <email address hidden>
Date: Thu Jul 28 11:43:36 2022 +0530

    Set force_config_drive only when OVNMetadata is disabled

    It was already done in [1] but accidently reverted in [2],
    this patch fixes it. It got detected while investigation [3].

    Since the known metadata issue is now fixed in OVN, we can
    keep the force config drive disabled when OVN metadata is
    enabled.

    [1] https://review.opendev.org/660689
    [2] https://review.opendev.org/791415
    [3] https://bugs.launchpad.net/tripleo/+bug/1968732

    Related-Bug: #1830179
    Related-Bug: #1968732
    Depends-On: https://review.opendev.org/851342
    Change-Id: I7781505ed3080a4485baa83f8170eb6c361382b4