Sometimes modules take a very long time to install
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 558
- Forks
- 224
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 1
Description
Describe the Bug
Sometimes, during the installation of the module, the processor starts to take 100% and the installation itself may take several hours. Try on MacAir/MacMini/Linux Rocky
Expected Behavior
The usual installation takes little time
Steps to Reproduce
This happens sometimes when adding a new module to a project
bolt module add openstack-glance
modules:
- puppetlabs/git
- puppet/consul
- puppet/nomad
- puppetlabs/docker
- puppet/vault
- puppet/vault_lookup
- puppet/ssh_keygen
- puppetlabs/vcsrepo
- puppet/archive
- puppet/extlib
- puppetlabs/firewall
- puppet/wireguard
- puppetlabs/inifile
- saz/timezone
- puppet/chrony
- puppet/systemd
- puppet/ferm
- puppetlabs/lvm
- saz/ssh
- openstack/keystone
- puppetlabs/apache
Strace bolt process
futex(0x11ab320, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x11ab390, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, FUTEX_BITSET_MATCH_ANY) = 0
futex(0x11ab320, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x4165844, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x11ab320, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x11ab394, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, FUTEX_BITSET_MATCH_ANY) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x11ab320, FUTEX_WAKE_PRIVATE, 1) = 0
Environment
❯ bolt --version
3.26.2
MacOS - Version 13.2.1 (22D68)
Contributor guide
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.
Research direction
Start by reproducing bolt module add openstack-glance with the listed modules on the reported environments, using the provided strace bolt output as a starting point. Trace the module installation path and define done as an installation that completes in the usual short time without sustained 100% processor usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100