Bug 2113948

Summary: Cannot find config file: /etc/puppet/hiera.yaml
Product: Red Hat OpenStack Reporter: bshewale <bshewale>
Component: openstack-tripleo-heat-templatesAssignee: Cédric Jeanneret <cjeanner>
Status: CLOSED CURRENTRELEASE QA Contact: Joe H. Rahme <jhakimra>
Severity: urgent Docs Contact:
Priority: high    
Version: 16.2 (Train)CC: cjeanner, jjoyce, jschluet, jslagle, mburns, mgarciac, pojadhav, ramishra, shrjoshi, tkajinam
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-03 14:54:39 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:

Description bshewale@redhat.com 2022-08-02 11:59:08 UTC
Description of problem: Cannot find config file: /etc/puppet/hiera.yaml


Version-Release number of selected component (if applicable): rhos16.2 on rhel8 common component

Error log:

Cannot find config file: /etc/puppet/hiera.yaml

Actual results: Cannot find config file: /etc/puppet/hiera.yaml


Expected results: Config file should be there.


Additional info:

Affected jobs:

periodic-tripleo-ci-rhel-8-containers-multinode-common-rhos-16.2
periodic-tripleo-ci-rhel-8-scenario001-standalone-common-rhos-16.2
periodic-tripleo-ci-rhel-8-scenario002-standalone-common-rhos-16.2
periodic-tripleo-ci-rhel-8-scenario004-standalone-common-rhos-16.2

Comment 3 Cédric Jeanneret 2022-08-02 12:54:24 UTC
Hello there,

Care to check the denials in /var/log/audit/audit.log? I'm wondering if we're not facing something where selinux prevents the access to the whole directory - it may lead to a "file not found" in some conditions.

Cheers,

C.

Comment 4 Cédric Jeanneret 2022-08-02 13:05:13 UTC
OK, after checking the audit.log and related, there's nothing showing selinux preventing that specific access - though there are some others, related to the PKI, and this sounds weird enough to trigger some more digging.. Wondering if selinux related packages (openstack-selinux, container-selinux) are properly installed....

Would it be possible to get a hand on a broken node? That would help with the investigations.

Comment 7 Cédric Jeanneret 2022-08-03 11:23:53 UTC
Hello there,

Is it better now that we should get a newer, corrected openstack-selinux package?

Cheers,

C.

Comment 10 Cédric Jeanneret 2022-08-03 14:54:39 UTC
currentrelease as there's an actual patch that is included now.