autopatch/kernel
5
0
Fork 1
Code Issues Pull Requests Releases Activity

fix(autopatch): Updated the UKI secureboot find string in config.yaml from centossecureboot204 to centossecureboot804 to match the r #9

Merged
eabdullin merged 1 commits from agent-fix/a10s-20260706-082153 into a10s 2026-07-06 08:34:46 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
eabdullin commented 2026-07-06 08:21:53 +00:00
Owner
Copy Link

Automated fix by autopatch agent.

Summary: Updated the UKI secureboot find string in config.yaml from centossecureboot204 to centossecureboot804 to match the renamed certificate in the upstream spec.

Root cause

The ReplaceAction for the UKI secureboot block failed because the upstream kernel.spec (c10s branch) renamed the CentOS UKI secureboot certificate:

  • UKI_secureboot_name=centossecureboot204 became UKI_secureboot_name=centossecureboot804

The a10s config.yaml had a combined multi-line replace action that searched for the entire %if 0%{?centos} / %else / %endif block containing the old name centossecureboot204. Because the spec now uses centossecureboot804, the find string no longer matched and the action was skipped.

Fix applied: Updated the find value in the combined UKI secureboot replace action from centossecureboot204 to centossecureboot804. The replace side (which emits UKI_secureboot_name=%{pesign_name_0} and UKI_secureboot_cert=%{_datadir}/pki/sb-certs/secureboot-uki-virt-%{_arch}.cer) was left unchanged, preserving the debranding intent.

The reference branch (a10) did not have this fix — it still used three separate single-line replaces targeting the old centossecureboot204 value.

Original error

Type: ActionNotAppliedError

Traceback (most recent call last):
  File "/root/autopatch-tool/src/webserv.py", line 89, in debrand_packages
    result = apply_modifications(
  File "/root/autopatch-tool/src/debranding.py", line 120, in apply_modifications
    config.apply_actions(rpms_working_dir + f"/{package}")
  File "/root/autopatch-tool/src/actions_handler.py", line 938, in apply_actions
    action.execute(Path(package_path))
  File "/root/autopatch-tool/src/actions_handler.py", line 475, in execute
    process_lines(
  File "/root/autopatch-tool/src/actions_handler.py", line 236, in process_lines
    raise ActionNotAppliedError(
actions_handler.ActionNotAppliedError: Action 'ReplaceAction' was not applied successfully: No changes made for '['%if 0%{?centos}', '        UKI_secureboot_name=centossecureboot204', '        UKI_secureboot_cert=%{_datadir}/pki/sb-certs/secureboot-uki-virt-%{_arch}.cer', '%else', '\t# RHEL only builds UKI for x86', '\tUKI_secureboot_name=redhatsecureboot504', '\tUKI_secureboot_cert=%{SOURCE153}', '%endif']' in /root/autopatch-tool/src/rpms-namespace/kernel/kernel.spec

Package: kernel | Webhook branch: c10s

Automated fix by autopatch agent. **Summary:** Updated the UKI secureboot find string in config.yaml from `centossecureboot204` to `centossecureboot804` to match the renamed certificate in the upstream spec. ### Root cause The `ReplaceAction` for the UKI secureboot block failed because the upstream `kernel.spec` (c10s branch) renamed the CentOS UKI secureboot certificate: - `UKI_secureboot_name=centossecureboot204` became `UKI_secureboot_name=centossecureboot804` The a10s `config.yaml` had a combined multi-line replace action that searched for the entire `%if 0%{?centos}` / `%else` / `%endif` block containing the old name `centossecureboot204`. Because the spec now uses `centossecureboot804`, the find string no longer matched and the action was skipped. **Fix applied:** Updated the `find` value in the combined UKI secureboot replace action from `centossecureboot204` to `centossecureboot804`. The `replace` side (which emits `UKI_secureboot_name=%{pesign_name_0}` and `UKI_secureboot_cert=%{_datadir}/pki/sb-certs/secureboot-uki-virt-%{_arch}.cer`) was left unchanged, preserving the debranding intent. The reference branch (a10) did not have this fix — it still used three separate single-line replaces targeting the old `centossecureboot204` value. ### Original error **Type:** `ActionNotAppliedError` ``` Traceback (most recent call last): File "/root/autopatch-tool/src/webserv.py", line 89, in debrand_packages result = apply_modifications( File "/root/autopatch-tool/src/debranding.py", line 120, in apply_modifications config.apply_actions(rpms_working_dir + f"/{package}") File "/root/autopatch-tool/src/actions_handler.py", line 938, in apply_actions action.execute(Path(package_path)) File "/root/autopatch-tool/src/actions_handler.py", line 475, in execute process_lines( File "/root/autopatch-tool/src/actions_handler.py", line 236, in process_lines raise ActionNotAppliedError( actions_handler.ActionNotAppliedError: Action 'ReplaceAction' was not applied successfully: No changes made for '['%if 0%{?centos}', ' UKI_secureboot_name=centossecureboot204', ' UKI_secureboot_cert=%{_datadir}/pki/sb-certs/secureboot-uki-virt-%{_arch}.cer', '%else', '\t# RHEL only builds UKI for x86', '\tUKI_secureboot_name=redhatsecureboot504', '\tUKI_secureboot_cert=%{SOURCE153}', '%endif']' in /root/autopatch-tool/src/rpms-namespace/kernel/kernel.spec ``` --- Package: `kernel` | Webhook branch: `c10s`
eabdullin added 1 commit 2026-07-06 08:21:54 +00:00 
Updated the UKI secureboot find string in config.yaml from `centossecureboot204` to `centossecureboot804` to match the renamed certificate in the upstream spec.
eabdullin merged commit 34b83264d0 into a10s 2026-07-06 08:34:46 +00:00
eabdullin deleted branch agent-fix/a10s-20260706-082153 2026-07-06 08:34:46 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: autopatch/kernel#9
No description provided.
Delete Branch "agent-fix/a10s-20260706-082153"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?