)]}'
{"grenade.sh":[{"author":{"_account_id":14525,"name":"Vasyl Saienko","email":"vsaienko@mirantis.com","username":"vsaienko"},"change_message_id":"a3feff3b7488bfcba4a42668935c41e44633d6b3","unresolved":false,"context_lines":[{"line_number":306,"context_line":"    done"},{"line_number":307,"context_line":""},{"line_number":308,"context_line":"    # Upgrade Tempest"},{"line_number":309,"context_line":"    if [[ \"$ENABLE_TEMPEST\" \u003d\u003d \"True\" \u0026\u0026 is_service_enabled tempest ]]; then"},{"line_number":310,"context_line":"        echo_summary \"Running upgrade-tempest\""},{"line_number":311,"context_line":"        $GRENADE_DIR/upgrade-tempest || die $LINENO \"Failure in upgrade-tempest\""},{"line_number":312,"context_line":"        stop $STOP upgrade-tempest 290"}],"source_content_type":"text/x-sh","patch_set":2,"id":"1a6eadb0_4b2cee98","line":309,"updated":"2016-12-16 13:14:24.000000000","message":"if tempest is enabled or not is specified by ENABLE_TEMPEST. Why we need to have a new check for it? This patch try to solve configuration problem as for me.","commit_id":"3d046efa2d4e45a8dba65b83f0894d4de1d6337a"},{"author":{"_account_id":8851,"name":"Valeriy Ponomaryov","email":"kiparis.kh@gmail.com","username":"vponomaryov"},"change_message_id":"fa46d36bce82e78aa99f37983a500b27147b0fd0","unresolved":false,"context_lines":[{"line_number":306,"context_line":"    done"},{"line_number":307,"context_line":""},{"line_number":308,"context_line":"    # Upgrade Tempest"},{"line_number":309,"context_line":"    if [[ \"$ENABLE_TEMPEST\" \u003d\u003d \"True\" \u0026\u0026 is_service_enabled tempest ]]; then"},{"line_number":310,"context_line":"        echo_summary \"Running upgrade-tempest\""},{"line_number":311,"context_line":"        $GRENADE_DIR/upgrade-tempest || die $LINENO \"Failure in upgrade-tempest\""},{"line_number":312,"context_line":"        stop $STOP upgrade-tempest 290"}],"source_content_type":"text/x-sh","patch_set":2,"id":"1a6eadb0_ab9902c6","line":309,"in_reply_to":"1a6eadb0_4b2cee98","updated":"2016-12-16 13:17:02.000000000","message":"Actually, dependency on redundant env var is a bug, from my point of view. Only presence of service should matter. And, I keep this env var only because of backwards compatibility.","commit_id":"3d046efa2d4e45a8dba65b83f0894d4de1d6337a"},{"author":{"_account_id":8851,"name":"Valeriy Ponomaryov","email":"kiparis.kh@gmail.com","username":"vponomaryov"},"change_message_id":"73e03053aa2d3b0cd247620c78b7fa2ba5f9eef2","unresolved":false,"context_lines":[{"line_number":306,"context_line":"    done"},{"line_number":307,"context_line":""},{"line_number":308,"context_line":"    # Upgrade Tempest"},{"line_number":309,"context_line":"    if [[ \"$ENABLE_TEMPEST\" \u003d\u003d \"True\" \u0026\u0026 is_service_enabled tempest ]]; then"},{"line_number":310,"context_line":"        echo_summary \"Running upgrade-tempest\""},{"line_number":311,"context_line":"        $GRENADE_DIR/upgrade-tempest || die $LINENO \"Failure in upgrade-tempest\""},{"line_number":312,"context_line":"        stop $STOP upgrade-tempest 290"}],"source_content_type":"text/x-sh","patch_set":2,"id":"1a6eadb0_ebe69a42","line":309,"in_reply_to":"1a6eadb0_ab9902c6","updated":"2016-12-16 13:17:40.000000000","message":"In other words, configuration is exactly correct. It disabled service explicitly.","commit_id":"3d046efa2d4e45a8dba65b83f0894d4de1d6337a"},{"author":{"_account_id":14525,"name":"Vasyl Saienko","email":"vsaienko@mirantis.com","username":"vsaienko"},"change_message_id":"68862367d70f656979cac6bf77e6c028329e04dd","unresolved":false,"context_lines":[{"line_number":306,"context_line":"    done"},{"line_number":307,"context_line":""},{"line_number":308,"context_line":"    # Upgrade Tempest"},{"line_number":309,"context_line":"    if [[ \"$ENABLE_TEMPEST\" \u003d\u003d \"True\" \u0026\u0026 is_service_enabled tempest ]]; then"},{"line_number":310,"context_line":"        echo_summary \"Running upgrade-tempest\""},{"line_number":311,"context_line":"        $GRENADE_DIR/upgrade-tempest || die $LINENO \"Failure in upgrade-tempest\""},{"line_number":312,"context_line":"        stop $STOP upgrade-tempest 290"}],"source_content_type":"text/x-sh","patch_set":2,"id":"1a6eadb0_cb70fe74","line":309,"in_reply_to":"1a6eadb0_ebe69a42","updated":"2016-12-16 13:19:03.000000000","message":"It fixes case when job is misconfigured, which should be done in the job itself.","commit_id":"3d046efa2d4e45a8dba65b83f0894d4de1d6337a"}],"upgrade-tempest":[{"author":{"_account_id":14525,"name":"Vasyl Saienko","email":"vsaienko@mirantis.com","username":"vsaienko"},"change_message_id":"6ddbc9839006efa16bea50facab1e81ad230d38c","unresolved":false,"context_lines":[{"line_number":80,"context_line":""},{"line_number":81,"context_line":"install_tempest_plugins"},{"line_number":82,"context_line":"# Use the same config to target smoke tests if exists else create it."},{"line_number":83,"context_line":"tempest_conf_file\u003d$BASE_RELEASE_DIR/tempest/etc/tempest.conf"},{"line_number":84,"context_line":"if [[ -e $tempest_conf_file ]]; then"},{"line_number":85,"context_line":"    cp $tempest_conf_file $TARGET_RELEASE_DIR/tempest/etc/tempest.conf"},{"line_number":86,"context_line":"else"}],"source_content_type":"application/octet-stream","patch_set":1,"id":"1a6eadb0_31180ed3","line":83,"updated":"2016-12-16 09:48:54.000000000","message":"This may happen when tempest is not installed on base release, but is enabled in grenade. According to the logs of manilla grenade job, you heat this situation.\n\nIt looks like misconfiguration of the job because once we called upgrade-tempest, we assume it was installed on base release.\n\n[0] http://logs.openstack.org/65/411065/2/check/gate-grenade-dsvm-manila-ubuntu-xenial/5e9b726/logs/grenade.sh.txt.gz#_2016-12-16_00_47_27_506","commit_id":"380d4d2a425cc3f7e70d276668bf03b48d9e5370"}]}