HP cloud requires 4G to do what AWS does in 2G mem
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Invalid
|
High
|
Unassigned | ||
mysql (Juju Charms Collection) |
New
|
Undecided
|
Unassigned |
Bug Description
I am sorry for this late bug report. CI consistently shows that upgrade-juju consistently fails on hp-cloud. Revno 2072 appears to be the culprit. Revno 2071 was the last pass, and we verified 2071 was good in two repeats runs of CI. Revno 2072 always fails and fails the same way...the mysql charm has a hook error.
The specific test that fails does this: A 1.16.3 env is bootstrapped on hp cloud. Wordpress + mysql is deployed and verified to be up. The test workspace installed the juju-core 1.17.0. package created from revno 2072. The new tools and metadata were published to all the clouds uder the testing/ prefix. Next juju-upgrade was called on HP cloud and we know 1.17.0 was found.
We see this error after the second effort to get the tools
ERROR juju runner.go:220 worker: exited "environ-
Much latter we see a hook failure
juju-
HOOK subprocess.
The mysql charm did not fail on aws, canonistack, lxc, or azure. Just Hp.
I am attaching the juju and CI log.
UPDATE
CI now deploys mysql on mem=4G to run the same tests that lxc, aws, azure, and canonistack do with 2G. I have verified that Juju can be deployed in 512m on canonistack, which it could not it August. I believe this is a HP issues, not a Juju issue.
Changed in juju-core: | |
milestone: | 1.17.1 → 1.17.0 |
summary: |
- upgrade-juju on HP cloud broken in devel + upgrade-juju and bootstrap on HP cloud broken in devel |
Changed in juju-core: | |
milestone: | 1.17.1 → 1.18.0 |
summary: |
- upgrade-juju and bootstrap on HP cloud broken in devel + HP cloud requires 4G to do what AWS does in 2G mem |
description: | updated |
Changed in juju-core: | |
milestone: | 1.18.0 → none |
This is the test runner log. It captures the all-machine-log when it believes there is a error.