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

Bug 2069066

Summary: policygentemplates-pre job stuck at INFO [pre-sync-entrypoint] Waiting to acquire sync lock
Product: OpenShift Container Platform Reporter: Marius Cornea <mcornea>
Component: Telco EdgeAssignee: Ian Miller <imiller>
Telco Edge sub component: ZTP QA Contact: yliu1
Status: CLOSED DUPLICATE Docs Contact:
Severity: urgent    
Priority: unspecified    
Version: 4.9   
Target Milestone: ---   
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: 2022-03-28 08:42:52 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 Marius Cornea 2022-03-28 08:07:09 UTC
Description of problem:

policygentemplates-pre job does not complete and the pod is logging:

ztp-hooks.presync Mon, 28 Mar 2022 07:55:57 +0000 INFO [pre-sync-entrypoint] Waiting to acquire sync lock
ztp-hooks.presync Mon, 28 Mar 2022 07:56:57 +0000 INFO [pre-sync-entrypoint] Waiting to acquire sync lock


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

OCP 4.9.26
openshift-gitops-operator.v1.4.5
registry-proxy.engineering.redhat.com/rh-osbs/openshift4-ztp-site-generate:v4.9.0-48

How reproducible:
100%

Steps to Reproduce:
1. Deploy hub cluster with OCP 4.9.26  
2. Install ACM and OpenShift GitOps operators
3. Deploy SNO node by using the Telco ZTP process

Actual results:

policygentemplates-pre job never completes and the pod is stuck at:
[pre-sync-entrypoint] Waiting to acquire sync lock

Expected results:

policygentemplates-pre job completes and the policies are successfully created by the policies app.

Additional info:

Comment 2 Marius Cornea 2022-03-28 08:42:52 UTC

*** This bug has been marked as a duplicate of bug 2065713 ***