---
id: "bug-1712"
status: "open"
status_updated: "2026-09-24"
status_note: "xce_test resupdate duplicate -v gives misleading message"
component: "controller"
severity: "unknown"
timestamp: "2026-08-26T09:32:18Z"
last_seen: "2026-09-19T09:00:00Z"
occurrences: 1
files: ["src/controller/testsuite/test.c:3525-3531 (case 'v' else-branch)"]
tags: ["controller", "testsuite", "xce_test", "cmd_resupdate", "misleading-error-message", "cli-ux-audit"]
related: ["bug-1706", "bug-1707"]
legacy: true
---

# bug-1712: cmd_resupdate: a duplicate -v for the same pending resource (`resupdate -n slots -v 4 -v 8`)…

## Description
cmd_resupdate: a duplicate -v for the same pending resource (`resupdate -n slots -v 4 -v 8`) prints the misleading message "ignore res value `%s' as no res name found" even though a resource name WAS found -- the real problem is a value is already pending for it, not a missing name.

## Environment
_Not recorded (migrated from buglog.json)._

## Reproduction
_Not recorded (migrated from buglog.json)._

## Root cause
The else-branch of the -v case handles two distinct situations (no preceding -n at all, vs. a duplicate -v for an already-named pending resource) with one shared, incorrectly-worded message.

## Fix
NOT YET FIXED. Recommended: distinguish the two cases with an accurate message for the duplicate-value case, e.g. "ignoring duplicate value '%s' for res '%s' (already has a pending value)".

## Verification
_Not recorded (migrated from buglog.json)._

## References
- Related: bug-1706, bug-1707