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

Backend throws container instance not found error, while deleting the s3 service #11700

Closed
ShaileshParmar11 opened this issue May 22, 2023 · 0 comments
Assignees
Labels

Comments

@ShaileshParmar11
Copy link
Contributor

Affected module
Does it impact the UI, backend or Ingestion Framework?
Backend

Describe the bug
A clear and concise description of what the bug is.

To Reproduce

  1. Ingest S3 data
  2. once ingestion is successful re-run the ingestion pipeline
  3. Delete s3 service
    For more details please refer to the attached video

Note:- The same scenario is working fine with other services

Screenshots or steps to reproduce

Screen.Recording.2023-05-22.at.10.55.05.AM.mov

Expected behavior
A clear and concise description of what you expected to happen.

Version:

  • OS: [e.g. iOS]
  • Python version:
  • OpenMetadata version: [e.g. 0.8]
  • OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[docker]==XYZ]

Additional context
Add any other context about the problem here.

@harshach harshach assigned harshach and unassigned mohityadav766 Jul 29, 2023
@harshach harshach removed this from Release 1.1 Aug 5, 2023
@harshach harshach moved this to Backend - Bugs & Minor Features in Release 1.3.0 Oct 22, 2023
harshach added a commit that referenced this issue Jan 9, 2024
@harshach harshach moved this from Backend - Bugs & Minor Features to Done in Release 1.3.0 Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Status: Done
Development

No branches or pull requests

3 participants