lsf_job_pend

What problem does it solve?

It helps you quickly diagnose why an LSF/OpenLava/Volclava job remains in PEND state and doesn’t start, so you can identify the real scheduling blocker and act immediately.

Core Features & Use Cases

• PEND Root-Cause Diagnosis: Determines the underlying Pending Reason (as reported by the scheduler) and selects targeted checks for slot limits, resource mismatches, license shortages, queue/host state issues, dependency problems, and user limits.
• Actionable Evidence Collection: Gathers the required job, queue, host, and (when applicable) license information, then summarizes the diagnosis using concrete command outputs and key fields.
• Fix-First Reporting: Produces an output plan including immediate copy-pastable remediation steps and longer-term prevention guidance.

Quick Start

Ask the skill: “Diagnose why my LSF job is stuck in PEND and give me the exact commands to fix it, using my job’s pending reason and job id.”