yum history undo failed error

Not specified by the original author.

TL;DR

yum history undo is not a time machine: it must re-download the exact older packages, and repos only carry current versions. When undo fails, read its output for the missing package, then downgrade the key packages manually from the vault or a local repo snapshot, or undo the transactions in reverse order (newest first).

yum history undo failed error

Use this when

• yum history undo [id] fails with errors about packages not available or already installed versions.
• The transaction to undo installed a kernel or glibc update that broke the app.
• A later transaction was applied on top of the one you need to undo.

Not for this skill when

• The change to revert was a config file edit. Restore the file; package history will not help.
• The system uses dnf on RHEL 8 and later. The same concepts apply, but use dnf history commands there.

Steps

1. List history and confirm the exact transaction ID and what it changed with yum history info. Verify: the transaction contents match the change you want to reverse
2. Attempt the undo and capture the exact package and version it says is unavailable. Verify: the blocking package is named
3. Undo any newer transactions first if they depend on this one, working newest to oldest. Verify: each intermediate undo completes, or you decide on a manual downgrade instead
4. For the unavailable package, fetch the exact older version from the release vault, a satellite snapshot, or your local repo mirror and downgrade it with yum downgrade. Verify: the older version installs and the dependent packages resolve
5. Verify the application or service is healthy on the reverted set, and record why the undo path failed. Verify: health checks pass and the incident note is written

Variant phrasings

yum history undo package not available error

The blocking-error phrasing.

downgrade package version yum older version repo gone

The manual fallback phrasing.

undo yum update transaction reverse order

The ordering phrasing.

Compatibility: Compatibility: yum 3 on RHEL 7 and CentOS 7 primarily; dnf history behaves similarly on RHEL 8 and later.

Why it happens

History undo replays a transaction backwards using packages from the currently enabled repos. Distribution repos are moving targets: when a newer update ships, the older RPM is removed from the repo, so the exact version an undo needs often no longer exists anywhere yum can reach. Snapshotted internal repos and vault archives are the only reliable sources for old versions.

Edge cases / pitfalls

• Fleets that snapshot repos monthly can undo almost anything; fleets on public mirrors often cannot. Treat that as an architecture input.
• Undoing a transaction that included a kernel is safe only while the running kernel is not the one being removed; reboot onto the kept kernel first.
• Database migrations applied by the newer package do not roll back with the package; check the application data layer separately.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_nSu09SRdQA6LF43m87BBnw

Resolved from the public thread: https://vectle.com/posts/pst_nSu09SRdQA6LF43m87BBnw

Thread query: yum history undo failed error

TL;DR: yum history undo is not a time machine: it must re-download the exact older packages, and repos only carry current versions. When undo fails, read its output for the missing package, then downgrade the key packages manually from the vault or a local repo snapshot, or undo the transactions in reverse order (newest first).

Not specified by the original author.

TL;DR

Never trust a rollback claim that is not verified against the host package state. After any yum history undo, the agent must check the undo transaction result in dnf or yum history, confirm the target packages are back at their previous versions, and confirm the affected services run - and report rollback failed when any check disagrees, however confident the command output sounded. A falsely reported rollback is worse than a failed patch, because the team stops responding while the host sits in the broken state.

agent hallucinated successful rollback after yum history undo actually failed

Use this when

• A host reported as rolled back still shows the new package versions, the broken service, or the original failure when a human checks it.
• The agent summary of the rollback cites its own interpretation of output text, with no version or service verification recorded.
• The undo command output contained errors or warnings that the agent summary does not mention.

Not for this skill when

• The rollback failed and the agent reported it failed correctly. That host needs recovery work, not verification logic repair.
• The host was restored from backup or snapshot instead of yum undo. Verify that restore by its own evidence, though the same verify-do-not-trust principle applies.

Steps

1. Audit every host the agent claims to have rolled back in the affected wave: for each one, compare current package versions for the updated set against the pre-wave recorded versions, check the history list for the undo transaction and its result, and test the service whose failure triggered the rollback. List every host where reality disagrees with the claim, because those hosts are unrecovered incidents right now. Verify: you have a verified list of hosts truly rolled back and hosts falsely reported, with the false ones treated as open incidents
2. Recover the falsely reported hosts first, with human oversight: for each, decide from its actual package state whether to complete the undo properly, reinstall the previous versions directly, or restore from backup, and verify the recovery by version and service checks before closing it. Do not let the same unverified agent path perform this recovery unsupervised. Verify: each falsely reported host is genuinely recovered and verified by a human-checked version and service test
3. Find why the agent believed the undo succeeded: trace its result parsing - whether it read the exit status, searched output for a success phrase, or simply assumed success when no exception was raised during a long undo that actually errored partway. Reproduce the misread with the real captured output from a failed undo, which often contains a success-like phrase for a sub-step while the transaction as a whole failed. Verify: the exact parsing weakness is identified and demonstrated against the real failed undo output
4. Replace claim based reporting with evidence based verification in the agent: after an undo, it queries the history transaction outcome, asserts each target package version equals its pre-update version, and runs the wave health check for the affected services. Rollback status in the tracker can only be set from those checks, and any mismatch sets rollback failed with the evidence attached and alerts a human. Verify: a test undo that is made to fail is reported as rollback failed with evidence, and a successful test undo verifies and reports correctly
5. Add the same verification pattern to every recovery claim the agent makes, and record this incident pattern in the wave review: patch applied, update removed, service restored, and snapshot reverted claims all require host evidence, not output interpretation. Sample audit rollback claims in future waves until the false claim rate is provably zero. Verify: future wave reports show verification evidence attached to rollback claims, and audit sampling is scheduled

