Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[artifactory-oss/jcr/cpp-ce] Artifactory dependency charts fails with jf-event issue when splitServicesToContainers is enabled #1639

Closed
nefelim4ag opened this issue Jun 5, 2022 · 12 comments · Fixed by #1658
Labels
bug Something isn't working waiting-for-public-release

Comments

@nefelim4ag
Copy link

Must be disabled, because working only with enterprise image

artifactory:
  jfconnect: # Broken missing jfconnect in OSS image
    enabled: false

Not working because the missing jf-event in OSS image

artifactory:
  splitServicesToContainers: true
@chukka chukka added the bug Something isn't working label Jun 6, 2022
@chukka
Copy link
Collaborator

chukka commented Jun 6, 2022

@nefelim4ag Yes, This is already fixed internally and will be released in upcoming next minor release of artifactory

@nefelim4ag
Copy link
Author

nefelim4ag commented Jul 21, 2022

107.41.4 - same, missing jf-event with artifactory.splitServicesToContainers: true

/bin/bash: /opt/jfrog/artifactory/app/event/bin/jf-event: No such file or directory

@nefelim4ag nefelim4ag reopened this Jul 21, 2022
@chukka
Copy link
Collaborator

chukka commented Jul 21, 2022

@nefelim4ag can you please share complete logs and reproducible steps ?

@nefelim4ag
Copy link
Author

nefelim4ag commented Jul 21, 2022

artifactory-oss: 107.41.4

artifactory:
  splitServicesToContainers: true # Broken missing jf-events in OSS image
  artifactory:
    persistence:
      size: 100Gi
      storageClassName: "efs"
    resources:
      requests:
        memory: "2Gi"
        cpu: "200m"
    javaOpts:
      corePoolSize: 8
      jmx:
        authenticate: false
        enabled: false
        port: 9010
        ssl: false
      xms: "512m"
      xmx: "2g"
  ingress:
    enabled: true
    hosts:
      - artifactory-dev.example.net
    annotations:
      kubernetes.io/ingress.class: contour
      cert-manager.io/cluster-issuer: zerossl
    tls:
      - secretName: artifactory-tls
        hosts:
          - artifactory-dev.example.net

  jfconnect: # Broken missing jfconnect in OSS image
    enabled: false

  nginx:
    enabled: false

  postgresql:
    enabled: true
    postgresqlPassword: password
    global:
      storageClass: "ebs"
    persistence:
      enabled: true
      size: 16Gi
    resources:
     requests:
       memory: "256Mi"
       cpu: "100m"

And you just have no knob to disable jf-event:
https://github.com/jfrog/charts/blob/master/stable/artifactory/templates/artifactory-statefulset.yaml#L636

@nefelim4ag
Copy link
Author

@chukka image
releases-docker.jfrog.io/jfrog/artifactory-oss:7.41.4

So, no jf-event

bash-4.4$ ls -al /opt/jfrog/artifactory/app/
total 4
drwxrwxrwx 1 artifactory artifactory 202 Jul  6 19:29 .
drwxr-xr-x 1 artifactory artifactory  28 Jul  6 19:30 ..
drwxrwxrwx 4 artifactory artifactory  34 Jul  6 19:29 artifactory
-rwxrwxrwx 1 artifactory artifactory 174 Jul  6 19:17 artifactory.product.version.properties
drwxrwxrwx 3 artifactory artifactory 307 Jul  6 19:30 bin
drwxrwxrwx 2 artifactory artifactory 270 Jul  6 19:28 doc
drwxrwxrwx 3 artifactory artifactory  17 Jul  6 19:28 frontend
drwxrwxrwx 3 artifactory artifactory  17 Jul  6 19:28 integration
drwxrwxrwx 3 artifactory artifactory  17 Jul  6 19:28 metadata
drwxrwxrwx 6 artifactory artifactory  95 Jul  6 19:28 misc
drwxrwxrwx 3 artifactory artifactory  17 Jul  6 19:28 observability
drwxrwxrwx 3 artifactory artifactory  17 Jul  6 19:28 router
drwxrwxrwx 2 artifactory artifactory   6 Jul  6 19:29 run
drwxr-xr-x 8 artifactory artifactory  88 Jul  6 19:29 third-party
bash-4.4$ find /opt/ -name jf-event

@chukka
Copy link
Collaborator

chukka commented Jul 21, 2022

Yes, Thanks for reporting ! we already added support to disable jf-event via values.yaml internally and will be fixed in upcoming release

@nefelim4ag
Copy link
Author

2022-07-21T12:08:22.188Z [jfrou] [WARN ] [24052b61cd9bd0b9] [local_topology.go:274         ] [main                ] - Readiness test failed with the following error: "required node services are missing or unhealthy"
2022-07-21T12:08:26.006Z [jfrou] [WARN ] [03455cef6a7bdcd2] [local_topology_helper.go:65   ] [main                ] - Missing required services: [jfevt]
2022-07-21T12:08:27.192Z [jfrou] [WARN ] [7f2781dc5d2b024b] [local_topology_helper.go:65   ] [main                ] - Missing required services: [jfevt]
2022-07-21T12:08:27.192Z [jfrou] [WARN ] [7f2781dc5d2b024b] [local_topology.go:274         ] [main                ] - Readiness test failed with the following error: "required node services are missing or unhealthy"
2022-07-21T12:08:30.998Z [jfrou] [WARN ] [4f039419bf21907e] [local_topology_helper.go:65   ] [main                ] - Missing required services: [jfevt]

So, I just drop jf-event container from the pod, and to fix this error drop jfevt from jf-router list.

You already released 2 versions, and already said the same (we have fixed and we will release it) about a month ago: #1639 (comment)

So, I will return on next release :)

@chukka
Copy link
Collaborator

chukka commented Jul 22, 2022

@nefelim4ag Sorry for the confusion ! It was partially fixed previously and we missed it . I will reopen until this is properly fixed

@chukka chukka reopened this Jul 22, 2022
@chukka chukka changed the title artifactory-oss: 107.38.10 [artifactory-oss/jcr/cpp-ce] Artifactory dependency charts fails with jf-event issue when splitServicesToContainers is enabled Jul 22, 2022
@chukka
Copy link
Collaborator

chukka commented Jul 26, 2022

Update : Fix for this issue will be available in 7.42.x and above versions

@chukka
Copy link
Collaborator

chukka commented Aug 3, 2022

@nefelim4ag can you try latest oss chart 107.41.7 and share feedback

@nefelim4ag
Copy link
Author

Works, thanks!

@peterkimeli
Copy link

Works for me, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working waiting-for-public-release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants