{"action":"opened","issue":{"url":"https://api.github.com/repos/openshift/openshift-ansible/issues/4270","repository_url":"https://api.github.com/repos/openshift/openshift-ansible","labels_url":"https://api.github.com/repos/openshift/openshift-ansible/issues/4270/labels{/name}","comments_url":"https://api.github.com/repos/openshift/openshift-ansible/issues/4270/comments","events_url":"https://api.github.com/repos/openshift/openshift-ansible/issues/4270/events","html_url":"https://github.com/openshift/openshift-ansible/issues/4270","id":231019193,"number":4270,"title":"Deploying metrics with bad variables doesn't show errors","user":{"login":"alikhajeh1","id":638577,"avatar_url":"https://avatars0.githubusercontent.com/u/638577?v=3","gravatar_id":"","url":"https://api.github.com/users/alikhajeh1","html_url":"https://github.com/alikhajeh1","followers_url":"https://api.github.com/users/alikhajeh1/followers","following_url":"https://api.github.com/users/alikhajeh1/following{/other_user}","gists_url":"https://api.github.com/users/alikhajeh1/gists{/gist_id}","starred_url":"https://api.github.com/users/alikhajeh1/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alikhajeh1/subscriptions","organizations_url":"https://api.github.com/users/alikhajeh1/orgs","repos_url":"https://api.github.com/users/alikhajeh1/repos","events_url":"https://api.github.com/users/alikhajeh1/events{/privacy}","received_events_url":"https://api.github.com/users/alikhajeh1/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-05-24T12:14:16Z","updated_at":"2017-05-24T12:14:16Z","closed_at":null,"body":"#### Description\r\n\r\nWhen installing metrics using [this](https://docs.openshift.org/latest/install_config/cluster_metrics.html#deploying-the-metrics-components), if there are errors in creating any of the templates (e.g. heapster), they are not shown. We had to use `oc create -f` on the tmp yamls that the playbook creates to debug issues.\r\n\r\n\r\n##### Version\r\n\r\nPlease put the following version information in the code block\r\nindicated below.\r\n\r\n```\r\nansible 2.2.0.0\r\n  config file =\r\n  configured module search path = Default w/o overrides\r\n\r\n# git describe\r\nopenshift-ansible-3.5.71-1\r\n```\r\n\r\n##### Steps To Reproduce\r\n1. Run the following command, which has got bad variables (the limit is lower than the request):\r\n```ansible-playbook <OPENSHIFT_ANSIBLE_DIR>/byo/openshift-cluster/openshift-metrics.yml \\\r\n   -e openshift_metrics_install_metrics=True \\\r\n   -e openshift_metrics_hawkular_hostname=hawkular-metrics.example.com \\\r\n   -e openshift_metrics_cassandra_storage_type=pv \\\r\n   -e openshift_metrics_heapster_requests_memory=300Mi \\\r\n   -e openshift_metrics_heapster_limits_memory=200Mi\r\n```\r\n\r\n\r\n##### Expected Results\r\nIt would be good if the above playbook failed with the error message from Origin, e.g.:\r\n```\r\nThe ReplicationController \"heapster\" is invalid: spec.template.spec.containers[0].resources.limits: Invalid value: \"200Mi\": must be greater than or equal to memory request\r\n```\r\n\r\n##### Observed Results\r\nThe playbook completes and when `oc get pods` or `oc get rc` is run, the failed objects are not there, which might make the user think that the playbook didn't try to create them.\r\n\r\n\r\n##### Additional Information\r\n```\r\nCentOS Linux release 7.3.1611 (Core)\r\n```"}}
{"actor":{"display_login":"alikhajeh1"}}