Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1609050

Summary:

Logging environment file causes error in existing deployment

Product:

Red Hat OpenStack

Reporter:

Christopher Brown <chris.brown>

Component:

rhosp-director

Assignee:

Juan Badia Payno <jbadiapa>

Status:

CLOSED WORKSFORME

QA Contact:

Gurenko Alex <agurenko>

Severity:

medium

Docs Contact:

Priority:

medium

Version:

10.0 (Newton)

CC:

chris.brown, dbecker, jslagle, mburns, morazi, mtenheuv, pkilambi

Target Milestone:

---

Keywords:

Triaged, ZStream

Target Release:

---

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

If docs needed, set a value

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2018-10-01 14:52:20 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
logging environment file	none

Description Christopher Brown 2018-07-26 20:14:41 UTC

Description of problem:

I am including the logging-environment.yaml file in my deployment along with a very basic configuration. When running new deployment or stack update, I get the following error:

2018-07-26 12:30:19Z [Controller]: UPDATE_FAILED  StackValidationFailed: resources.Controller: Property error: Controller.Properties.resource_def: Error in ControllerServiceChain output role_data: u'tag'
2018-07-26 12:30:19Z [overcloud]: UPDATE_FAILED  StackValidationFailed: resources.Controller: Property error: Controller.Properties.resource_def: Error in ControllerServiceChain output role_data: u'tag'

Further updates to the stack fail but crucially, the stack itself seems to be affected as removing the environment file and running another stack update results in the same failure.

Version-Release number of selected component (if applicable):

OSP 10z8

How reproducible:

Always when using this environment file.

Steps to Reproduce:
Run deployment with:

openstack overcloud deploy --templates \
  -r /home/stack/templates/roles_data.yaml \
  -e /usr/share/openstack-tripleo-heat-templates/extraconfig/pre_deploy/rhel-registration/rhel-registration-resource-registry.yaml \
  -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \
  -e /usr/share/openstack-tripleo-heat-templates/environments/network-management.yaml \
  -e /usr/share/openstack-tripleo-heat-templates/environments/neutron-ovs-dpdk.yaml \
  -e /home/stack/templates/inject-trust-anchor.yaml \
  -e /home/stack/templates/logging-environment.yaml \
  -e /usr/share/openstack-tripleo-heat-templates/environments/tls-endpoints-public-dns.yaml \
  -e /home/stack/templates/common.yaml

Observe failure. Re-run update without "-e /home/stack/templates/logging-environment.yaml \". Update still fails.

Comment 1 David Peacock 2018-07-27 00:31:27 UTC

Thank you for this bug report.  I don't see the logging-environment.yaml you mention attached; please would you check this?

Thanks,
David

Comment 2 Christopher Brown 2018-07-27 07:06:52 UTC

Created attachment 1471001 [details]
logging environment file

Comment 3 Christopher Brown 2018-07-27 07:07:45 UTC

(In reply to David Peacock from comment #1)
> Thank you for this bug report.  I don't see the logging-environment.yaml you
> mention attached; please would you check this?

Ok, have attached, as mentioned, its as basic as can be.

Comment 4 Juan Badia Payno 2018-08-09 09:03:29 UTC

Let's try to find out where the problem is without logging into the servers.
Could you run the following commands and upload the overcloud_resource_failed.log?

for failed in $(openstack stack resource list \
        --nested-depth 5 overcloud | grep FAILED |
        grep 'StructuredDeployment ' | cut -d '|' -f3)
    do
    echo "heat deployment-show out put for deployment: $failed" >> overcloud_resource_failed.log
    echo "######################################################" >> overcloud_resource_failed.log
    heat deployment-show $failed >> overcloud_resource_failed.log
    echo "######################################################" >> overcloud_resource_failed.log
    echo "puppet standard error for deployment: $failed" >> overcloud_resource_failed.log
    echo "######################################################" >> overcloud_resource_failed.log
    # the sed part removes color codes from the text
    heat deployment-show $failed |
        jq -r .output_values.deploy_stderr |
        sed -r "s:\x1B\[[0-9;]*[mK]::g" >> overcloud_resource_failed.log
    echo "######################################################" >> overcloud_resource_failed.log
done

BTW, if the problem persists with and without the logging-environment file, IMO the problem should be somewhere else.

Could you attach the common.yaml file?

Comment 5 Christopher Brown 2018-08-09 10:11:05 UTC

Hi Juan,

We have worked around this by automating elsewhere in the templates.

I don't currently have access to an environment where I can test this now but may do in a few days.

Will update if so.

Thanks
Chris

Comment 6 Christopher Brown 2018-09-10 11:30:55 UTC

Hi Juan,

I don't have access to this environment any longer.

The error occurred by including this file so I don't think its anything specific to my environment.

If you cannot replicate feel free to close.

Cheers
Chris

Comment 7 Juan Badia Payno 2018-10-01 14:52:20 UTC

I was not able to replicate the error.