lp:charm-ironic-conductor

Author: Billy Olsen
Author Date: 2025-11-13 19:36:45 UTC

Specify the uefi_ipxe_bootfile_name in config

The uefi_ipxe_bootfile_name is not specified in the config file and
thus defaults to snponly.efi. However, this can cause incorrect boot
and so use the undionly.kpxe value.

Closes-Bug: #2127951

Change-Id: Iafe66ca7ce2e69abe863b52c741327914eb5da93
Signed-off-by: Billy Olsen <billy.olsen@canonical.com>
Signed-off-by: Felipe Reyes <felipe.reyes@canonical.com>
(cherry picked from commit d59eaf1b6dd1ef6a39ce6d7a48664c64f7d07b60)

Author: Billy Olsen
Author Date: 2025-11-13 19:36:45 UTC

Specify the uefi_ipxe_bootfile_name in config

The uefi_ipxe_bootfile_name is not specified in the config file and
thus defaults to snponly.efi. However, this can cause incorrect boot
and so use the undionly.kpxe value.

Closes-Bug: #2127951

Change-Id: Iafe66ca7ce2e69abe863b52c741327914eb5da93
Signed-off-by: Billy Olsen <billy.olsen@canonical.com>
Signed-off-by: Felipe Reyes <felipe.reyes@canonical.com>

Author: Felipe Reyes
Author Date: 2025-03-14 20:08:03 UTC

Use charm specific job templates

The openstack-python3-ussuri-jobs template is running on noble (python
3.12) making the pep8 tox target fail due to the dependencies and
versions locked down by the charm.

This change makes the charm to use the
openstack-python3-charm-jobs-ussuri template which runs on focal and
it's owned by the openstack charms team.

For the coverage report, the openstack-cover-charm-jobs template is used
now which provides the same guarantees described earlier

Change-Id: I0ced3d08f1df1c920f17e568e406d5167b2b7696

Author: Jadon Naas
Author Date: 2024-08-10 01:07:53 UTC

Update pinned version of Python cryptography

The cryptography module was being pinned to `<3.4` since it was the
version that introduced a build dependency on Rust, since then this
charm gained support to produce binary charms (38e8d49).

This change bumps up the cryptography pinning to 40.0.2, because that's
the version used by the stable/2023.1 branch, this prevents
from an older version (yoga) run a newer version than a later release
(antelope).

The reason why we need to bump up the cryptography version is to allow
the charm without errors when deployed on a FIPS enabled environment.

Closes-Bug: #1999545
Related-Bug: #1975491
Change-Id: I5961614fe0099c4f35b183e759d007ef279a0d48

Author: Alex Kavanagh
Author Date: 2023-10-17 17:01:33 UTC

Updates for testing period for 23.10 release

* charm-helpers sync for classic charms
* build.lock file for reactive charms
* ensure tox.ini is from release-tools
* Locked requirements using pip-compile:
  * existing (test-)requirements.txt ->
    (test-)requirements.in
  * pip-compile to *-py3[8|10].txt using python3.8
    and python3.10.
  * Updated tox.ini to use the appropriate merged
    requirements-*.txt files.
* Removal of lunar from metadata, charmcraft.yaml
  osci.yaml, tests.yaml and associated bundles.
* Locked libs and tests to stable/bobcat branches for:
  * charm-helpers
  * charms.openstack
  * zaza
  * zaza-openstack-tests

Change-Id: I518b987e11a29f617af8e077ed365d0bd3ab913a

Author: Corey Bryant
Author Date: 2023-07-06 20:03:02 UTC

Use service_domain in [service_user] section

Rebuild to update [service_user] config to use the service domain.
This was fixed in charm-helpers.

The keystone charm currently creates two service users, one for the
service domain (for v3 authentication), and the other for the default
domain (for v2 authentication). The [service_user] config needs to
use the service domain.

Closes-Bug: #2026202
Change-Id: I97e5d6aecf977e0217665c83c63b69672da0590c

Author: Corey Bryant
Author Date: 2023-07-06 20:02:18 UTC

Use service_domain in [service_user] section

Rebuild to update [service_user] config to use the service domain.
This was fixed in charm-helpers.

The keystone charm currently creates two service users, one for the
service domain (for v3 authentication), and the other for the default
domain (for v2 authentication). The [service_user] config needs to
use the service domain.

