distutils and cloudutils warnings when upgrading to 4.22.1.0
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 32
Description
### problem
I upgraded Cloudstack from version 4.22.0.1 to version 4.22.1.0 on Rocky Linux 10 via community packages.
During the packages upgrade the following errors are displayed:
```
Running scriptlet: cloudstack-common-4.22.1.0-1.noarch 10/10
/var/tmp/rpm-tmp.LLxpZf: line 2: unalias: cp: not found
Traceback (most recent call last):
File "", line 1, in
ModuleNotFoundError: No module named 'distutils'
```
and
```
Running scriptlet: cloudstack-agent-4.22.1.0-1.noarch 10/10
Running /usr/bin/cloudstack-agent-upgrade to update bridge name for upgrade from CloudStack 4.0.x (and before) to CloudStack 4.1 (and later)
Traceback (most recent call last):
File "/usr/bin/cloudstack-agent-upgrade", line 18, in
from cloudutils.networkConfig import networkConfig
ModuleNotFoundError: No module named 'cloudutils'
```
### versions
Cloudstack upgraded from 4.22.0.1 to 4.22.1.0
Rocky Linux 10
KVM hypervisor
### The steps to reproduce the bug
1. dnf upgrade cloudstack-management cloudstack-usage
2. dnf upgrade cloudstack-agent
3.
...
### What to do about it?
_No response_
Contributor guide
Research direction
Reproduce the upgrade on Rocky Linux 10, then inspect the package scriptlet and /usr/bin/cloudstack-agent-upgrade, including their imports of distutils and cloudutils.networkConfig. Trace how these modules are packaged and loaded during the upgrade. Done means the cloudstack-common and cloudstack-agent upgrades complete without these ModuleNotFoundError warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100