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

With cronjob enabled, the Chart does not install #31

Closed
sseneca opened this issue Oct 22, 2020 · 2 comments
Closed

With cronjob enabled, the Chart does not install #31

sseneca opened this issue Oct 22, 2020 · 2 comments

Comments

@sseneca
Copy link

sseneca commented Oct 22, 2020

From the values.yaml, "Nexcloud image is used as default but only curl is needed". I chose curlimages/curl, but this doesn't work.

With the following:

    cronjob:
      enabled: true
      image:
        repository: curlimages/curl
        tag: 7.73.0

The nextcloud-cron pods fail to get in the READY state. The logs:

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 503 

The main nextcloud pod waits for these, which eventually times out and the installation fails.

Edit: Never mind, the chart is broken even using the default nextcloud image. Deploy file can be found here.

It looks related to #16. The change broke it for somebody else too:

#16 (comment)

The error message is different (503 vs 400). Total guess: it's running curl and expecting to find the Nextcloud instance up, but Nextcloud won't be up until after the cron pod itself is up.

@sseneca sseneca changed the title Chart doesn't install if curlimages/curl used as cronjob image With cronjob enabled, the Chart does not install Oct 22, 2020
@hyperbolic2346
Copy link
Contributor

Thanks for helping me figure out what was going on here.

@pfuhrmann
Copy link
Contributor

Yes. CronJob will fail initially until nextcloud pod itself is running. This actually makes sense to me, not sure if there is anything to fix here.

Once the pod with nextcloud app is running, cronjobs will execute as expected.

@sseneca sseneca closed this as completed Jan 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants