Stuck on an issue?

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.

Period not parsed correctly "...is an unknown value" "schedule name is unknown"

See original GitHub issue

Hi - I am having an issue where the period config doesn’t be seem to be read properly. The schedule and period is as below

      {
         "RetainRunning": false,
         "Enforced": true,
         "Hibernate": false,
         "Description": "Day to day office hours of eem including holidays",
         "ConfiguredInStack": "arn:aws:cloudformation:...stack/....",
         "StopNewInstances": true,
         "Periods": [
            "eem-office-hours-incl-holidays-21-period-0011",
            "eem-office-hours-incl-holidays-21-period-0001",
            "eem-office-hours-incl-holidays-21-period-0003",
            "eem-office-hours-incl-holidays-21-period-0002",
            "eem-office-hours-incl-holidays-21-period-0009",
            "eem-office-hours-incl-holidays-21-period-0012",
            "eem-office-hours-incl-holidays-21-period-0004",
            "eem-office-hours-incl-holidays-21-period-0008",
            "eem-office-hours-incl-holidays-21-period-0005",
            "eem-office-hours-incl-holidays-21-period-0010",
            "eem-office-hours-incl-holidays-21-period-0006",
            "eem-office-hours-incl-holidays-21-period-0007"
         ],
         "Timezone": "Europe/Berlin",
         "Type": "schedule",
         "Name": "eem-office-hours-incl-holidays-21"
      }

{
         "Description": "July, Schedule eem-office-hours-incl-holidays-21 period 7, do not delete or update manually",
         "Monthdays": [
            "1-31"
         ],
         "Months": [
            "7"
         ],
         "Weekdays": [
            "mon-fri"
         ],
         "Begintime": "07:15",
         "Endtime": "18:30",
         "Type": "period",
         "Name": "eem-office-hours-incl-holidays-21-period-0007"
      }

And in CloudWatchEventHandler cloudwatch logs I see this ERROR : "1-31" is an unknown value

In my rds cloudwatch log I also see WARNING : Skipping instance RDS:.... in region eu-central-1 for account ....., schedule name "eem-office-hours-incl-holidays-21" is unknown

Do you know what might be wrong here?

Issue Analytics

State:
Created 3 years ago
Comments:9

Top GitHub Comments

2reactions

Nico-DBcommented, Feb 5, 2021

@e-power : Hi, we are facing some kind of a similar issue. When defining MonthDays which exceeds 27, you are not able to define it as a range. For example the following does not work:

---
AWSTemplateFormatVersion: '2010-09-09'
Parameters:
  ServiceTokenSchedule:
    Description: Token
    Type: String
Resources:
  FeoAUUTC:
    Type: Custom::ServiceInstanceSchedule
    Properties:
      Description: FeoAUUTC
      ServiceToken: !Ref ServiceTokenSchedule
      Enforced: 'True'
      Timezone: Europe/Berlin
      Periods:
      - Description: Feo AU Up April
        Months: apr
        MonthDays: 6-30

This does work:

---
AWSTemplateFormatVersion: '2010-09-09'
Parameters:
  ServiceTokenSchedule:
    Description: Token
    Type: String
Resources:
  FeoAUUTC:
    Type: Custom::ServiceInstanceSchedule
    Properties:
      Description: FeoAUUTC
      ServiceToken: !Ref ServiceTokenSchedule
      Enforced: 'True'
      Timezone: Europe/Berlin
      Periods:
      - Description: Feo AU Up April
        Months: apr
        MonthDays: 6-27,28,29,30

I know that this is a bug since a long time. What´s new for me is that in the passed the Cloudformation-Stack failed to create and told me that 30 is an unknown value. Which it does not anymore. Is it possible to either fix this issue or hand over the error back to cloudformation again?

0reactions

praveeniscommented, Feb 23, 2021

Hi @e-power ,

we will update the documentation in the upcoming release.

Thanks, Praveen