| 2016-11-03 02:35:12 |
Ryan Beisner |
bug |
|
|
added bug |
| 2016-11-03 02:40:07 |
Ryan Beisner |
description |
Per policies and best practices, the charm should deploy to a non-error state (blocked is ok). However, when deployed without config, config-changed hooks fail.
And when deployed with config but no remote host, the remote ssh commands try to run and fail. We should check that the remote host is up before firing the installation, and block until it is reachable. |
Per policies and best practices, the charm should deploy to a non-error state (blocked is ok). However, when deployed without config, config-changed hooks fail.
And when deployed with config but no remote host, the remote ssh commands try to run and fail. We should check that the remote host is up before firing the installation, and block until it is reachable.
Logs and artifacts:
https://openstack-ci-reports.ubuntu.com/artifacts/test_charm_pipeline/openstack/charm-nova-compute-proxy/393024/2/1119/index.html |
|
| 2016-11-03 02:42:38 |
Ryan Beisner |
description |
Per policies and best practices, the charm should deploy to a non-error state (blocked is ok). However, when deployed without config, config-changed hooks fail.
And when deployed with config but no remote host, the remote ssh commands try to run and fail. We should check that the remote host is up before firing the installation, and block until it is reachable.
Logs and artifacts:
https://openstack-ci-reports.ubuntu.com/artifacts/test_charm_pipeline/openstack/charm-nova-compute-proxy/393024/2/1119/index.html |
Per policies and best practices, the charm should deploy to a non-error state (blocked is ok). However, when deployed without config, the install hook fails.
And when deployed with config but no remote host, the remote ssh commands try to run and fail. We should check that the remote host is up before firing the proxy installation, and block until it is reachable.
Logs and artifacts:
https://openstack-ci-reports.ubuntu.com/artifacts/test_charm_pipeline/openstack/charm-nova-compute-proxy/393024/2/1119/index.html |
|
| 2016-11-03 16:27:35 |
Ryan Beisner |
summary |
charm single fails |
charm single fails (need to use blocked status, wait for config and relations) |
|
| 2016-11-04 02:50:04 |
Vance Morris |
charm-nova-compute-proxy: status |
New |
Confirmed |
|
| 2016-11-07 23:22:01 |
Ryan Beisner |
description |
Per policies and best practices, the charm should deploy to a non-error state (blocked is ok). However, when deployed without config, the install hook fails.
And when deployed with config but no remote host, the remote ssh commands try to run and fail. We should check that the remote host is up before firing the proxy installation, and block until it is reachable.
Logs and artifacts:
https://openstack-ci-reports.ubuntu.com/artifacts/test_charm_pipeline/openstack/charm-nova-compute-proxy/393024/2/1119/index.html |
Per policies and best practices, the charm should deploy to a non-error state (blocked is ok). However, when deployed without config, the install hook fails.
And when deployed with config but no remote host, the remote ssh commands try to run and fail. We should check that the remote host is up before firing the proxy installation, and block until it is reachable.
We should also implement require_relations and block until that is satisfied.
Logs and artifacts:
https://openstack-ci-reports.ubuntu.com/artifacts/test_charm_pipeline/openstack/charm-nova-compute-proxy/393024/2/1119/index.html |
|
| 2016-11-07 23:23:28 |
Ryan Beisner |
description |
Per policies and best practices, the charm should deploy to a non-error state (blocked is ok). However, when deployed without config, the install hook fails.
And when deployed with config but no remote host, the remote ssh commands try to run and fail. We should check that the remote host is up before firing the proxy installation, and block until it is reachable.
We should also implement require_relations and block until that is satisfied.
Logs and artifacts:
https://openstack-ci-reports.ubuntu.com/artifacts/test_charm_pipeline/openstack/charm-nova-compute-proxy/393024/2/1119/index.html |
Per policies and best practices, the charm should deploy to a non-error state (blocked is ok). However, when deployed without config, or before the remote compute host is ready, the install proxy charm hook fails.
We should check that the remote host is up before firing the proxy installation, and block until it is reachable.
We should also implement require_relations and block until that is satisfied.
Logs and artifacts:
https://openstack-ci-reports.ubuntu.com/artifacts/test_charm_pipeline/openstack/charm-nova-compute-proxy/393024/2/1119/index.html |
|
| 2016-11-07 23:24:13 |
Ryan Beisner |
summary |
charm single fails (need to use blocked status, wait for config and relations) |
charm needs to implement required_relations (block until control plane is ready) |
|
| 2016-12-13 14:00:41 |
Alex Kavanagh |
charm-nova-compute-proxy: importance |
Undecided |
Medium |
|
| 2019-04-12 15:02:57 |
Ryan Beisner |
charm-nova-compute-proxy: status |
Confirmed |
Won't Fix |
|
