You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 9, 2024. It is now read-only.
Recently we are noticing a weird error when deploying our serverless functions into OpenWhisk.
We have functions that are on a cron schedule, which was running correctly until ~5 days back. All cron scheduled functions just stopped working. We started troubleshooting the issues and here is what we found.
When doing an sls deploy on our function, they are no longer being registered in the openwhisk/alarmsprovider container when it used to be registered. We do see that a trigger and a rule is created using the wsk cli but they are not triggered after a successful deployment.
Further testing, when we manually create a trigger and rule through the wsk cli, the trigger is fired correctly on schedule.
The text was updated successfully, but these errors were encountered:
Is this an instance of openwhisk you are running yourselves or a hosted service?
There hasn't been a new release of the framework plugin since May 2019, which makes me wonder why it would be an issue with the framework rather than the plaform itself? Do you have any more idea?
Recently we are noticing a weird error when deploying our serverless functions into OpenWhisk.
We have functions that are on a cron schedule, which was running correctly until ~5 days back. All cron scheduled functions just stopped working. We started troubleshooting the issues and here is what we found.
When doing an
sls deploy
on our function, they are no longer being registered in the openwhisk/alarmsprovider container when it used to be registered. We do see that a trigger and a rule is created using the wsk cli but they are not triggered after a successful deployment.Further testing, when we manually create a trigger and rule through the wsk cli, the trigger is fired correctly on schedule.
The text was updated successfully, but these errors were encountered: