uabrc / uabrc/devops-docs

Script to Add Missing Cheaha User Accounts

Open
#50 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1
Forks
9
PR merge metrics
No merged PRs in 30d

Description

If Cheaha user accounts aren't added correctly, it can lead to various issues for those users. When launching an HPC desktop job, users may encounter an internal server error and Permission denied errors. Also, using srun may result in an invalid account partition error. These errors occur despite the successful creation of the user account.

Reference issue: RITM0702342

To add a missing Cheaha user account, you can execute the following script. We recommend adding this to your $HOME/.bashrc to have quick access to the function.

function slurm-add-account() {
    users=("${@:1}")

    for user in "${users[@]}"; do
      echo "$user"
      /cm/shared/apps/slurm/current/bin/sacctmgr --immediate add Account $user
      /cm/shared/apps/slurm/current/bin/sacctmgr --immediate add User Accounts=$user $user
    done

    for user in "${users[@]}"; do
      sacctmgr show Account $user
      sacctmgr show user $user
    done
}

To utilize this function, slurm-add-account, you simply need to input your username after the command. You can also add multiple usernames separated by spaces.
slurm-add-account user1 user2 user3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the repository's documentation structure and searching for existing Cheaha or Slurm-related pages. Use the issue text and the slurm-add-account function as the source material; done means the missing-account procedure, command usage, and multiple-user example are documented in the appropriate location.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.