Bug 1543045 - OSP13 | Overcloud deployment fails when trying to deploy with sensu.
Summary: OSP13 | Overcloud deployment fails when trying to deploy with sensu.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: sensu
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: beta
: 13.0 (Queens)
Assignee: Martin Magr
QA Contact: Leonid Natapov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-07 15:48 UTC by Leonid Natapov
Modified: 2023-02-22 23:02 UTC (History)
10 users (show)

Fixed In Version: sensu-1.1.3-2.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-27 13:08:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:2084 0 None None None 2018-06-27 13:10:40 UTC

Description Leonid Natapov 2018-02-07 15:48:20 UTC
I am trying to deploy overcloud with the opstools (sensu,collectd,fluentd).

The deployment fails (tested few times) with the following error:

-----

    2018-02-07 15:09:20Z [overcloud.AllNodesDeploySteps.ComputeDeployment_Step1]: CREATE_FAILED  Resource CREATE failed: Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2
    2018-02-07 15:09:21Z [overcloud.AllNodesDeploySteps.ComputeDeployment_Step1]: CREATE_FAILED  Error: resources.ComputeDeployment_Step1.resources[0]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 2
    2018-02-07 15:09:21Z [overcloud.AllNodesDeploySteps]: CREATE_FAILED  Resource CREATE failed: Error: resources.ComputeDeployment_Step1.resources[0]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 2
    2018-02-07 15:09:21Z [overcloud.AllNodesDeploySteps]: CREATE_FAILED  Error: resources.AllNodesDeploySteps.resources.ComputeDeployment_Step1.resources[0]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 2
    2018-02-07 15:09:21Z [overcloud]: CREATE_FAILED  Resource CREATE failed: Error: resources.AllNodesDeploySteps.resources.ComputeDeployment_Step1.resources[0]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 2
     
     Stack overcloud CREATE_FAILED
     
    overcloud.AllNodesDeploySteps.ComputeDeployment_Step1.0:
      resource_type: OS::Heat::StructuredDeployment
      physical_resource_id: f6ef996d-4d90-4a0f-84d5-da916d114944
      status: CREATE_FAILED
      status_reason: |
        Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 2
      deploy_stdout: |
        ...
                "2018-02-07 15:09:18,269 INFO: 18386 -- Removing container: docker-puppet-nova_libvirt",
                "2018-02-07 15:09:18,295 INFO: 18386 -- Finished processing puppet configs for nova_libvirt",
                "2018-02-07 15:09:18,296 ERROR: 18384 -- ERROR configuring sensu"
            ]
        }
            to retry, use: --limit @/var/lib/heat-config/heat-config-ansible/522f3b65-3262-45f7-b313-3f12fb153414_playbook.retry
     
        PLAY RECAP *********************************************************************
        localhost                  : ok=6    changed=2    unreachable=0    failed=1
     
        (truncated, view all with --long)
      deploy_stderr: |
     
    Heat Stack create failed.
    Heat Stack create failed.


Submit a correction or amendment below (click here to make a fresh posting)

Comment 1 Martin Magr 2018-02-07 16:11:59 UTC
This is a packaging issue, when there was accidentally removed sensu-common requirement for sensu package.

Comment 9 Leonid Natapov 2018-03-07 08:10:21 UTC
Availability Monitoring can be installed. Used osp13 puddle from 2018-03-02.2

Comment 11 errata-xmlrpc 2018-06-27 13:08:58 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:2084


Note You need to log in before you can comment on or make changes to this bug.