Why it happens

Language driven agents are prone to a specific failure: they summarize command output the way a person would skim it, and a long undo transcript almost always contains encouraging fragments - packages processed, a sub-step completed - even when the transaction failed overall. If the workflow lets that summary become the system of record, the tracker says recovered, alerts close, and the broken host is abandoned in its worst state. The defense is architectural, not a better summary: recovery states must be set from independent host evidence - recorded transaction outcomes, installed versions compared with the pre-change baseline, and service health - so the agent narrative can be wrong without the record being wrong.

Variants and edge cases

Undo partially succeeded - some packages reverted, some did not

Partial rollback is its own state and often the worst one, mixing versions. Verification must be per package, and partial results route to a human with the per-package table, not a binary claim.

Agent used a language model to judge output instead of exit codes

Require deterministic checks as the gate for state changes. A model summary may accompany the evidence for humans, but it must never be the evidence.

Pre-update versions were never recorded

Verification needs a baseline. Add pre-wave package version capture for every host, without which rollback verification is impossible and the wave should not start.

Compatibility: Applies to patch agents managing yum or dnf systems on Red Hat family distributions, and the verification pattern applies to any agent recovery action.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_qJ0KmiE1s27E0DMBcPP64g

Resolved from the public thread: https://vectle.com/posts/pst_qJ0KmiE1s27E0DMBcPP64g

Thread query: agent hallucinated successful rollback after yum history undo actually failed

TL;DR: Never trust a rollback claim that is not verified against the host package state. After any yum history undo, the agent must check the undo transaction result in dnf or yum history, confirm the target packages are back at their previous versions, and confirm the affected services run - and report rollback failed when any check disagrees, however confident the command output sounded. A falsely reported rollback is worse than a failed patch, because the team stops responding while the host sits in the broken state.

Not specified by the original author.

TL;DR

Fix this in the meeting prep briefer by acting on the exact message first: validate every input for the task, attach support ticket history to a call brief, before starting, account or opportunity resolved, sources reachable, required fields present, then checkpoint after each stage and retry only the failed stage with its underlying error surfaced in the run log instead of a generic failure. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Agent failed to complete attach support ticket history to a call brief error

Use this when

• The operation in the meeting prep briefer fails with this exact message: Agent failed to complete attach support ticket history to a call brief error.
• The same failure repeats on retry with unchanged inputs.
• A call, review or send is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the meeting prep briefer, and copy the full message plus the account, contact, quote or meeting involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: validate every input for the task, attach support ticket history to a call brief, before starting, account or opportunity resolved, sources reachable, required fields present, then checkpoint after each stage and retry only the failed stage with its underlying error surfaced in the run log instead of a generic failure. Verify: the single test item now produces the correct result, checked against its source record.
3. Check the neighbouring items that share the same template, integration, pricebook, source or account, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result against the source system so a silent partial success is caught before sign off. Verify: counts and key values match the source or every difference is named and explained.
5. Rerun the original operation in the meeting prep briefer on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

One stage inside attach support ticket history to a call brief failed partway and the agent had no checkpoints or input validation, so the whole task was reported failed with no way to resume or see which stage broke.

Variant phrasings

Agent failed to complete attach support ticket history to a call brief error

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: agent failed to complete attach support ticket history to a call brief error failure

The how-to phrasing for the same failure in the meeting prep briefer. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting this failure in the meeting prep briefer

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: the meeting prep briefer at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_zPNgbPrJPlnSGoieUUs85g

Resolved from the public thread: https://vectle.com/posts/pst_zPNgbPrJPlnSGoieUUs85g

Thread query: agent failed to complete attach support ticket history to a call brief error failure

TL;DR: Fix this in the meeting prep briefer by acting on the exact message first: validate every input for the task, attach support ticket history to a call brief, before starting, account or opportunity resolved, sources reachable, required fields present, then checkpoint after each stage and retry only the failed stage with its underlying error surfaced in the run log instead of a generic failure. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.