Skip to content
Snippets Groups Projects
  1. Jan 17, 2018
  2. Jan 16, 2018
  3. Jan 12, 2018
  4. Jan 11, 2018
    • Doug Szumski's avatar
      Local connection to remote Grafana can fail · 28546710
      Doug Szumski authored
      Following deployment of Grafana, a check is made to ensure that the
      login page is accessible. If the Grafana container has been deployed
      to a remote host, but is not directly accessible over the deployment
      network then the check will fail because the task is set to run with
      connection: local. For example, if Ansible is using a different
      network to the network on which grafana is exposed to connect to the
      remote host then the task may fail. A similar problem exists for the
      remaining two tasks in the post_config file.
      
      Further to this, if Grafana is not accessible, the ansible uri
      module does not return a status field, so no retry attempts are made
      and the task fails with an obscure message:
      
      TASK [grafana : Wait for grafana application ready] *****************
      fatal: [some_remote_node]: FAILED! => {"failed": true, "msg": "The
      conditional check 'result.status == 200' failed. The error was: error
      while evaluating conditional (result.status == 200): 'dict object' has
      no attribute 'status'"}
      
      $ ansible --version
      ansible 2.3.2.0
        config file = /etc/ansible/ansible.cfg
        configured module search path = Default w/o overrides
        python version = 2.7.5 (default, Aug 4 2017, 00:39:18) [GCC 4.8.5 20150623
      (Red Hat 4.8.5-16)]
      
      Change-Id: I77e2129b4a1c5f2f0802fb92eb03395ff72cf5f3
      Closes-Bug: #1742501
      28546710
    • Zuul's avatar
    • Zuul's avatar
      Merge "Enable vitrage dashboard" · 5fe4f199
      Zuul authored
      5fe4f199
    • ZhongShengping's avatar
      Use WSGIApplicationGroup %{GLOBAL} in mod_wsgi configuration · a3f8c987
      ZhongShengping authored
      Change-Id: I419cd02aeb899d93bba5f330d7e4535afd8c0ed8
      Closes-bug: #1708655
      a3f8c987
  5. Jan 10, 2018
  6. Jan 09, 2018
  7. Jan 08, 2018
  8. Jan 05, 2018
  9. Jan 04, 2018
  10. Jan 03, 2018
Loading