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

Preserve the log file from a prior ocp-ansible.sh run #127

Open
viccross opened this issue Oct 27, 2022 · 3 comments
Open

Preserve the log file from a prior ocp-ansible.sh run #127

viccross opened this issue Oct 27, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@viccross
Copy link
Owner

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.

@viccross viccross added the enhancement New feature or request label Oct 27, 2022
@viccross viccross self-assigned this Oct 27, 2022
@viccross
Copy link
Owner Author

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.

@viccross
Copy link
Owner Author

Consider also relating it to the name of the cluster, for when/if named cluster support comes along.

@viccross
Copy link
Owner Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant