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

[BUG] When custom repo is used backup/recovery stops working #1991

Closed
sk4zuzu opened this issue Jan 22, 2021 · 1 comment
Closed

[BUG] When custom repo is used backup/recovery stops working #1991

sk4zuzu opened this issue Jan 22, 2021 · 1 comment
Assignees
Labels
Milestone

Comments

@sk4zuzu
Copy link
Contributor

sk4zuzu commented Jan 22, 2021

Describe the bug
Backup/recovery uses resolved_repository_hostname which does not point to the correct VM when custom repository is used.

How to reproduce
Steps to reproduce the behavior:

  1. use custom repository during epicli apply
  2. enable something (anything really) to backup and run epicli backup

Expected behavior
No error, ansible stores backup artifacts correctly on a proper node.

Config files
N/A

Environment

  • Cloud provider: all
  • OS: all

Additional context
N/A

@sk4zuzu sk4zuzu added this to the S20210128 milestone Jan 22, 2021
@sk4zuzu sk4zuzu self-assigned this Jan 22, 2021
@mkyc mkyc modified the milestones: S20210128, S20210211 Jan 28, 2021
@przemyslavic przemyslavic self-assigned this Feb 2, 2021
@rpudlowski93 rpudlowski93 self-assigned this Feb 8, 2021
@rpudlowski93
Copy link
Contributor

  • Tested, works as expected ✅

I created new cluster with custom repository and postgresql + load balancer machines and after that I executed backup of the postgresql and load balancer instances and everything passed well, backups are stored on master node.

@mkyc mkyc closed this as completed Feb 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants