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
In the case of a retry, when the new Ansible run is started the old log file is removed. If someone attempts a cluster rebuild "over the top" of an existing build, the reason they attempted the prior build is lost. Let's change the process so that the log file is date/time sensitive and "rotated" when a new attempt is generated.
Possibly corollary to this should be the return of the lockout of the automation to prevent multiple or simultaneous build runs.
The text was updated successfully, but these errors were encountered:
Possible implementation: the actual log file is created with a timestamp, and /var/www/html/logfile.txt is a symlink to that file. When a new attempt is started, the symlink is updated.
New plan: a userid created for each cluster. This userid will have all the content for that given cluster: install-config.yaml, logfile(s), links to corresponding OpenShift clients, etc.
In the case of a retry, when the new Ansible run is started the old log file is removed. If someone attempts a cluster rebuild "over the top" of an existing build, the reason they attempted the prior build is lost. Let's change the process so that the log file is date/time sensitive and "rotated" when a new attempt is generated.
Possibly corollary to this should be the return of the lockout of the automation to prevent multiple or simultaneous build runs.
The text was updated successfully, but these errors were encountered: