Skip to content

Two periods defined in schedule, only one period is working #184

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

Closed
prandelicious opened this issue Jul 16, 2020 · 3 comments
Closed

Two periods defined in schedule, only one period is working #184

prandelicious opened this issue Jul 16, 2020 · 3 comments
Labels

Comments

@prandelicious
Copy link

I have the following periods defined:

{
   "Periods": [
      {
         "Begintime": "10:00",
         "Description": "period-1",
         "Endtime": "23:59",
         "Name": "period1",
         "Type": "period"
      }
   ]
}

{
   "Periods": [
      {
         "Begintime": "00:00",
         "Description": "period-2",
         "Endtime": "03:00",
         "Name": "period2",
         "Type": "period"
      }
   ]
}

and the schedule:

{
   "Schedules": [
      {
         "UseMaintenanceWindow": false,
         "StopNewInstances": true,
         "UseMetrics": false,
         "Timezone": "Asia/Manila",
         "Hibernate": false,
         "Enforced": false,
         "RetainRunning": false,
         "Description": "Test schedule, delete after use",
         "Periods": [
            "period1",
            "period2"
         ],
         "Name": "testing",
         "Type": "schedule"
      }
   ]
}

but when I simulate the usage, it gives me this:

{
   "Schedule": "testing",
   "Usage": {
      "2020-07-16": {
         "RunningPeriods": {
            "Period1": {
               "Begin": "07/16/20 03:00:00",
               "End": "07/16/20 23:59:00",
               "BillingHours": 21,
               "BillingSeconds": 75540
            }
         },
         "BillingSeconds": 75540,
         "BillingHours": 21
      },
      "2020-07-17": {
         "RunningPeriods": {
            "Period1": {
               "Begin": "07/17/20 03:00:00",
               "End": "07/17/20 23:59:00",
               "BillingHours": 21,
               "BillingSeconds": 75540
            }
         },
         "BillingSeconds": 75540,
         "BillingHours": 21
      },
      "2020-07-18": {
         "RunningPeriods": {
            "Period1": {
               "Begin": "07/18/20 03:00:00",
               "End": "07/18/20 23:59:00",
               "BillingHours": 21,
               "BillingSeconds": 75540
            }
         },
         "BillingSeconds": 75540,
         "BillingHours": 21
      },
      "2020-07-19": {
         "RunningPeriods": {
            "Period1": {
               "Begin": "07/19/20 03:00:00",
               "End": "07/19/20 23:59:00",
               "BillingHours": 21,
               "BillingSeconds": 75540
            }
         },
         "BillingSeconds": 75540,
         "BillingHours": 21
      },
      "2020-07-20": {
         "RunningPeriods": {
            "Period1": {
               "Begin": "07/20/20 03:00:00",
               "End": "07/20/20 23:59:00",
               "BillingHours": 21,
               "BillingSeconds": 75540
            }
         },
         "BillingSeconds": 75540,
         "BillingHours": 21
      }
   }
}

Only Period1 is recognized.

@praveenis
Copy link

Hi @prandelicious , I apologize for this issue. Can you please confirm whether actual scheduling of instance is working as expected. Also I will add this to our future release backlog as a bug fix for 'scheduler-cli describe-schedule-usage' command.

Thanks,
Praveen

@maykays maykays added the bug label Aug 21, 2020
@alex1969-prog
Copy link

when scheduling these adjacent periods are merged to avoid a stop in between the two periods

@rakshb
Copy link

rakshb commented Oct 2, 2023

We have added this to the backlog and it will be prioritized for a future release.

@rakshb rakshb closed this as not planned Won't fix, can't repro, duplicate, stale Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants