| 2013-11-26 19:19:49 |
Curtis Hovey |
bug |
|
|
added bug |
| 2013-11-26 19:19:49 |
Curtis Hovey |
attachment added |
|
the all-machines log from the hp-cloud env https://bugs.launchpad.net/bugs/1255242/+attachment/3917690/+files/all-machines-test-release-hp.log.gz |
|
| 2013-11-26 19:22:29 |
Curtis Hovey |
attachment added |
|
CI testrunner log for r2072 https://bugs.launchpad.net/juju-core/+bug/1255242/+attachment/3917691/+files/upgrade-juju-r2092.log |
|
| 2013-11-26 19:22:52 |
Curtis Hovey |
tags |
hp-cloud regression upgrade-juju |
ci hp-cloud regression upgrade-juju |
|
| 2013-12-05 17:46:24 |
Curtis Hovey |
summary |
upgrade-juju on HP cloud broken in devel |
juju 1.17.0 bootstrap on HP fails |
|
| 2013-12-05 17:48:16 |
Curtis Hovey |
summary |
juju 1.17.0 bootstrap on HP fails |
upgrade-juju on HP cloud broken in devel |
|
| 2013-12-09 20:36:18 |
Curtis Hovey |
juju-core: milestone |
1.17.1 |
1.17.0 |
|
| 2013-12-18 17:45:18 |
Curtis Hovey |
summary |
upgrade-juju on HP cloud broken in devel |
upgrade-juju and bootstrap on HP cloud broken in devel |
|
| 2013-12-18 18:03:16 |
Curtis Hovey |
attachment added |
|
HP deployment log lp:juju-core r2158 https://bugs.launchpad.net/juju-core/+bug/1255242/+attachment/3932040/+files/all-machines-test-release-hp.log.gz |
|
| 2013-12-19 16:41:37 |
Curtis Hovey |
tags |
ci hp-cloud regression upgrade-juju |
ci hp-cloud intermittent-failure regression upgrade-juju |
|
| 2013-12-19 16:41:41 |
Curtis Hovey |
juju-core: importance |
Critical |
High |
|
| 2013-12-19 16:42:46 |
Curtis Hovey |
juju-core: milestone |
1.17.0 |
1.17.1 |
|
| 2014-01-23 10:37:34 |
Martin Packman |
juju-core: milestone |
1.17.1 |
1.18.0 |
|
| 2014-02-11 23:46:24 |
Curtis Hovey |
summary |
upgrade-juju and bootstrap on HP cloud broken in devel |
HP cloud requires 4G to do what AWS does in 2G mem |
|
| 2014-02-11 23:57:11 |
Curtis Hovey |
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-provisioner": no state server machines with addresses found
Much latter we see a hook failure
juju-test-release-hp-machine-2:2013-11-26 15:10:05 INFO juju.worker.uniter context.go:263
HOOK subprocess.CalledProcessError: Command '['service', 'mysql', 'start']' returned non-zero exit status 1
The mysql charm did not fail on aws, canonistack, lxc, or azure. Just Hp.
I am attaching the juju and CI log. |
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-provisioner": no state server machines with addresses found
Much latter we see a hook failure
juju-test-release-hp-machine-2:2013-11-26 15:10:05 INFO juju.worker.uniter context.go:263
HOOK subprocess.CalledProcessError: Command '['service', 'mysql', 'start']' returned non-zero exit status 1
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. |
|
| 2014-02-11 23:57:15 |
Curtis Hovey |
juju-core: milestone |
1.18.0 |
|
|
| 2014-02-13 15:48:18 |
Curtis Hovey |
tags |
ci hp-cloud intermittent-failure regression upgrade-juju |
ci hp-cloud intermittent-failure upgrade-juju |
|
| 2014-04-10 14:54:19 |
Curtis Hovey |
bug task added |
|
mysql (Juju Charms Collection) |
|
| 2014-04-10 14:54:28 |
Curtis Hovey |
juju-core: status |
Triaged |
Invalid |
|
| 2017-05-15 14:00:04 |
Curtis Hovey |
removed subscriber Curtis Hovey |
|
|
|
