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

validate_env.py sends too frequent notifications, misses failure reason #232

Open
sadsfae opened this Issue Apr 15, 2019 · 0 comments

Comments

Projects
None yet
1 participant
@sadsfae
Copy link
Member

commented Apr 15, 2019

Some things that need to be fixed with /opt/quads/quads/tools/validate_env.py

  1. it should NOT send a validation failure message every time it runs, it should ideally be sent once or every 3-4 hours.
  2. It should contain the validation failure reason.

In 1.0 we utilized the /opt/quads/data/.failreport* file structure to capture and report these reasons and initially only sent out one failed validation type notification with the reason to the operator team or admin_cc.

Example:

A post allocation test has failed for:

   cloud: cloud07
   owner: jharriga
   ticket: 488919

The release of the environment is contingent on the success
of the validation scripts.  Before users are notified, make
sure to address the environment and ensure all validation steps
succeed to ensure a timely release to the end user.

@sadsfae sadsfae added this to the 1.1.0 milestone Apr 15, 2019

@sadsfae sadsfae changed the title quads/quads/tools/notify.py sends too frequent notifications, misses failure reason notify.py sends too frequent notifications, misses failure reason Apr 15, 2019

@sadsfae sadsfae changed the title notify.py sends too frequent notifications, misses failure reason validate_env.py sends too frequent notifications, misses failure reason Apr 15, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.