#11192 Ansible: vars/all/FedoraPreviousPrevious.yaml not being properly updated
Closed: Fixed by humaton. Opened by adamwill.

  • Describe the issue

vars/all/FedoraPreviousPrevious.yaml should have been set to True when F37 was released, and then back to False when F35 went EOL. It was not touched either time; it hasn't been touched since F34 EOL. So right now it's correct, but it is clearly missing from some SOPs.

  • When do you need this? (YYYY/MM/DD)

No immediate need to change it now, but it needs to be in some SOP to update this file at new release and EOL points.

  • When is this no longer needed or useful? (YYYY/MM/DD)

When we stop doing releases, I guess?

  • If we cannot complete your request, what is the impact?

Plays that use the FedoraPreviousPrevious or FedoraPreviousPreviousCycleNumber vars won't work correctly. I can't update the Greenwave config to use those vars because I can't trust that they'll be updated; I'd like to update it to use those vars (and the other cycle-related vars) so we don't have to remember to update that file manually at various points either. Currently we do have to remember to update that file manually, and frequently it does not happen.

@humaton (since he touched these files most recently)


Metadata Update from @humaton:
- Issue tagged with: docs

This was completely missing from our current SOP. I will make it part of the new docs.

the new docs have points in EOL and final release documents.

Metadata Update from @humaton:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata