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

Reset mount filesystem #137

Merged
merged 4 commits into from
Mar 18, 2024
Merged

Reset mount filesystem #137

merged 4 commits into from
Mar 18, 2024

Conversation

rustyShacklefurd
Copy link
Contributor

@rustyShacklefurd rustyShacklefurd commented Feb 23, 2024

Description:
This PR modifies the reset job. The reset job has to be run via mounting the PVC that is in use so that the correct filesystem locations are being reset. There is a limitation in the CSI driver (aka google-filestore-driver in GCP Log explorer) where the driver has a subsystem puts locks on the volume mapped to the pod; this makes it impossible to get the volume to attach to a secondary pod on the same node where the server-repository lives . This adding a secondary pod on the same node where the PVC is bound is documented as a working solution but the subsystem has a different setup.

Because of the limitation above, the reset job now runs kubectl to get the running server-repository pod, execs into the pod and triggers the reset script. There is a reset job for both previewnet and testnet

Related issue(s):

Fixes #43

Notes for reviewer:
These are the logs from the test environment run of this:

Defaulted container "sourcify-server" out of: sourcify-server, sourcify-repository
Unable to use a TTY - input is not a terminal or the right kind of file
Resetting Hedera previewnet (Chain ID: 297)
  /data/contracts/partial_match/297 does not exist
  /data/contracts/full_match/297 does not exist

Checklist

  • Documented (Code comments, README, etc.)
  • Tested (unit, integration, etc.)

…ing locally when running via docker-compose docs

Signed-off-by: Matt Halder <[email protected]>
…ogging errors and shows that it has a locking subsystem on the volume needed to run the operation on. Due to this limitation the operations will have to be triggered and carried out by the existing pod that is attached

Signed-off-by: Matt Halder <[email protected]>
…erver-repository k8s pod and triggers the reset script.

Signed-off-by: Matt Halder <[email protected]>
@rustyShacklefurd rustyShacklefurd requested review from quiet-node and Sheng-Long and removed request for a team February 23, 2024 20:06
…olebindings together with unpredictable results (i.e. some of the pieces were missing after deploy. Reordering of components showed the issue and then things were regrouped back together. This is working on the test ENV for right now

Signed-off-by: Matt Halder <[email protected]>
Copy link
Collaborator

@Nana-EC Nana-EC left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 clarification and a suggestion

@rustyShacklefurd rustyShacklefurd merged commit d6034bb into main Mar 18, 2024
4 of 10 checks passed
@rustyShacklefurd rustyShacklefurd deleted the reset-mount-filesystem branch March 18, 2024 17:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Confirm environment reset scripts
2 participants