Bug 1967274

We should likely change the project to tripleo-heat-templates because puppet-ironic work required is entirely to service technical debt to test configuration file generation testing, as I understand it at this point. Added appropriate links.

Hi Julia,

> change the project to tripleo-heat-templates
done

> OpenStack gerrit 797668 - puppet-ironic
  NOT backported to W ?

> OpenStack gerrit 802736 - tripleo-common
  backported and merged to W https://review.opendev.org/q/I28a3e1200567236d4f78bfddb7899490bbea267f

> OpenStack gerrit 802740 - tripleo-heat-templates
  backported and merged to W https://review.opendev.org/q/Ie75aa0f2994a4cf662905b912231a12e3bd8afe7

> OpenStack gerrit 806074 - tripleo-common
  backported and merged to W https://review.opendev.org/q/I28a3e1200567236d4f78bfddb7899490bbea267f

All linked reviews are now merged, what is left to do in THT ?

Greetings!

> 
> > OpenStack gerrit 797668 - puppet-ironic
>   NOT backported to W ?
> 

Merged yesterday, and likely need to chat with Takashi before backporting since the module is strictly needed for self testing the module, not actual configuration of the tftp containers, which comes from the tht embedded config.

> All linked reviews are now merged, what is left to do in THT ?

AFAIK, nothing. The module change is defaulted, and the underlying configuration files generated in this specific case are not used by the containers for product usage. They are directly launched via command line on the container.

Adding two tripleo-common changes to remove the container build inclusion of the tftp-server package. Second one is in the gate now, so it should be fine.

Hi,

I think we are good to backport the change in puppet-ironic, because it doesn't
change the default behavior in existing supported platforms.
AFAIK Alfredo has been trying integration tests on CentOS9 and ironic is now
tested as part of scenario003.
Unfortunately some core features like actual baremetal node deployment is not tested
in that job but it's a good starting point to ensure at last deployment completes
without failure.

The only blocker for puppet-ironic backport is that we are now creating the Xena release
of Puppet OpenStack. The patch for puppet-ironic landed too later for the release.
We can start backporting the change to Xena and Wallaby once stable/xena is created and
we merge some basic changes in helpers for CI.


Note the change in ironic-distgit[1] is not yet backported to RDO Xena and RDO Wallaby.
Because the change in puppet-ironic depends on the change in RDO package(the new package
and service) we need backport in RDO first.

[1] https://review.rdoproject.org/r/c/openstack/ironic-distgit/+/34691

(In reply to Takashi Kajinami from comment #8)
> Hi,
> 
> I think we are good to backport the change in puppet-ironic, because it
> doesn't
> change the default behavior in existing supported platforms.
> AFAIK Alfredo has been trying integration tests on CentOS9 and ironic is now
> tested as part of scenario003.
> Unfortunately some core features like actual baremetal node deployment is
> not tested
> in that job but it's a good starting point to ensure at last deployment
> completes
> without failure.
> 
> The only blocker for puppet-ironic backport is that we are now creating the
> Xena release
> of Puppet OpenStack. The patch for puppet-ironic landed too later for the
> release.
> We can start backporting the change to Xena and Wallaby once stable/xena is
> created and
> we merge some basic changes in helpers for CI.
> 
> 
> Note the change in ironic-distgit[1] is not yet backported to RDO Xena and
> RDO Wallaby.
> Because the change in puppet-ironic depends on the change in RDO package(the
> new package
> and service) we need backport in RDO first.
> 

Let's get the scenario passing in p-o-i in master and then we can start backporting distgit change to xena.

Apparently after https://review.opendev.org/c/openstack/puppet-ironic/+/812806 we should be fine.


> [1] https://review.rdoproject.org/r/c/openstack/ironic-distgit/+/34691

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2022:6543