cluster: reliably execute commands#1176
cluster: reliably execute commands#1176achuzhoy wants to merge 1 commit intorh-ecosystem-edge:mainfrom
Conversation
📝 WalkthroughWalkthroughReplaces line-by-line stdout processing with a single concatenated output string for NTP source verification and swaps the command helper from Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
No actionable comments were generated in the recent review. 🎉 Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 golangci-lint (2.5.0)Command failed Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@tests/internal/cluster/cluster.go`:
- Line 156: The hostnameCmd slice is incorrectly a single-element slice, so
ExecCommand will search for an executable named "chroot /rootfs sh -c 'printf
$(hostname)'"; update hostnameCmd to be a proper argv slice (e.g.
[]string{"sh","-c","chroot /rootfs sh -c 'printf $(hostname)'"} or split into
[]string{"chroot","/rootfs","sh","-c","printf $(hostname)"}) so ExecCommand
receives separate args, and leave the variable name hostnameCmd and the call
site to ExecCommand unchanged.
8c7c77b to
6c28185
Compare
Previous way of executing commands against nodes doesn't seem to work properly anymore Signed-off-by: Alexander Chuzhoy <achuzhoy@redhat.com>
Previous way of executing commands against nodes
doesn't seem to work properly anymore
Summary by CodeRabbit