-
Notifications
You must be signed in to change notification settings - Fork 41
Closed
Labels
needs-kindIndicates an issue or PR lacks a `kind/foo` label and requires one.Indicates an issue or PR lacks a `kind/foo` label and requires one.needs-priorityIndicates an issue or PR lacks a `priority/foo` label and requires one.Indicates an issue or PR lacks a `priority/foo` label and requires one.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.
Description
Current Setup:
- OCP 4.17
- mta-operator 7.3.0 - temporarily patched to use
quay.io/jmontleon/tackle2-operator-container:pr437
When we create a tackle with auth required, we get a failure for it:
message: 'The conditional check ''cr | json_query(''resources[].status.conditions[?type==`Ready`].status'') | first | first | bool'' failed. The error was: You need to install "jmespath" prior to running json_query filter'
reason: Failed
status: 'True'
type: Failure
here's the complete YAML of the Tackle:
apiVersion: tackle.konveyor.io/v1alpha1
kind: Tackle
metadata:
creationTimestamp: '2025-06-04T09:35:09Z'
generation: 1
managedFields: …
name: tackle
namespace: mta-poc
resourceVersion: '280936928'
uid: a0d49832-92b9-4759-8747-a4a50e352be1
spec:
feature_auth_required: 'true'
hub_bucket_volume_size: 5Gi
maven_data_volume_size: 5Gi
rwx_supported: 'false'
status:
conditions:
- lastTransitionTime: '2025-06-04T09:35:52Z'
message: ''
reason: ''
status: 'False'
type: Successful
- lastTransitionTime: '2025-06-04T09:39:28Z'
message: Running reconciliation
reason: Running
status: 'False'
type: Running
- ansibleResult:
changed: 0
completion: '2025-06-04T09:39:44.205078+00:00'
failures: 1
ok: 30
skipped: 43
lastTransitionTime: '2025-06-04T09:35:52Z'
message: 'The conditional check ''cr | json_query(''resources[].status.conditions[?type==`Ready`].status'') | first | first | bool'' failed. The error was: You need to install "jmespath" prior to running json_query filter'
reason: Failed
status: 'True'
type: Failure
Is this an issue on our side? Does it have to do with the custom build of the operator? Any idea?
Background: we currently can not use the mta-operator 7.3.0 as it is, because not all containers have resource requirements set. #439 describes this issue, #437 fixes it - and we are using a custom image for the mta-operator based on this PR.
Metadata
Metadata
Assignees
Labels
needs-kindIndicates an issue or PR lacks a `kind/foo` label and requires one.Indicates an issue or PR lacks a `kind/foo` label and requires one.needs-priorityIndicates an issue or PR lacks a `priority/foo` label and requires one.Indicates an issue or PR lacks a `priority/foo` label and requires one.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.
Type
Projects
Status
✅ Done