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

Scheduled Last Day of Week feature in 30+ day months moves scheduled job to First Day of Week #14411

Open
5 of 11 tasks
leelightfoot25 opened this issue Sep 5, 2023 · 0 comments
Labels
community component:ui needs_investigation PRs or issues that need further investigation type:bug

Comments

@leelightfoot25
Copy link

Please confirm the following

  • I agree to follow this project's code of conduct.
  • I have checked the current issues for duplicates.
  • I understand that AWX is open source software provided for free and that I might not receive a timely response.
  • I am NOT reporting a (potential) security vulnerability. (These should be emailed to [email protected] instead.)

Bug Summary

Preface that I looked at closed and opened issues prior to creating this in both AWX and AWX-OPERATOR Github projects. My current release version is AWX release version is 22.1.0 not 23.0.0

To recreate this issue try to create a schedule that uses Last Wednesday or Last Thursday (as we tried at the end of August 2023) It automatically shifts the job when you hit save it will say First Wednesday or First Thursday. This happened on multiple template schedules, and we tried re-creating the template all together and got the same response when you go to add teh schedule and configure it to always use the Last (Wednesday or Thursday) is how it was reproduced. My technician thinks he's only seen this behavior on months that have 31 days. I could not confirm this.

My environment:
I am running this from the awx-operator project from kubernetes platform.

I'm certain the first thing someone is going to suggest is to try it from the most recent version of awx-operator i have a planned release to upgrade to that later this week, but i don't see this issue/bug documented anywhere in open or closed and I did fuzzy regex searches for 'schedule', 'Last DAY', 'First Day' and reviewed all of the results to see if i could see someone else talking about this issue.

AWX version

22.1.0

Select the relevant components

  • UI
  • UI (tech preview)
  • API
  • Docs
  • Collection
  • CLI
  • Other

Installation method

kubernetes

Modifications

no

Ansible version

the operator and image is using Ansible 2.9

Operating system

kubernetes is running on Fedora 38

Web browser

Chrome

Steps to reproduce

To recreate this issue try to create a schedule that uses Last Wednesday or Last Thursday (as we tried at the end of August 2023) It automatically shifts the job when you hit save it will say First Wednesday or First Thursday. This happened on multiple template schedules, and we tried re-creating the template all together and got the same response when you go to add teh schedule and configure it to always use the Last (Wednesday or Thursday) is how it was reproduced. My technician thinks he's only seen this behavior on months that have 31 days. I could not confirm this.

Expected results

When you select Last Thursday of every month it should:

  1. show last Thursday as the schedule in the Frequency Details
  2. the next schedule event should also reflect the last Thursdays of every month. Here it does.
    188f9191-6e2a-428d-969c-49b27fa3da6f

Actual results

I think what's happening is the displayed value in Frequency details just doesn't match what the Schedule is set to and what the occurrences is reporting. And that the job is being scheduled correctly and running at the correct time. But My technician was worried because it was showing that it was going to run at a different day and time then what his approved change was for.

Additional information

No response

@fosterseth fosterseth added needs_investigation PRs or issues that need further investigation and removed needs_triage labels Sep 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community component:ui needs_investigation PRs or issues that need further investigation type:bug
Projects
None yet
Development

No branches or pull requests

2 participants