When run on a multi-cpu host/vm, swift-storage charm amulet test fails with: workers:2 != expected workers:1
Bug #1440961 reported by
Ryan Beisner
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Swift Storage Charm |
Fix Released
|
Low
|
Ryan Beisner | ||
| swift-storage (Juju Charms Collection) |
Invalid
|
Low
|
Ryan Beisner | ||
Bug Description
When run on a multi-cpu host/vm, swift-storage charm amulet test fails with: workers:2 != expected workers:1
juju-test.
When run on a single-core host, the amulet test passes with the hard-coded "1" expectation.
Related branches
| description: | updated |
Revision history for this message
| Seyeong Kim (seyeongkim) wrote | #1 |
| Changed in swift-storage (Juju Charms Collection): | |
| assignee: | nobody → Ryan Beisner (1chb1n) |
| status: | New → Confirmed |
| Changed in swift-storage (Juju Charms Collection): | |
| status: | Confirmed → New |
| Changed in swift-storage (Juju Charms Collection): | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in charm-swift-storage: | |
| assignee: | nobody → Ryan Beisner (1chb1n) |
| importance: | Undecided → Low |
| status: | New → Triaged |
| Changed in swift-storage (Juju Charms Collection): | |
| status: | Triaged → Invalid |
| Changed in charm-swift-storage: | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
I had same problem with swift-proxy charm. I asked dosaboy and
It seemed that there is no function to get deployed vm's cpu count.
so I just removed that element on amulet test
If there is no function like this yet, how about removing this checking from amulet test?