canonical / canonical/sysbench-operator
Cannot start performance test on ARM K8s: Action id 32 failed: Failed: sysbench is not prepared
- Dominant language
- Python
- Stars
- 2
- Forks
- 1
- Avg merge
- 9h 7m
- Merged PRs (30d)
- 11
Description
## Steps to reproduce
1. juju set-model-constraints arch=arm64
2. juju deploy postgresql-k8s --trust --channel 14/edge --config profile=testing
3. juju deploy sysbench
4. juju config sysbench threads=1 scale=1 duration=300
5. juju relate sysbench postgresql-k8s
6. wait for all stable
7. juju run sysbench/leader prepare
```
taurus@pi5juju:~$ juju run sysbench/leader prepare
Running operation 29 with 1 task
- task 30 on unit-sysbench-0
Waiting for task 30...
ERROR timed out waiting for results from: unit sysbench/0
...
taurus@pi5juju:~$ juju show-task 30
status: prepared
taurus@pi5juju:~$ juju run sysbench/leader run
Running operation 31 with 1 task
- task 32 on unit-sysbench-0
Waiting for task 32...
Action id 32 failed: Failed: sysbench is not prepared
```
## Expected behavior
No errors and test on Microk8s started the same way as on LXD.
I have feeling it used to work earlier... and lost in the last revisions.
## Actual behavior
Cannot start performance test.
## Versions
Operating system: Ubuntu 23.10
Juju CLI: 3.4.2-genericlinux-arm64
Juju agent: see above
Charm revision: see above
LXD: not applicable
MicroK8s: MicroK8s v1.30.0 revision 6788 (strict)
```
taurus@pi5juju:~$ juju status
Model Controller Cloud/Region Version SLA Timestamp
arm m2k8s microk8s/localhost 3.4.2 unsupported 03:04:09+02:00
App Version Status Scale Charm Channel Rev Address Exposed Message
postgresql-k8s 14.11 active 1 postgresql-k8s 14/edge 248 10.152.183.57 no Primary
sysbench active 1 sysbench latest/stable 25 10.152.183.154 no
Unit Workload Agent Address Ports Message
postgresql-k8s/0* active idle 10.1.46.58 Primary
sysbench/0* active idle 10.1.46.63
```
Juju debug-log is clean... no errors.
Contributor guide
Assessment
This issue has not been assessed yet.