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

Restore Doc Troubleshoot section update #8732

Merged
merged 5 commits into from
Jan 8, 2025
Merged

Conversation

SanjuPal01
Copy link
Collaborator

@SanjuPal01 SanjuPal01 commented Jan 7, 2025

πŸ”© Description: What code changed, and why?

⛓️ Related Resources

https://progresssoftware.atlassian.net/browse/CHEF-17894

πŸ‘ Definition of Done

πŸ‘Ÿ How to Build and Test the Change

βœ… Checklist

All PRs must tick these:

With occasional exceptions, all PRs from Progress employees must tick these:

  • Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
  • Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
  • Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
  • Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
  • Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

  • Tests added/updated? (all new code needs new tests)
  • Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.

πŸ“· Screenshots, if applicable

Signed-off-by: β€œSanjuPal01” <[email protected]>
@SanjuPal01 SanjuPal01 requested a review from a team as a code owner January 7, 2025 09:19
@github-actions github-actions bot added the documentation Anything related to the Automate docs. label Jan 7, 2025
Copy link

netlify bot commented Jan 7, 2025

βœ… Deploy Preview for chef-automate ready!

Name Link
πŸ”¨ Latest commit fbe921c
πŸ” Latest deploy log https://app.netlify.com/sites/chef-automate/deploys/677e78b3baafa100087a92dc
😎 Deploy Preview https://deploy-preview-8732--chef-automate.netlify.app
πŸ“± Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Signed-off-by: β€œSanjuPal01” <[email protected]>
@SanjuPal01 SanjuPal01 requested review from a team and dishanktiwari2501 January 7, 2025 09:35
Signed-off-by: Dishank Tiwari <[email protected]>
Copy link
Collaborator

@Dmaddu Dmaddu left a comment

Choose a reason for hiding this comment

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

please update the error message as well

Signed-off-by: β€œSanjuPal01” <[email protected]>
@@ -213,7 +213,7 @@ Success: Restored backup 20180517223558
chef-automate debug set-log-level deployment-service debug
```

1. To restore a backup on a different host with an existing Automate deployment, delete the `.tmp` folder in the configured backup directory before proceeding (the default directory is `/var/opt/chef-automate/backups`).
1. If you already deployed Chef Automate and while restoring you are getting this error in logs: `The Access Key Id you provided does not exist in our records.`, then delete the `.tmp` folder in the configured backup directory before proceeding (the default directory is `/var/opt/chef-automate/backups`).
Copy link
Collaborator

Choose a reason for hiding this comment

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

Replace it with: 1. If you have already deployed Chef Automate and are getting this error in the logs while restoring: The Access Key ID you provided does not exist in our records. Before proceeding, delete the .tmp folder in the configured backup directory (the default directory is /var/opt/chef-automate/backups).

Signed-off-by: β€œSanjuPal01” <[email protected]>

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@Dmaddu Dmaddu merged commit 82a3333 into main Jan 8, 2025
9 of 12 checks passed
@Dmaddu Dmaddu deleted the sanju/backup_doc_change branch January 8, 2025 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Anything related to the Automate docs.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants