github.com/juju/juju/cmd/juju/service unit tests fail if xenial is the LTS

Bug #1568374 reported by Cheryl Jennings
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Reed O'Brien
juju-core
Fix Released
Critical
Reed O'Brien
1.25
Fix Released
Critical
Reed O'Brien

Bug Description

The following tests fail for this pacakge when xenial is the default lts (from distro-info --lts):

FAIL: bundle_test.go:1426: deployRepoCharmStoreSuite.TestDeployBundleAnnotations
FAIL: bundle_test.go:555: deployRepoCharmStoreSuite.TestDeployBundleLocalAndCharmStoreCharms
FAIL: bundle_test.go:498: deployRepoCharmStoreSuite.TestDeployBundleLocalDeployment
FAIL: bundle_test.go:1049: deployRepoCharmStoreSuite.TestDeployBundleMachineAttributes
FAIL: bundle_test.go:952: deployRepoCharmStoreSuite.TestDeployBundleMachinesUnitsPlacement
FAIL: bundle_test.go:1287: deployRepoCharmStoreSuite.TestDeployBundleMassiveUnitColocation
FAIL: bundle_test.go:1167: deployRepoCharmStoreSuite.TestDeployBundleUnitColocationWithUnit
FAIL: bundle_test.go:1237: deployRepoCharmStoreSuite.TestDeployBundleUnitPlacedToMachines
FAIL: deploy_test.go:1082: DeploySuite.TestAddMetricCredentialsDefaultForUnmeteredCharm
FAIL: deploy_test.go:235: DeploySuite.TestCharmBundle
FAIL: deploy_test.go:143: DeploySuite.TestCharmDir
FAIL: deploy_test.go:283: DeploySuite.TestConstraints
FAIL: deploy_test.go:424: DeploySuite.TestForceMachine
FAIL: deploy_test.go:433: DeploySuite.TestForceMachineExistingContainer
FAIL: deploy_test.go:107: DeploySuite.TestNoCharm
FAIL: deploy_test.go:390: DeploySuite.TestNumUnits
FAIL: deploy_test.go:330: DeploySuite.TestStorage
FAIL: expose_test.go:63: ExposeSuite.TestBlockExpose
FAIL: expose_test.go:45: ExposeSuite.TestExpose
FAIL: removeunit_test.go:59: RemoveUnitSuite.TestBlockRemoveUnit
FAIL: removeunit_test.go:48: RemoveUnitSuite.TestRemoveUnit
FAIL: unexpose_test.go:67: UnexposeSuite.TestBlockUnexpose
FAIL: unexpose_test.go:45: UnexposeSuite.TestUnexpose
FAIL: upgradecharm_test.go:83: UpgradeCharmErrorsSuite.TestWithInvalidRepository
FAIL: upgradecharm_test.go:363: UpgradeCharmSuccessSuite.TestCharmPath
FAIL: upgradecharm_test.go:376: UpgradeCharmSuccessSuite.TestCharmPathNoRevUpgrade
FAIL: upgradecharm_test.go:337: UpgradeCharmSuccessSuite.TestSwitch

Tags: tech-debt
Changed in juju-core:
milestone: 2.0.0 → 2.0-rc1
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta5 → 2.0-rc1
Changed in juju-core:
status: Triaged → In Progress
assignee: nobody → Reed O'Brien (reedobrien)
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
tags: added: tech-debt
Revision history for this message
Cheryl Jennings (cherylj) wrote :

Please also evaluate if these failures exist on 1.25.

Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
affects: juju-core → juju
Changed in juju:
milestone: 2.0-beta6 → none
milestone: none → 2.0-beta6
Changed in juju-core:
assignee: nobody → Reed O'Brien (reedobrien)
importance: Undecided → Critical
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.