Closes-Bug: #2026202
Change-Id: Iba684eef4fa638d4321171decdc5d079eac7aa6a

Author: Corey Bryant
Author Date: 2023-07-06 20:01:26 UTC

Use service_domain in [service_user] section

Rebuild to update [service_user] config to use the service domain.
This was fixed in charm-helpers.

The keystone charm currently creates two service users, one for the
service domain (for v3 authentication), and the other for the default
domain (for v2 authentication). The [service_user] config needs to
use the service domain.

Closes-Bug: #2026202
Change-Id: I6cb98e6a74437efccd028b27d2e6aa5cd547a340

Author: Corey Bryant
Author Date: 2023-07-06 19:58:18 UTC

Use service_domain in [service_user] section

Rebuild to update [service_user] config to use the service domain.
This was fixed in charm-helpers.

The keystone charm currently creates two service users, one for the
service domain (for v3 authentication), and the other for the default
domain (for v2 authentication). The [service_user] config needs to
use the service domain.

Closes-Bug: #2026202
Change-Id: I67fa174a0afd1790f49ca27f7681c7a570b21d0e

Author: Corey Bryant
Author Date: 2023-07-06 19:57:13 UTC

Use service_domain in [service_user] section

Rebuild to update [service_user] config to use the service domain.
This was fixed in charm-helpers.

The keystone charm currently creates two service users, one for the
service domain (for v3 authentication), and the other for the default
domain (for v2 authentication). The [service_user] config needs to
use the service domain.

Closes-Bug: #2026202
Change-Id: I053c866d147ad5ef828b8ad2333b14964e93fd85

Author: Corey Bryant
Author Date: 2023-01-13 20:06:41 UTC

Pin tox to < 4.0.0

Tox 4.0.0 was recently released and it has several breaking changes.
We pin to < 4.0.0 here. We are planning to move forward only on the
master charm branches.

Tox is also pinned to < 4.0.0 for stable branches in upstream
openstack-zuul-jobs as well as in zosci-config. However, the
requires= section in the charm's tox.ini file ends up installing
tox>4, wiping out the zuul-pinned tox<4 that was already installed
installed. This patch fixes that.

Related-Bug: #2002788
Change-Id: I6add653a61220766e103688aaf47b2ba1ba36f06

Author: Alex Kavanagh
Author Date: 2021-10-21 13:49:40 UTC

21.10 - Release

Remove the "channel: candidate" from the func-test
bundles.

Change-Id: Iad55cdc1534ffc2390b1133fe6e0dc64034af359

Author: Alex Kavanagh
Author Date: 2021-10-21 13:49:40 UTC

21.10 - Release

Remove the "channel: candidate" from the func-test
bundles.

Change-Id: Iad55cdc1534ffc2390b1133fe6e0dc64034af359

Author: Alex Kavanagh
Author Date: 2021-10-21 13:49:40 UTC

21.10 - Release

Remove the "channel: candidate" from the func-test
bundles.

Change-Id: Iad55cdc1534ffc2390b1133fe6e0dc64034af359

Author: Alex Kavanagh
Author Date: 2021-10-21 13:49:40 UTC

21.10 - Release

Remove the "channel: candidate" from the func-test
bundles.

Change-Id: Iad55cdc1534ffc2390b1133fe6e0dc64034af359

Author: Aurelien Lourot
Author Date: 2021-07-22 12:54:56 UTC

Sync release-tools

In order to fix ResolutionImpossible on tox invocation.

https://github.com/openstack-charmers/release-tools/issues/151
https://github.com/openstack-charmers/release-tools/pull/152

Change-Id: I91666f3f1abc8753cb5136af04f99e91dd7b2aea
(cherry picked from commit 00f6602cfe25bc7fafb464908f0f5e9e4f3e71e7)

Author: Aurelien Lourot
Author Date: 2021-02-10 19:08:08 UTC

Updates for stable branch creation 21.01

Set default branch for git review/gerrit.
Switch tests to stable.
Switch to using stable charm-helpers branch.
Switch to using stable charm.openstack branch.
Switch to using stable zaza branch.
Switch to using stable zaza-openstack-tests branch.

Change-Id: Ia08c8e7dfd52472cee078c2dc8839eef2beadac6