Activity log for bug #1599636

Date Who What changed Old value New value Message
2016-07-06 20:31:18 Ursula Junque bug added bug
2016-07-06 20:31:51 Ursula Junque description Charm version is cs:trusty/keystone-255. With an HA mitaka cloud deployed, when trying to action pause keystone the action fails: $ juju action fetch 783e4ee0-a498-42e3-8448-45ac26f6a847 message: 'Couldn''t pause: Services should be paused but these services running: haproxy, these ports which should be closed, but are open: 5000, 35357, Paused. Use ''resume'' action to resume normal service.' status: failed juju logs for the paused unit don't show anything suspicious: http://pastebin.ubuntu.com/18656279/ juju status for keystone related units: http://pastebin.ubuntu.com/18656492/ Charm version is cs:trusty/keystone-255. With an HA mitaka cloud deployed, when trying to action pause keystone the action fails: $ juju action fetch 783e4ee0-a498-42e3-8448-45ac26f6a847 message: 'Couldn''t pause: Services should be paused but these services running: haproxy, these ports which should be closed, but are open: 5000, 35357, Paused. Use ''resume'' action to resume normal service.' status: failed juju logs for the paused unit don't show anything suspicious: http://pastebin.ubuntu.com/18656279/ juju status for keystone related units: http://pastebin.ubuntu.com/18656492/
2016-07-07 14:34:11 Ursula Junque summary pause/resume failing: haproxy is running and ports are open pause/resume failing on HA deployment: haproxy is running and ports are open
2016-07-07 14:34:11 Ursula Junque description Charm version is cs:trusty/keystone-255. With an HA mitaka cloud deployed, when trying to action pause keystone the action fails: $ juju action fetch 783e4ee0-a498-42e3-8448-45ac26f6a847 message: 'Couldn''t pause: Services should be paused but these services running: haproxy, these ports which should be closed, but are open: 5000, 35357, Paused. Use ''resume'' action to resume normal service.' status: failed juju logs for the paused unit don't show anything suspicious: http://pastebin.ubuntu.com/18656279/ juju status for keystone related units: http://pastebin.ubuntu.com/18656492/ Charm version is cs:trusty/keystone-255. With an HA mitaka cloud deployed, when trying to action pause keystone the action fails: $ juju action fetch 783e4ee0-a498-42e3-8448-45ac26f6a847 message: 'Couldn''t pause: Services should be paused but these services running: haproxy, these ports which should be closed, but are open: 5000, 35357, Paused. Use ''resume'' action to resume normal service.' status: failed I noticed the problem is "juju action pause" tries to stop haproxy service, but once pacemaker/corosync detect haproxy isn't running they restart it, so the service is never really stopped and the action fails. juju logs excerpt for the paused unit: http://pastebin.ubuntu.com/18656279/ juju status for keystone related units: http://pastebin.ubuntu.com/18656492/
2016-07-07 14:46:59 Ursula Junque summary pause/resume failing on HA deployment: haproxy is running and ports are open pause/resume failing on HA deployment: haproxy is running
2016-07-07 19:36:17 Ursula Junque description Charm version is cs:trusty/keystone-255. With an HA mitaka cloud deployed, when trying to action pause keystone the action fails: $ juju action fetch 783e4ee0-a498-42e3-8448-45ac26f6a847 message: 'Couldn''t pause: Services should be paused but these services running: haproxy, these ports which should be closed, but are open: 5000, 35357, Paused. Use ''resume'' action to resume normal service.' status: failed I noticed the problem is "juju action pause" tries to stop haproxy service, but once pacemaker/corosync detect haproxy isn't running they restart it, so the service is never really stopped and the action fails. juju logs excerpt for the paused unit: http://pastebin.ubuntu.com/18656279/ juju status for keystone related units: http://pastebin.ubuntu.com/18656492/ I have an HA mitaka cloud, and am checking the pause/resume actions of its units. When trying to "action pause" the units of the services that use hacluster (e.g. keystone, cinder, neutron-api), the action fails *most of the time* because haproxy is running. "juju action pause" tries to stop haproxy service, but once pacemaker/corosync detect haproxy isn't running they restart it, the service is never really stopped and the action fails. Oddly enough, nova-cloud-controller works every time. Keystone example: $ juju action fetch 783e4ee0-a498-42e3-8448-45ac26f6a847 message: 'Couldn''t pause: Services should be paused but these services running: haproxy, these ports which should be closed, but are open: 5000, 35357, Paused. Use ''resume'' action to resume normal service.' status: failed juju logs excerpt for the paused unit: https://pastebin.canonical.com/160484/ juju status of the whole environment: https://pastebin.canonical.com/160483/ /var/log/syslog excerpt right after juju action pause is issued: https://pastebin.canonical.com/160379/ nova-cloud-controller units consistenty pause successfully. All others sometimes work, but vast majority attempts fail. This could indicate that something incidental is been relied upon (e.g. assuming network is "fast" enough that races aren't an issue).
2016-07-07 19:51:41 Ursula Junque bug task added cinder (Juju Charms Collection)
2016-07-07 19:52:04 Ursula Junque bug task added openstack-dashboard (Juju Charms Collection)
2016-07-07 19:53:23 Ursula Junque description I have an HA mitaka cloud, and am checking the pause/resume actions of its units. When trying to "action pause" the units of the services that use hacluster (e.g. keystone, cinder, neutron-api), the action fails *most of the time* because haproxy is running. "juju action pause" tries to stop haproxy service, but once pacemaker/corosync detect haproxy isn't running they restart it, the service is never really stopped and the action fails. Oddly enough, nova-cloud-controller works every time. Keystone example: $ juju action fetch 783e4ee0-a498-42e3-8448-45ac26f6a847 message: 'Couldn''t pause: Services should be paused but these services running: haproxy, these ports which should be closed, but are open: 5000, 35357, Paused. Use ''resume'' action to resume normal service.' status: failed juju logs excerpt for the paused unit: https://pastebin.canonical.com/160484/ juju status of the whole environment: https://pastebin.canonical.com/160483/ /var/log/syslog excerpt right after juju action pause is issued: https://pastebin.canonical.com/160379/ nova-cloud-controller units consistenty pause successfully. All others sometimes work, but vast majority attempts fail. This could indicate that something incidental is been relied upon (e.g. assuming network is "fast" enough that races aren't an issue). I have an HA mitaka cloud, and am checking the pause/resume actions of its units. When trying to "action pause" the units of the services that use hacluster (e.g. keystone, cinder, neutron-api), the action fails *most of the time* because haproxy is running. "juju action pause" tries to stop haproxy service, but once pacemaker/corosync detect haproxy isn't running they restart it, the service is never really stopped and the action fails. Oddly enough, nova-compute-kvm works every time. Keystone example: $ juju action fetch 783e4ee0-a498-42e3-8448-45ac26f6a847 message: 'Couldn''t pause: Services should be paused but these services running: haproxy, these ports which should be closed, but are open: 5000, 35357, Paused. Use ''resume'' action to resume normal service.' status: failed juju logs excerpt for the paused unit: https://pastebin.canonical.com/160484/ juju status of the whole environment: https://pastebin.canonical.com/160483/ /var/log/syslog excerpt right after juju action pause is issued: https://pastebin.canonical.com/160379/ nova-compute-kvm units consistenty pause successfully. All others sometimes work, but vast majority attempts fail. This could indicate that something incidental is been relied upon (e.g. assuming network is "fast" enough that races aren't an issue).
2016-07-07 20:46:54 Ursula Junque description I have an HA mitaka cloud, and am checking the pause/resume actions of its units. When trying to "action pause" the units of the services that use hacluster (e.g. keystone, cinder, neutron-api), the action fails *most of the time* because haproxy is running. "juju action pause" tries to stop haproxy service, but once pacemaker/corosync detect haproxy isn't running they restart it, the service is never really stopped and the action fails. Oddly enough, nova-compute-kvm works every time. Keystone example: $ juju action fetch 783e4ee0-a498-42e3-8448-45ac26f6a847 message: 'Couldn''t pause: Services should be paused but these services running: haproxy, these ports which should be closed, but are open: 5000, 35357, Paused. Use ''resume'' action to resume normal service.' status: failed juju logs excerpt for the paused unit: https://pastebin.canonical.com/160484/ juju status of the whole environment: https://pastebin.canonical.com/160483/ /var/log/syslog excerpt right after juju action pause is issued: https://pastebin.canonical.com/160379/ nova-compute-kvm units consistenty pause successfully. All others sometimes work, but vast majority attempts fail. This could indicate that something incidental is been relied upon (e.g. assuming network is "fast" enough that races aren't an issue). I have an HA mitaka cloud, and am checking the pause/resume actions of its units. When trying to "action pause" the units of most services that use hacluster (keystone, cinder, neutron-api, ceilometer, nova-cloud-controller, ceph-radosgw and less often openstack-dashboard), the action fails *most of the time* because haproxy is running. "juju action pause" tries to stop haproxy service, but once pacemaker/corosync detects haproxy isn't running service is restarted, service is never really stopped and the action fails. Oddly enough, nova-compute-kvm works every time. Keystone example: $ juju action fetch 783e4ee0-a498-42e3-8448-45ac26f6a847 message: 'Couldn''t pause: Services should be paused but these services running: haproxy, these ports which should be closed, but are open: 5000, 35357, Paused. Use ''resume'' action to resume normal service.' status: failed juju logs excerpt for the paused unit: https://pastebin.canonical.com/160484/ juju status of the whole environment: https://pastebin.canonical.com/160483/ /var/log/syslog excerpt right after juju action pause is issued: https://pastebin.canonical.com/160379/ nova-compute-kvm units consistenty pause successfully. All others sometimes work, but vast majority attempts fail. This could indicate that something incidental is been relied upon (e.g. assuming network is "fast" enough that races aren't an issue).
2016-07-07 20:47:17 Ursula Junque bug task added neutron-api (Juju Charms Collection)
2016-07-07 20:47:43 Ursula Junque bug task added ceilometer (Juju Charms Collection)
2016-07-07 20:48:05 Ursula Junque bug task added ceph-radosgw (Juju Charms Collection)
2016-07-07 20:48:35 Ursula Junque bug task added nova-cloud-controller (Juju Charms Collection)
2016-07-07 20:58:09 Ursula Junque description I have an HA mitaka cloud, and am checking the pause/resume actions of its units. When trying to "action pause" the units of most services that use hacluster (keystone, cinder, neutron-api, ceilometer, nova-cloud-controller, ceph-radosgw and less often openstack-dashboard), the action fails *most of the time* because haproxy is running. "juju action pause" tries to stop haproxy service, but once pacemaker/corosync detects haproxy isn't running service is restarted, service is never really stopped and the action fails. Oddly enough, nova-compute-kvm works every time. Keystone example: $ juju action fetch 783e4ee0-a498-42e3-8448-45ac26f6a847 message: 'Couldn''t pause: Services should be paused but these services running: haproxy, these ports which should be closed, but are open: 5000, 35357, Paused. Use ''resume'' action to resume normal service.' status: failed juju logs excerpt for the paused unit: https://pastebin.canonical.com/160484/ juju status of the whole environment: https://pastebin.canonical.com/160483/ /var/log/syslog excerpt right after juju action pause is issued: https://pastebin.canonical.com/160379/ nova-compute-kvm units consistenty pause successfully. All others sometimes work, but vast majority attempts fail. This could indicate that something incidental is been relied upon (e.g. assuming network is "fast" enough that races aren't an issue). I have an HA mitaka cloud (deployed with autopilot), and am checking the pause/resume actions of its units. When trying to "action pause" the units of most services that use hacluster (keystone, cinder, neutron-api, ceilometer, nova-cloud-controller, ceph-radosgw and less often openstack-dashboard), the action fails *most of the time* because haproxy is running. "juju action pause" tries to stop haproxy service, but once pacemaker/corosync detects haproxy isn't running, the service is restarted. haproxy is never really stopped and the action fails. nova-compute-kvm works every time. Keystone example: $ juju action fetch 783e4ee0-a498-42e3-8448-45ac26f6a847 message: 'Couldn''t pause: Services should be paused but these services running: haproxy, these ports which should be closed, but are open: 5000, 35357, Paused. Use ''resume'' action to resume normal service.' status: failed juju logs excerpt for the paused unit: https://pastebin.canonical.com/160484/ juju status of the whole environment: https://pastebin.canonical.com/160483/ /var/log/syslog excerpt right after juju action pause is issued: https://pastebin.canonical.com/160379/ nova-compute-kvm units consistenty pause successfully. All others sometimes work, but vast majority attempts fail. This could indicate that something incidental is been relied upon (e.g. assuming network is "fast" enough that races aren't an issue). Output of a script that pauses and resumes one unit per service to check the behavior: https://pastebin.canonical.com/160490/. Notice that neutron-api despite failing the action reports the unit as successfully paused shortly after.
2016-07-07 20:58:20 Ursula Junque summary pause/resume failing on HA deployment: haproxy is running pause failing on HA deployment: haproxy is running
2016-07-07 21:26:02 Ursula Junque description I have an HA mitaka cloud (deployed with autopilot), and am checking the pause/resume actions of its units. When trying to "action pause" the units of most services that use hacluster (keystone, cinder, neutron-api, ceilometer, nova-cloud-controller, ceph-radosgw and less often openstack-dashboard), the action fails *most of the time* because haproxy is running. "juju action pause" tries to stop haproxy service, but once pacemaker/corosync detects haproxy isn't running, the service is restarted. haproxy is never really stopped and the action fails. nova-compute-kvm works every time. Keystone example: $ juju action fetch 783e4ee0-a498-42e3-8448-45ac26f6a847 message: 'Couldn''t pause: Services should be paused but these services running: haproxy, these ports which should be closed, but are open: 5000, 35357, Paused. Use ''resume'' action to resume normal service.' status: failed juju logs excerpt for the paused unit: https://pastebin.canonical.com/160484/ juju status of the whole environment: https://pastebin.canonical.com/160483/ /var/log/syslog excerpt right after juju action pause is issued: https://pastebin.canonical.com/160379/ nova-compute-kvm units consistenty pause successfully. All others sometimes work, but vast majority attempts fail. This could indicate that something incidental is been relied upon (e.g. assuming network is "fast" enough that races aren't an issue). Output of a script that pauses and resumes one unit per service to check the behavior: https://pastebin.canonical.com/160490/. Notice that neutron-api despite failing the action reports the unit as successfully paused shortly after. I have an HA mitaka cloud (deployed with autopilot), and am checking the pause/resume actions of its units. When trying to "action pause" the units of most services that use hacluster (keystone, cinder, neutron-api, ceilometer, nova-cloud-controller, ceph-radosgw and less often openstack-dashboard), the action fails *most of the time* because haproxy is running. "juju action pause" tries to stop haproxy service, but once pacemaker/corosync detects haproxy isn't running, the service is restarted. haproxy is never really stopped and the action fails. Keystone example: $ juju action fetch 783e4ee0-a498-42e3-8448-45ac26f6a847 message: 'Couldn''t pause: Services should be paused but these services running: haproxy, these ports which should be closed, but are open: 5000, 35357, Paused. Use ''resume'' action to resume normal service.' status: failed juju logs excerpt for the paused unit: https://pastebin.canonical.com/160484/ juju status of the whole environment: https://pastebin.canonical.com/160483/ /var/log/syslog excerpt right after juju action pause is issued: https://pastebin.canonical.com/160379/ The actions for these services sometimes work, but vast majority attempts fail. This could indicate that something incidental is been relied upon (e.g. assuming network is "fast" enough that races aren't an issue). Output of a script that pauses and resumes one unit per service to check the behavior: https://pastebin.canonical.com/160490/. Notice that neutron-api despite failing the action reports the unit as successfully paused shortly after.
2016-07-07 21:52:39 Ryan Beisner bug added subscriber Ryan Beisner
2016-07-08 08:07:25 James Page ceilometer (Juju Charms Collection): importance Undecided High
2016-07-08 08:07:27 James Page ceph-radosgw (Juju Charms Collection): importance Undecided High
2016-07-08 08:07:40 James Page openstack-dashboard (Juju Charms Collection): importance Undecided High
2016-07-08 08:07:45 James Page keystone (Juju Charms Collection): importance Undecided High
2016-07-08 08:07:49 James Page cinder (Juju Charms Collection): status New Triaged
2016-07-08 08:07:52 James Page keystone (Juju Charms Collection): status New Triaged
2016-07-08 08:08:30 James Page cinder (Juju Charms Collection): importance Undecided High
2016-07-08 08:08:33 James Page neutron-api (Juju Charms Collection): importance Undecided High
2016-07-08 08:08:36 James Page nova-cloud-controller (Juju Charms Collection): importance Undecided High
2016-07-08 08:08:39 James Page neutron-api (Juju Charms Collection): status New Triaged
2016-07-08 08:08:41 James Page nova-cloud-controller (Juju Charms Collection): status New Triaged
2016-07-08 08:08:43 James Page openstack-dashboard (Juju Charms Collection): status New Triaged
2016-07-08 08:08:45 James Page ceph-radosgw (Juju Charms Collection): status New Triaged
2016-07-08 08:08:49 James Page ceilometer (Juju Charms Collection): status New Triaged
2016-07-08 14:10:40 Ursula Junque tags landscape kanban-cross-team landscape
2016-07-08 14:54:46 🤖 Landscape Builder tags kanban-cross-team landscape landscape
2016-07-11 13:28:07 Ursula Junque bug task added glance (Juju Charms Collection)
2016-07-11 13:37:49 James Page glance (Juju Charms Collection): status New Triaged
2016-07-11 13:37:50 James Page glance (Juju Charms Collection): importance Undecided High
2016-07-12 08:31:52 James Page ceilometer (Juju Charms Collection): importance High Low
2016-07-12 08:31:53 James Page ceph-radosgw (Juju Charms Collection): importance High Low
2016-07-12 08:31:55 James Page cinder (Juju Charms Collection): importance High Low
2016-07-12 08:31:57 James Page glance (Juju Charms Collection): importance High Low
2016-07-12 08:31:59 James Page keystone (Juju Charms Collection): importance High Low
2016-07-12 08:32:00 James Page neutron-api (Juju Charms Collection): importance High Low
2016-07-12 08:32:02 James Page nova-cloud-controller (Juju Charms Collection): importance High Low
2016-07-12 08:32:04 James Page openstack-dashboard (Juju Charms Collection): importance High Low
2016-07-12 08:32:08 James Page ceilometer (Juju Charms Collection): milestone 16.07
2016-07-12 08:32:11 James Page cinder (Juju Charms Collection): milestone 16.10
2016-07-12 08:32:14 James Page ceph-radosgw (Juju Charms Collection): milestone 16.07
2016-07-12 08:32:16 James Page ceph-radosgw (Juju Charms Collection): milestone 16.07 16.10
2016-07-12 08:32:33 James Page ceilometer (Juju Charms Collection): milestone 16.07 16.10
2016-07-12 08:32:35 James Page glance (Juju Charms Collection): milestone 16.10
2016-07-12 08:32:37 James Page keystone (Juju Charms Collection): milestone 16.10
2016-07-12 08:32:39 James Page neutron-api (Juju Charms Collection): milestone 16.10
2016-07-12 08:32:40 James Page nova-cloud-controller (Juju Charms Collection): milestone 16.10
2016-07-12 08:32:44 James Page openstack-dashboard (Juju Charms Collection): milestone 16.10
2017-02-23 18:34:58 James Page charm-ceilometer: importance Undecided Low
2017-02-23 18:34:58 James Page charm-ceilometer: status New Triaged
2017-02-23 18:35:01 James Page ceilometer (Juju Charms Collection): status Triaged Invalid
2017-02-23 18:44:19 James Page charm-ceph-radosgw: importance Undecided Low
2017-02-23 18:44:19 James Page charm-ceph-radosgw: status New Triaged
2017-02-23 18:44:20 James Page ceph-radosgw (Juju Charms Collection): status Triaged Invalid
2017-02-23 18:45:54 James Page charm-cinder: importance Undecided Low
2017-02-23 18:45:54 James Page charm-cinder: status New Triaged
2017-02-23 18:45:56 James Page cinder (Juju Charms Collection): status Triaged Invalid
2017-02-23 18:48:00 James Page charm-glance: importance Undecided Low
2017-02-23 18:48:00 James Page charm-glance: status New Triaged
2017-02-23 18:48:02 James Page glance (Juju Charms Collection): status Triaged Invalid
2017-02-23 18:54:21 James Page charm-keystone: importance Undecided Low
2017-02-23 18:54:21 James Page charm-keystone: status New Triaged
2017-02-23 18:54:23 James Page keystone (Juju Charms Collection): status Triaged Invalid
2017-02-23 18:56:38 James Page charm-neutron-api: importance Undecided Low
2017-02-23 18:56:38 James Page charm-neutron-api: status New Triaged
2017-02-23 18:56:39 James Page neutron-api (Juju Charms Collection): status Triaged Invalid
2017-02-23 19:02:55 James Page charm-nova-cloud-controller: importance Undecided Low
2017-02-23 19:02:55 James Page charm-nova-cloud-controller: status New Triaged
2017-02-23 19:02:57 James Page nova-cloud-controller (Juju Charms Collection): status Triaged Invalid
2017-02-23 19:05:35 James Page charm-openstack-dashboard: importance Undecided Low
2017-02-23 19:05:35 James Page charm-openstack-dashboard: status New Triaged
2017-02-23 19:05:36 James Page openstack-dashboard (Juju Charms Collection): status Triaged Invalid
2017-03-20 13:29:20 Sandor Zeestraten bug added subscriber Sandor Zeestraten
2019-04-09 14:58:58 Edward Hope-Morley bug task deleted openstack-dashboard (Juju Charms Collection)
2019-04-09 14:59:05 Edward Hope-Morley bug task deleted nova-cloud-controller (Juju Charms Collection)
2019-04-09 14:59:12 Edward Hope-Morley bug task deleted neutron-api (Juju Charms Collection)
2019-04-09 14:59:40 Edward Hope-Morley bug task deleted keystone (Juju Charms Collection)
2019-04-09 14:59:44 Edward Hope-Morley bug task deleted glance (Juju Charms Collection)
2019-04-09 14:59:49 Edward Hope-Morley bug task deleted cinder (Juju Charms Collection)
2019-04-09 14:59:53 Edward Hope-Morley bug task deleted ceph-radosgw (Juju Charms Collection)
2019-04-09 15:00:03 Edward Hope-Morley bug task deleted ceilometer (Juju Charms Collection)
2019-04-09 15:00:25 Edward Hope-Morley charm-ceilometer: milestone 19.04
2019-04-09 15:00:28 Edward Hope-Morley charm-ceph-radosgw: milestone 19.04
2019-04-09 15:00:31 Edward Hope-Morley charm-cinder: milestone 19.04
2019-04-09 15:00:33 Edward Hope-Morley charm-glance: milestone 19.04
2019-04-09 15:00:36 Edward Hope-Morley charm-keystone: milestone 19.04
2019-04-09 15:00:39 Edward Hope-Morley charm-neutron-api: milestone 19.04
2019-04-09 15:00:41 Edward Hope-Morley charm-nova-cloud-controller: milestone 19.04
2019-04-09 15:00:44 Edward Hope-Morley charm-openstack-dashboard: milestone 19.04
2019-04-09 15:00:56 Edward Hope-Morley tags landscape landscape sts
2019-04-09 15:05:03 Edward Hope-Morley bug task added charm-deployment-guide
2019-04-09 15:05:10 Edward Hope-Morley charm-deployment-guide: importance Undecided High
2019-04-17 22:10:07 David Ames charm-ceilometer: milestone 19.04 19.07
2019-04-17 22:10:11 David Ames charm-ceph-radosgw: milestone 19.04 19.07
2019-04-17 22:10:14 David Ames charm-cinder: milestone 19.04 19.07
2019-04-17 22:10:17 David Ames charm-glance: milestone 19.04 19.07
2019-04-17 22:10:20 David Ames charm-keystone: milestone 19.04 19.07
2019-04-17 22:10:23 David Ames charm-neutron-api: milestone 19.04 19.07
2019-04-17 22:10:26 David Ames charm-nova-cloud-controller: milestone 19.04 19.07
2019-04-17 22:10:30 David Ames charm-openstack-dashboard: milestone 19.04 19.07
2019-08-12 21:32:44 David Ames charm-ceilometer: milestone 19.07 19.10
2019-08-12 21:32:48 David Ames charm-ceph-radosgw: milestone 19.07 19.10
2019-08-12 21:32:52 David Ames charm-cinder: milestone 19.07 19.10
2019-08-12 21:32:57 David Ames charm-glance: milestone 19.07 19.10
2019-08-12 21:33:01 David Ames charm-keystone: milestone 19.07 19.10
2019-08-12 21:33:04 David Ames charm-neutron-api: milestone 19.07 19.10
2019-08-12 21:33:10 David Ames charm-nova-cloud-controller: milestone 19.07 19.10
2019-08-12 21:33:13 David Ames charm-openstack-dashboard: milestone 19.07 19.10
2019-10-24 23:22:56 David Ames charm-ceilometer: milestone 19.10 20.01
2019-10-24 23:23:01 David Ames charm-ceph-radosgw: milestone 19.10 20.01
2019-10-24 23:23:04 David Ames charm-cinder: milestone 19.10 20.01
2019-10-24 23:23:07 David Ames charm-glance: milestone 19.10 20.01
2019-10-24 23:23:10 David Ames charm-keystone: milestone 19.10 20.01
2019-10-24 23:23:14 David Ames charm-neutron-api: milestone 19.10 20.01
2019-10-24 23:23:17 David Ames charm-nova-cloud-controller: milestone 19.10 20.01
2019-10-24 23:23:20 David Ames charm-openstack-dashboard: milestone 19.10 20.01
2019-11-08 20:38:16 Peter Matulis charm-deployment-guide: assignee Peter Matulis (petermatulis)
2019-11-08 20:38:21 Peter Matulis charm-deployment-guide: status New In Progress
2019-11-13 13:45:02 Nobuto Murata bug added subscriber Nobuto Murata
2019-11-18 22:43:26 Peter Matulis charm-deployment-guide: status In Progress Fix Released
2020-03-02 15:41:19 James Page charm-ceilometer: milestone 20.01 20.05
2020-03-02 15:41:21 James Page charm-ceph-radosgw: milestone 20.01 20.05
2020-03-02 15:41:23 James Page charm-cinder: milestone 20.01 20.05
2020-03-02 15:41:25 James Page charm-glance: milestone 20.01 20.05
2020-03-02 15:41:27 James Page charm-keystone: milestone 20.01 20.05
2020-03-02 15:41:29 James Page charm-neutron-api: milestone 20.01 20.05
2020-03-02 15:41:31 James Page charm-nova-cloud-controller: milestone 20.01 20.05
2020-03-02 15:41:33 James Page charm-openstack-dashboard: milestone 20.01 20.05
2020-05-21 20:43:02 David Ames charm-ceilometer: milestone 20.05 20.08
2020-05-21 20:43:05 David Ames charm-ceph-radosgw: milestone 20.05 20.08
2020-05-21 20:43:09 David Ames charm-cinder: milestone 20.05 20.08
2020-05-21 20:43:17 David Ames charm-glance: milestone 20.05 20.08
2020-05-21 20:43:20 David Ames charm-keystone: milestone 20.05 20.08
2020-05-21 20:43:23 David Ames charm-neutron-api: milestone 20.05 20.08
2020-05-21 20:43:25 David Ames charm-nova-cloud-controller: milestone 20.05 20.08
2020-05-21 20:43:28 David Ames charm-openstack-dashboard: milestone 20.05 20.08
2020-08-03 14:03:34 James Page charm-ceilometer: milestone 20.08
2020-08-03 14:03:36 James Page charm-ceph-radosgw: milestone 20.08
2020-08-03 14:03:38 James Page charm-cinder: milestone 20.08
2020-08-03 14:03:40 James Page charm-glance: milestone 20.08
2020-08-03 14:03:41 James Page charm-keystone: milestone 20.08
2020-08-03 14:03:43 James Page charm-neutron-api: milestone 20.08
2020-08-03 14:03:44 James Page charm-nova-cloud-controller: milestone 20.08
2020-08-03 14:03:46 James Page charm-openstack-dashboard: milestone 20.08