Duplicate configdrive while DHCP-less ramdisk clean/redeploy

We've discussed this issue during and after our weekly meeting, and that's the solution we're leaning towards:

1) Modify Glean [1] to optionally accept a hint for the IPA's configdrive in a new kernel parameter, e.g. glean-configdrive=LABEL=config-foo or glean-configdrive=UUID=bar (note: I'd rather avoid committing to using labels in case we figure out how to use UUIDs).

2) Modify Ironic's ISO building process [2] to generate a random label, e.g. config-<something> and pass it to Glean. This is going to be a breaking change, so we need to add it behind a flag with the intention to make it the default later.

[1] https://opendev.org/opendev/glean/src/branch/master/glean/init/glean-early.sh#L32
[2] https://opendev.org/openstack/ironic/src/commit/e4a5691d331c620f1e21d761c7de95e346f3effc/ironic/drivers/modules/image_utils.py#L425

I'm working on fixing this issue in change https://review.opendev.org/c/openstack/ironic-python-agent/+/895519

Additionally, an additional diskimage-builder change is currently in review which should improve overall security when dealing with configuration drives. https://review.opendev.org/c/openstack/diskimage-builder/+/899886

Reviewed: https://review.opendev.org/c/openstack/ironic-python-agent/+/895519
Committed: https://opendev.org/openstack/ironic-python-agent/commit/33f01fa3c2f32f447ed36f00fea68321c3991c2e
Submitter: "Zuul (22348)"
Branch: master

commit 33f01fa3c2f32f447ed36f00fea68321c3991c2e
Author: Julia Kreger <email address hidden>
Date: Fri Sep 15 15:03:30 2023 -0700

    Fix vmedia network config drive handling

    When performing DHCP-less deployments, the agent can start and
    discover more than one configuration drive present on a host.

    For example, a host was previously deployed using Ironic, and
    is now being re-deployed again.

    If Glean was present in the ramdisk, the glean-early.sh would end
    mounting the folder based upon label.

    If cloud-init, somehow is still in the ramdisk, the other folder
    could somehow get mounted.

    This patch, which is intended to be backportable, causes the agent
    to unmount any configuration drive folders, mount the most likely
    candidate based upon device type, partition, and overall state of
    the machine, and then utilize that configuration, if present,
    to re-configure and reload networking.

    Thus allowing dhcp-less re-deployments to be fixed without
    forcing any breaking changes.

    It should also be noted that this fix was generated in concert
    with an additional tempest test case, because this overall failure
    case needed to be reproduced to ensure we had a workable non-breaking
    path forward.

    Closes-Bug: 2032377
    Change-Id: I9a3b3dbb9ca98771ce2decf893eba7a4c1890eee

This issue was fixed in the openstack/ironic-python-agent 9.9.0 release.

Re-opening since this got reverted.

Reviewed: https://review.opendev.org/c/openstack/ironic/+/915022
Committed: https://opendev.org/openstack/ironic/commit/fb850e7f005e0ef4b5c489b8c2b245791d0d33eb
Submitter: "Zuul (22348)"
Branch: master

commit fb850e7f005e0ef4b5c489b8c2b245791d0d33eb
Author: Julia Kreger <email address hidden>
Date: Wed Apr 3 12:56:57 2024 -0700

    Inject a randomized publisher id

    To serve as a mechanism to allow an interlocking device identification
    this patch injects a publisher id value into ISO images *and* the kernel
    command line for any software running from the ISO image to match
    the ISO in use to the location of data housed locally from within the
    image.

    Related-Bug: 2032377
    Change-Id: I9b74ec977fabc0a7f8ed6f113595a3f1624f6ee6

Related fix proposed to branch: stable/2024.1
Review: https://review.opendev.org/c/openstack/ironic/+/917735

Related fix proposed to branch: stable/2023.2
Review: https://review.opendev.org/c/openstack/ironic/+/917861

Related fix proposed to branch: stable/2023.1
Review: https://review.opendev.org/c/openstack/ironic/+/917862

Reviewed: https://review.opendev.org/c/openstack/ironic/+/917735
Committed: https://opendev.org/openstack/ironic/commit/78c1d9a98d6ff175b3bfa5bdda6694a4cf30cff2
Submitter: "Zuul (22348)"
Branch: stable/2024.1

commit 78c1d9a98d6ff175b3bfa5bdda6694a4cf30cff2
Author: Julia Kreger <email address hidden>
Date: Wed Apr 3 12:56:57 2024 -0700

    Inject a randomized publisher id

    To serve as a mechanism to allow an interlocking device identification
    this patch injects a publisher id value into ISO images *and* the kernel
    command line for any software running from the ISO image to match
    the ISO in use to the location of data housed locally from within the
    image.

    Related-Bug: 2032377
    Change-Id: I9b74ec977fabc0a7f8ed6f113595a3f1624f6ee6
    (cherry picked from commit fb850e7f005e0ef4b5c489b8c2b245791d0d33eb)

Reviewed: https://review.opendev.org/c/openstack/ironic/+/917861
Committed: https://opendev.org/openstack/ironic/commit/c71e124f9c06fdb5fc0a19a29bc7fb25f71ece9e
Submitter: "Zuul (22348)"
Branch: stable/2023.2

commit c71e124f9c06fdb5fc0a19a29bc7fb25f71ece9e
Author: Julia Kreger <email address hidden>
Date: Wed Apr 3 12:56:57 2024 -0700

    Inject a randomized publisher id

    To serve as a mechanism to allow an interlocking device identification
    this patch injects a publisher id value into ISO images *and* the kernel
    command line for any software running from the ISO image to match
    the ISO in use to the location of data housed locally from within the
    image.

    Some differences exist with this patch due to refactoring changes in
    I8567a10b77cdc3785686b79defcdafd75af53df0 where the basic flow and
    logic was simplified just enough to require the logic to change
    a little bit.

    Related-Bug: 2032377
    Change-Id: I9b74ec977fabc0a7f8ed6f113595a3f1624f6ee6
    (cherry picked from commit fb850e7f005e0ef4b5c489b8c2b245791d0d33eb)
    (cherry picked from commit 78c1d9a98d6ff175b3bfa5bdda6694a4cf30cff2)

Reviewed: https://review.opendev.org/c/openstack/ironic/+/917862
Committed: https://opendev.org/openstack/ironic/commit/1060a570b7345f1b9fd898e08d4629607a44e2d4
Submitter: "Zuul (22348)"
Branch: stable/2023.1

commit 1060a570b7345f1b9fd898e08d4629607a44e2d4
Author: Julia Kreger <email address hidden>
Date: Wed Apr 3 12:56:57 2024 -0700

    Inject a randomized publisher id

    To serve as a mechanism to allow an interlocking device identification
    this patch injects a publisher id value into ISO images *and* the kernel
    command line for any software running from the ISO image to match
    the ISO in use to the location of data housed locally from within the
    image.

    Some differences exist with this patch due to refactoring changes in
    I8567a10b77cdc3785686b79defcdafd75af53df0 where the basic flow and
    logic was simplified just enough to require the logic to change
    a little bit. Furthermore, even going to 2023.1, some default
    configuration options were also removed as they were centered
    around GRUB v1.

    Related-Bug: 2032377
    Change-Id: I9b74ec977fabc0a7f8ed6f113595a3f1624f6ee6
    (cherry picked from commit fb850e7f005e0ef4b5c489b8c2b245791d0d33eb)
    (cherry picked from commit 78c1d9a98d6ff175b3bfa5bdda6694a4cf30cff2)
    (cherry picked from commit c71e124f9c06fdb5fc0a19a29bc7fb25f71ece9e)