You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are seeing notify.py send out premature released notifications to users before assignments have actually completed their validation workflow.
This seems to occur right at 22:00 UTC when the assignment starts to be provisioned, but the assignments wiki does show they are not released yet and still validating.
The text was updated successfully, but these errors were encountered:
when running notify.py we are checking for validated clouds but old
clouds that moved back to default cloud remained validated.
added logic to move old clouds back to validated=False.
Closes: #317
Change-Id: I09614cb58628b38b428af265241cc619765806ae
quads-1.1.2-20200122.noarch
3.7
Fedora 29
Describe the bug
This behavior is partly captured here and related:
#307
We are seeing
notify.py
send out premature released notifications to users before assignments have actually completed their validation workflow.This seems to occur right at
22:00 UTC
when the assignment starts to be provisioned, but the assignments wiki does show they are not released yet and still validating.The text was updated successfully, but these errors were encountered: