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

Fix the bug for upgrade flag #7896

Merged
merged 3 commits into from
May 24, 2023
Merged

Fix the bug for upgrade flag #7896

merged 3 commits into from
May 24, 2023

Conversation

SahithiMy
Copy link
Contributor

@SahithiMy SahithiMy commented May 16, 2023

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

Fixed the bug for upgrade-frontends flag which is upgrading backend nodes as-well.

⛓️ Related Resources

https://chefio.atlassian.net/browse/CHEF-1890

πŸ‘ Definition of Done

Fixed the bug for --upgrade-frontends for upgrade command.

πŸ‘Ÿ How to Build and Test the Change

rebuild components/automate-cli
chef-automate upgrade run --airgap-bundle latest.aib --upgrade-frontends

βœ… 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

Before upgrade
Screenshot 2023-05-22 at 2 00 46 PM

After upgrade
Screenshot 2023-05-16 at 6 46 13 PM

@netlify
Copy link

netlify bot commented May 16, 2023

πŸ‘· Deploy Preview for chef-automate processing.

Name Link
πŸ”¨ Latest commit a84b55d
πŸ” Latest deploy log https://app.netlify.com/sites/chef-automate/deploys/646dd41440b1c60008e81e09

@YashviJain01 YashviJain01 marked this pull request as draft May 22, 2023 10:14
@YashviJain01 YashviJain01 marked this pull request as ready for review May 23, 2023 06:08
SahithiMy added 3 commits May 24, 2023 14:38
Signed-off-by: SahithiMy <sahithi.mylangam@progress.com>
Signed-off-by: SahithiMy <sahithi.mylangam@progress.com>
Signed-off-by: SahithiMy <sahithi.mylangam@progress.com>
@sonarqube-for-infrastructure-prod

@kalroy kalroy merged commit 0e50cc1 into main May 24, 2023
4 checks passed
@kalroy kalroy deleted the sahithi/CHEF-1890 branch May 24, 2023 15:30
bvtejaswi pushed a commit that referenced this pull request May 24, 2023
* Fixed the bug for upgrade

Signed-off-by: SahithiMy <sahithi.mylangam@progress.com>

* Fix for upgrade

Signed-off-by: SahithiMy <sahithi.mylangam@progress.com>

* updated error msg

Signed-off-by: SahithiMy <sahithi.mylangam@progress.com>

---------

Signed-off-by: SahithiMy <sahithi.mylangam@progress.com>
Co-authored-by: SahithiMy <sahithi.mylangam@progress.com>
if err != nil {
return status.Annotate(err, status.DeployError)
if frontend {
err := moveAirgapFrontendBundlesOnlyToTransferDir(airgapMetadata, upgradeRunCmdFlags.airgap)
Copy link
Collaborator

Choose a reason for hiding this comment

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

upgradeRunCmdFlags.airgap -> airgapBundlePath

Copy link
Collaborator

Choose a reason for hiding this comment

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

while testing i found that the value of upgradeRunCmdFlags.airgap is nil, which create the problem while fresh deployment for HA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants