Skip to content

Issues: noobaa/noobaa-core

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.

Sign up for GitHub

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

119 Open 2,604 Closed
119 Open 2,604 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

NC | NSFS | Add Error Logs Printings In All bucketspace_fs Methods NS-FS
#8699 opened Jan 16, 2025 by shirady
Improve Bucket Policy Code Ideas (Use Enum)
#8697 opened Jan 16, 2025 by shirady
npm run pkg failed due to No available node version
#8686 opened Jan 14, 2025 by lzw06061139
5
During upgrade, if few hosts are not reachble in --expected_hosts, noobaa is not throwing any warning Non Containerized Non containerized
#8672 opened Jan 9, 2025 by PravinRanjan10
2
NSFS | macos | buckets created with parent directory GID instead of thread (user) GID NS-FS
#8665 opened Jan 8, 2025 by nadavMiz
If connection fails for the first few events it fails for others as well in the events.log file NS-FS
#8653 opened Jan 6, 2025 by ramya-c3
multiple events support are not working in the bucket.json/notification.json then it fails to send the event in the array NS-FS
#8652 opened Jan 6, 2025 by ramya-c3
https to http not getting supported for notification push of the events NS-FS
#8651 opened Jan 6, 2025 by ramya-c3
Why are we appending node names to the event name NS-FS
#8650 opened Jan 6, 2025 by ramya-c3
put-bucket notification should check the connection before saving the information to the bucket NS-FS
#8649 opened Jan 6, 2025 by ramya-c3
When connection fails the event file is not getting renamed with failure status NS-FS
#8648 opened Jan 6, 2025 by ramya-c3
Multi level connections are not supported NS-FS
#8647 opened Jan 6, 2025 by ramya-c3
password is getting exposed in connections_kv.json file NS-FS
#8643 opened Jan 2, 2025 by ramya-c3
CI | Investigation of Tests That Are Failing in the CI (Encryption tests, namespace caching)
#8623 opened Dec 22, 2024 by shirady
SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at NamespaceFS.complete_object_upload NS-FS
#8620 opened Dec 20, 2024 by rkomandu
@shirady
4
ENDPOINT CLIENT ERROR - REPLY WITH BAD REQUEST [Error: Parse Error: Invalid header value char] NS-FS
#8618 opened Dec 20, 2024 by rkomandu
@shirady
2
Request without required Headers for STS and IAM NS-FS
#8617 opened Dec 20, 2024 by naveenpaul1
Events gets missed in case when node goes to suspended mode or goes down NS-FS
#8609 opened Dec 18, 2024 by ramya-c3
1
loosing information when noobaa log level is set to all, when rate limit is on (rsyslog) NS-FS
#8606 opened Dec 18, 2024 by rkomandu
@naveenpaul1
1
NooBaa nsfs service showing Error No disk candidates found at generate entropy due to unsupported /dev/nvme0 devices NS-FS
#8598 opened Dec 17, 2024 by ramya-c3
1
9
NC | Documentation and CLI help gaps Non Containerized Non containerized NS-FS
#8595 opened Dec 16, 2024 by naveenpaul1
@naveenpaul1
S3 ListBuckets implement prefix parameter S3-Compatibility S3 Compatibility and Namespace over AWS
#8594 opened Dec 15, 2024 by guymguym
NC | Online upgrade improvements Non Containerized Non containerized
#8586 opened Dec 8, 2024 by romayalon
11 of 12 tasks
2
NC | Noobaa Service Does Not Contain --unhandled-rejections=warn Non Containerized Non containerized NS-FS
#8570 opened Dec 2, 2024 by shirady
2
fix or remove set_keep_alive_whitespace_interval
#8569 opened Dec 2, 2024 by nadavMiz
ProTip! Exclude everything labeled bug with -label:bug.