Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Instances not being stopped correctly
See original GitHub issueI’m seeing some pretty odd behaviour with my EC2 scheduler. My first thought is that it’s because I’m trying to schedule OpsWorks EC2 instances, as the RDS schedule is working fine.
Below are logs showing the desired state is stopped, and that the Scheduler is not stopping the instances.
2018-02-18 - 06:00:23.248 - DEBUG : No running periods at this time found in schedule "instance-schedule-opsworks" for this time, desired state is stopped 2018-02-18 - 06:00:23.248 - DEBUG : Desired state for instance from schedule "instance-schedule-opsworks" is stopped, last desired state was stopped, actual state is running 2018-02-18 - 06:00:23.248 - INFO : Scheduler result {'752691938387': {'started': {}, 'resized': {}, 'stopped': {}}}
Issue Analytics
- State:
- Created 6 years ago
- Comments:13 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hello, I believe I found the issue with instance startup. My EBS volumes are encrypted, I added “kms:CreateGrant” to the instanceSchduler role and now the instances are starting as per the schedule
Fixed in v1.2.0