Summary:

gbenhaim said that creating a new hotfix release to be released via Errata advisory should be like "creating a new whole Y-stream version". It means:

• We'd need to use HoneyBadger to setup Errata release
• We'd need to use HoneyBadger to create new Brew tag (with *-candidate tag)

And to use HoneyBadger, we need to create a new yaml file for it (and it's not automated, since it's a new release and we lack of details). Only SP is allowed to merge new changes, and it takes time until SP engineer will review & merge it.

Note: For versions older than CNV 4.13, it should be done manually by opening SP tickets (If it won't be created by SP's rcm-ansible).

Issues:

1. CNV hotfix release is not tracked in Product Pages, and HoneyBadger is using that info (e.g. release date)

Also that affects stirabos's automation in hco-bundle-registry midstream (affects in a way that we can't automate hotfix release there)

2. Errata Tool requires CNV hotfix builds to be tagged to *-candidate tag (e.g. cnv-4.11-rhel-8-candidate)

We can't use *-candidate because it conflicts with regular Y/Z-stream releases. We'd need a new brew tag for it.

3. CNV 4.13 is managed by HoneyBadger, and versions older than CNV 4.13 are managed by SP's rcm-ansible automation [1]. I think there's a chance that SP will have no capacity to align with our requirements in the coming weeks.

[1] https://code.engineering.redhat.com/gerrit/gitweb?p=rcm-ansible.git;a=blob;f=roles/cnv/vars/main.yml