fails on ubuntu jammy without --kayobe-in-requirements
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- ansible, python
- Domain
- devops, infrastructure
Research direction
Reproduce the failure on Ubuntu Jammy using the OpenStack 2024.1 or 2025.1 release, starting from the command that runs pip freeze and searches for kayobe. Compare behavior with and without --kayobe-in-requirements; done means the command succeeds without requiring that workaround.
Written by the indexing model from the issue text.
Description
Previously used --kayobe-in-requirements to work around this error:
fatal: [localhost]: FAILED! =>
changed: true
cmd: set -o pipefail && pip freeze | grep kayobe | cut -d @ -f 3
delta: '0:00:00.190243'
end: '2026-06-02 12:09:46.221401'
failed_when_result: true
msg: ''
rc: 0
start: '2026-06-02 12:09:46.031158'
stderr: ''
stderr_lines:
stdout: ''
stdout_lines:
OpenStack 2024.1/2025.1 release
- Dominant language
- Python
- Stars
- 6
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stackhpc/beokay
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100