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 on 2015-04-07
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack swift-storage charm
Low
Ryan Beisner
swift-storage (Juju Charms Collection)
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.conductor.14-basic-precise-icehouse DEBUG : account server config error: section [DEFAULT] workers:2 != expected workers:1

When run on a single-core host, the amulet test passes with the hard-coded "1" expectation.

Ryan Beisner (1chb1n) on 2015-04-07
description: updated
Seyeong Kim (seyeongkim) wrote :

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?

Ryan Beisner (1chb1n) on 2015-07-29
Changed in swift-storage (Juju Charms Collection):
assignee: nobody → Ryan Beisner (1chb1n)
status: New → Confirmed
Ryan Beisner (1chb1n) on 2017-01-05
Changed in swift-storage (Juju Charms Collection):
status: Confirmed → New
James Page (james-page) on 2017-01-05
Changed in swift-storage (Juju Charms Collection):
status: New → Triaged
importance: Undecided → Low
James Page (james-page) on 2017-02-23
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
Ryan Beisner (1chb1n) on 2017-09-12
Changed in charm-swift-storage:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers