Running 'scaley scale' as non-root reports 'group ops are locked'

Open
#23 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
go
Domain
cli, devops

Research direction

Start by reproducing scaley scale mygroup as a non-root user with and without /var/run/scaley/lock, then trace the lock-folder and group-operation handling in the Go entry points. Done means a configured group can be scaled as non-root without the lock-folder error or the spurious “Group operations are locked” message.

Written by the indexing model from the issue text.

Description

bug

Precondition: scaley installed and a group configured
Reproduction:

  • run scaley scale mygroup as non-root fails with can't create lock folder /var/run/scaley/lock
  • create folder /var/run/scaley/lock having the non-root user as owner
  • run scaley scale mygroup as non-root fails with `Group operations are locked for xyz'

Nothing of the above happens if 'scaley' is run as root

Dominant language
Go
Stars
0
Forks
0
No merged PRs in 30d

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.

More from engineyard/scaley

All issues in engineyard/scaley

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.