max/vmn-ansible
1
1
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

[BUG]: OMZ installation fails #16

New Issue
Closed
opened 2026-09-14 16:03:56 +04:00 by max · 5 comments
max commented 2026-09-14 16:03:56 +04:00
Owner
Copy Link
Copy Source

📋 Description

oh-my-zsh script is copied to a newly created host, but omz is not installed

🔁 Steps to Reproduce

  1. Run deployment playbook (both LXC and VM fails)
  2. Login to the new machine as human admin user
  3. No omz installed

✅ Expected Behavior

OMZ is installed automatically and shows up when human user logs in

❌ Actual Behavior

OMZ is not installed automatically and user has to install it manually by running the script when first log in

📄 Logs / Screenshots

No response

📦 Audio Splitter Version

dev

💻 Operating System

any

🌍 Browser (if applicable)

No response

📎 Additional Context

No response

✅ Submission Checklist

  • I have searched for existing issues (open and closed) that report the same problem
  • I am using the latest stable release of Audio Splitter
  • I have provided clear steps to reproduce the issue
  • I have included relevant logs or error messages (with sensitive info removed)
### 📋 Description oh-my-zsh script is copied to a newly created host, but omz is not installed ### 🔁 Steps to Reproduce 1. Run deployment playbook (both LXC and VM fails) 2. Login to the new machine as human admin user 3. No omz installed ### ✅ Expected Behavior OMZ is installed automatically and shows up when human user logs in ### ❌ Actual Behavior OMZ is not installed automatically and user has to install it manually by running the script when first log in ### 📄 Logs / Screenshots _No response_ ### 📦 Audio Splitter Version dev ### 💻 Operating System any ### 🌍 Browser (if applicable) _No response_ ### 📎 Additional Context _No response_ ### ✅ Submission Checklist - [x] I have searched for existing issues (open and closed) that report the same problem - [x] I am using the latest stable release of Audio Splitter - [x] I have provided clear steps to reproduce the issue - [ ] I have included relevant logs or error messages (with sensitive info removed)
max added the bug label 2026-09-14 16:03:57 +04:00
max commented 2026-09-16 10:13:25 +04:00
Author
Owner
Copy Link
Copy Source

It seems that LXCs with debian are not affected by this issue. We need to test:

  • VM with Debian
  • VM with Alpine
It seems that LXCs with debian are not affected by this issue. We need to test: - [x] VM with Debian - [x] VM with Alpine
max commented 2026-09-16 12:28:31 +04:00
Author
Owner
Copy Link
Copy Source

VM with Debian fails, omz is not installed. For some reason ansible tries to install it as root and fails, as expected. But task specifies: remote_user: "{{ human_admin_user }}"

VM with Debian fails, omz is not installed. For some reason ansible tries to install it as root and fails, as expected. But task specifies: remote_user: "{{ human_admin_user }}"
max commented 2026-09-16 13:12:53 +04:00
Author
Owner
Copy Link
Copy Source

Using sudo -u $USER in the script seems to solve the issue, omz is installed successfully, it exits with non-zero code though

Using sudo -u $USER in the script seems to solve the issue, omz is installed successfully, it exits with non-zero code though
max changed title from [BUG]: OMZ installtion fails to [BUG]: OMZ installation fails 2026-09-16 13:13:34 +04:00
max commented 2026-09-16 13:39:17 +04:00
Author
Owner
Copy Link
Copy Source

VMs with Debian passed. Alpine needs to be tested

VMs with Debian passed. Alpine needs to be tested
max commented 2026-09-16 15:29:24 +04:00
Author
Owner
Copy Link
Copy Source

Alpine fails because sudo on this system requires additional configuration

Alpine fails because sudo on this system requires additional configuration
max added a new dependency 2026-09-16 16:49:42 +04:00
#35 [BUG]: sudo on Alpine doesn't work out-of-the-box
max closed this issue 2026-09-16 17:31:22 +04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
 documentation
issues related to documentation (typo, old info, inconsistencies, etc)
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
max
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Depends on
#35 [BUG]: sudo on Alpine doesn't work out-of-the-box
max/vmn-ansible
Reference: max/vmn-ansible#16
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?