Activity log for bug #1582272

Date Who What changed Old value New value Message
2016-05-16 15:05:07 Bjoern bug added bug
2016-05-17 16:19:50 Jean-Philippe Evrard openstack-ansible: status New Incomplete
2016-05-17 16:19:54 Jean-Philippe Evrard openstack-ansible: importance Undecided Low
2016-05-17 16:53:27 Bjoern openstack-ansible: status Incomplete New
2016-05-27 16:11:42 Ian Cordasco openstack-ansible: assignee Xin (zxuuzx)
2016-05-31 16:06:40 Jesse Pretorius description During a kilo to Liberty upgrade I noticed inconsistent output of the playbooks to run. My upgrade got stuck at repo_build (unrelated issue here) so I see no reason why it should define the restart point all the way back to setup-hosts play: ran setup-infrastructure.yml -e 'galera_upgrade=true' -e 'rabbitmq_upgrade=true' ******************** failure ******************** The upgrade script has encountered a failure. Failed on task setup-infrastructure.yml -e 'galera_upgrade=true' -e 'rabbitmq_upgrade=true' Re-run the run-upgrade.sh script, or execute the remaining tasks manually: openstack-ansible -e 'pip_install_options=--force-reinstall' openstack-ansible -e 'pip_install_options=--force-reinstall' openstack-ansible -e 'pip_install_options=--force-reinstall' openstack-ansible -e 'pip_install_options=--force-reinstall' openstack-ansible setup-hosts.yml --limit '!galera_all[0]' -e 'pip_install_options=--force-reinstall' openstack-ansible lxc-containers-create.yml --limit galera_all[0] -e 'pip_install_options=--force-reinstall' openstack-ansible -e 'pip_install_options=--force-reinstall' openstack-ansible setup-infrastructure.yml -e 'galera_upgrade=true' -e 'rabbitmq_upgrade=true' -e 'pip_install_options=--force-reinstall' openstack-ansible /opt/rpc-openstack/openstack-ansible/scripts/upgrade-utilities/playbooks/disable-neutron-port-security.yml -e 'pip_install_options=--force-reinstall' openstack-ansible /opt/rpc-openstack/openstack-ansible/scripts/upgrade-utilities/playbooks/memcached-flush.yml -e 'pip_install_options=--force-reinstall' openstack-ansible setup-openstack.yml -e 'pip_install_options=--force-reinstall' openstack-ansible /opt/rpc-openstack/openstack-ansible/scripts/upgrade-utilities/playbooks/cleanup-rabbitmq-vhost.yml -e 'pip_install_options=--force-reinstall' ******************** failure ******************** Also I saw in the logs that the previous, successful ran plays, got marked as OK, but still have been included in the output as plays to run: setup-hosts.yml --limit '!galera_all[0]' has been marked as success lxc-containers-create.yml --limit galera_all[0] has been marked as success Perhaps the -e 'pip_install_options=--force-reinstall' threw off the logic in the run-upgrade script During a kilo to Liberty upgrade I noticed inconsistent output of the playbooks to run. My upgrade got stuck at repo_build (unrelated issue here) and the remaining task list contains lines with no playbooks (note lines 5-8): ran setup-infrastructure.yml -e 'galera_upgrade=true' -e 'rabbitmq_upgrade=true' ******************** failure ******************** The upgrade script has encountered a failure. Failed on task setup-infrastructure.yml -e 'galera_upgrade=true' -e 'rabbitmq_upgrade=true' Re-run the run-upgrade.sh script, or execute the remaining tasks manually: openstack-ansible -e 'pip_install_options=--force-reinstall' openstack-ansible -e 'pip_install_options=--force-reinstall' openstack-ansible -e 'pip_install_options=--force-reinstall' openstack-ansible -e 'pip_install_options=--force-reinstall' openstack-ansible setup-hosts.yml --limit '!galera_all[0]' -e 'pip_install_options=--force-reinstall' openstack-ansible lxc-containers-create.yml --limit galera_all[0] -e 'pip_install_options=--force-reinstall' openstack-ansible -e 'pip_install_options=--force-reinstall' openstack-ansible setup-infrastructure.yml -e 'galera_upgrade=true' -e 'rabbitmq_upgrade=true' -e 'pip_install_options=--force-reinstall' openstack-ansible /opt/rpc-openstack/openstack-ansible/scripts/upgrade-utilities/playbooks/disable-neutron-port-security.yml -e 'pip_install_options=--force-reinstall' openstack-ansible /opt/rpc-openstack/openstack-ansible/scripts/upgrade-utilities/playbooks/memcached-flush.yml -e 'pip_install_options=--force-reinstall' openstack-ansible setup-openstack.yml -e 'pip_install_options=--force-reinstall' openstack-ansible /opt/rpc-openstack/openstack-ansible/scripts/upgrade-utilities/playbooks/cleanup-rabbitmq-vhost.yml -e 'pip_install_options=--force-reinstall' ******************** failure ******************** Also I saw in the logs that the previous, successful ran plays, got marked as OK, but still have been included in the output as plays to run: setup-hosts.yml --limit '!galera_all[0]' has been marked as success lxc-containers-create.yml --limit galera_all[0] has been marked as success Perhaps the -e 'pip_install_options=--force-reinstall' threw off the logic in the run-upgrade script
2016-05-31 16:09:41 Jesse Pretorius summary Restart plays not correctly defined when run-upgrade.sh fails When run-upgrade.sh fails, the list of restart commands are wrong
2016-06-08 20:30:23 Ian Cordasco openstack-ansible: status New Triaged
2016-06-08 20:30:26 Ian Cordasco openstack-ansible: importance Low High
2016-08-03 19:37:39 Ian Cordasco nominated for series openstack-ansible/liberty
2016-08-03 19:37:39 Ian Cordasco bug task added openstack-ansible/liberty
2016-08-03 19:37:39 Ian Cordasco nominated for series openstack-ansible/mitaka
2016-08-03 19:37:39 Ian Cordasco bug task added openstack-ansible/mitaka
2016-08-03 19:37:46 Ian Cordasco openstack-ansible/liberty: status New Triaged
2016-08-03 19:37:49 Ian Cordasco openstack-ansible/mitaka: status New Triaged
2016-08-03 19:37:51 Ian Cordasco openstack-ansible/liberty: importance Undecided Critical
2016-08-03 19:37:53 Ian Cordasco openstack-ansible/mitaka: importance Undecided Critical
2016-08-03 19:38:00 Ian Cordasco openstack-ansible: status Triaged New
2016-08-03 19:38:03 Ian Cordasco openstack-ansible: importance High Undecided
2016-08-03 19:38:23 Ian Cordasco openstack-ansible: status New Triaged
2016-08-03 19:38:25 Ian Cordasco openstack-ansible: importance Undecided High
2016-08-03 19:38:49 Ian Cordasco openstack-ansible/liberty: assignee Xin (zxuuzx)
2016-08-03 19:38:58 Ian Cordasco openstack-ansible/mitaka: assignee Xin (zxuuzx)
2016-08-08 15:45:27 OpenStack Infra openstack-ansible: status Triaged In Progress
2016-08-12 16:36:19 OpenStack Infra openstack-ansible: assignee Xin (zxuuzx) Miguel Alejandro Cantu (miguel-cantu)
2016-08-14 09:47:02 OpenStack Infra openstack-ansible: assignee Miguel Alejandro Cantu (miguel-cantu) Jesse Pretorius (jesse-pretorius)
2016-08-18 21:39:50 OpenStack Infra openstack-ansible: assignee Jesse Pretorius (jesse-pretorius) Kevin Carter (kevin-carter)
2016-08-20 13:09:12 OpenStack Infra openstack-ansible: assignee Kevin Carter (kevin-carter) Jesse Pretorius (jesse-pretorius)
2016-08-21 00:04:26 OpenStack Infra openstack-ansible: status In Progress Fix Released
2016-08-22 13:22:23 OpenStack Infra openstack-ansible/mitaka: status Triaged In Progress
2016-08-22 13:22:23 OpenStack Infra openstack-ansible/mitaka: assignee Xin (zxuuzx) Jean-Philippe Evrard (jean-philippe-evrard)
2016-08-22 17:57:21 OpenStack Infra openstack-ansible/mitaka: status In Progress Fix Committed
2016-08-25 09:49:46 OpenStack Infra openstack-ansible/liberty: status Triaged In Progress
2016-08-25 09:49:46 OpenStack Infra openstack-ansible/liberty: assignee Xin (zxuuzx) git-harry (git-harry)
2016-08-25 14:12:53 OpenStack Infra openstack-ansible/liberty: status In Progress Fix Committed
2023-01-31 16:43:47 Bjoern openstack-ansible/liberty: status Fix Committed Fix Released
2023-01-31 16:43:49 Bjoern openstack-ansible/mitaka: status Fix Committed Fix Released