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

drenv olm addon: read: connection reset by peer #1337

Closed
3 tasks
nirs opened this issue Apr 10, 2024 · 0 comments · Fixed by #1397
Closed
3 tasks

drenv olm addon: read: connection reset by peer #1337

nirs opened this issue Apr 10, 2024 · 0 comments · Fixed by #1397
Assignees
Labels
bug Something isn't working test Testing related issue

Comments

@nirs
Copy link
Member

nirs commented Apr 10, 2024

Another random error, seen once or twice in hundreds of builds.

drenv.commands.Error: Command failed:
   command: ('addons/olm/start', 'dr1')
   exitcode: 1
   error:
      Traceback (most recent call last):
        ...
      drenv.commands.Error: Command failed:
         command: ('kubectl', 'wait', '--context', 'dr1', '--for=condition=established', '--filename=https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.22.0/crds.yaml')
         exitcode: 1
         error:
            error: error parsing https://github.com/operator-framework/operator-lifecycle-manager/releases/download/v0.22.0/crds.yaml: read tcp 10.70.62.126:50904->185.199.109.133:443: read: connection reset by peer

Should be fixed by #1290

I think we should:

  • Upgrade olm to latest version (Upgrade olm to version v0.27.0 #1260) - no point in spending time on old version
  • Add static kustomization installing all olm components (crds, operator)
    • This may not work - current code wait until crds are established, but it works for other addons
  • If the static kustomization works, cache it.
@nirs nirs mentioned this issue Apr 10, 2024
9 tasks
@nirs nirs added bug Something isn't working test Testing related issue labels Apr 10, 2024
@nirs nirs mentioned this issue May 17, 2024
abhijeet219 added a commit to abhijeet219/ramen that referenced this issue May 20, 2024
This change will start using cache for kustomization resources, so
starting the addon can directly use the cached resources.

Changes:
- drenv fetch can be used to fetch resources anytime.
- Starting an addon will first try to fetch resources, then apply the
  fetched resources. If there is no change, fetch won't do anything,
  so takes very less time.

Fixes: RamenDR#1337
Signed-off-by: Abhijeet Shakya <abhijeetshakya21@gmail.com>
abhijeet219 added a commit to abhijeet219/ramen that referenced this issue May 20, 2024
This change will start using cache for kustomization resources, so
starting the addon can directly use the cached resources.

Changes:
- drenv fetch can be used to fetch resources anytime.
- Starting an addon will first try to fetch resources, then apply the
  fetched resources. If there is no change, fetch won't do anything,
  so takes very less time.

Fixes: RamenDR#1337
Signed-off-by: Abhijeet Shakya <abhijeetshakya21@gmail.com>
nirs pushed a commit that referenced this issue May 20, 2024
This change will start using cache for kustomization resources, so
starting the addon can directly use the cached resources.

Changes:
- drenv fetch can be used to fetch resources anytime.
- Starting an addon will first try to fetch resources, then apply the
  fetched resources. If there is no change, fetch won't do anything,
  so takes very less time.

Fixes: #1337
Signed-off-by: Abhijeet Shakya <abhijeetshakya21@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working test Testing related issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants