Add license scan report and status #2
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: fossabot <[email protected]>
|
Your license scan is passing -- congrats! Your badge status is now updated and ready to merge: |
tjoshum
pushed a commit
that referenced
this pull request
Mar 10, 2020
* CAS-23 propagate ShareProtocol from the wire to Nexus::share Once the value get to Nexus::shaere, discard it.
tiagolobocastro
pushed a commit
that referenced
this pull request
Mar 17, 2020
Add unimplemented mctl operations for getting rebuild state and rebuild progress. This will serve as a reference for adding future rebuild operations to mctl.
tiagolobocastro
pushed a commit
that referenced
this pull request
Mar 18, 2020
Add unimplemented mctl operations for getting rebuild state and rebuild progress. This will serve as a reference for adding future rebuild operations to mctl.
chriswldenyer
pushed a commit
that referenced
this pull request
Mar 20, 2020
* CAS-23 propagate ShareProtocol from the wire to Nexus::share Once the value get to Nexus::shaere, discard it.
chriswldenyer
pushed a commit
that referenced
this pull request
Mar 24, 2020
* CAS-23 propagate ShareProtocol from the wire to Nexus::share Once the value get to Nexus::shaere, discard it.
jkryl
pushed a commit
that referenced
this pull request
May 26, 2021
The problem was that the objects (old and new one) were basically the same except that order of entries in replicas array was different. Problem #1 is that we do useless update of CR and #2 is that k8s does not emit mod event in such case so volume-operator was timing out waiting for the event. The fix is to enforce deterministic order of entries in replicas array so that deep-equal compares the objects correctly.
bors bot
pushed a commit
that referenced
this pull request
May 26, 2021
901: fix(moac): timeouts when updating volume custom resource r=jkryl a=jkryl The problem was that the objects (old and new one) were basically the same except that order of entries in replicas array was different. Problem #1 is that we do useless update of CR and #2 is that k8s does not emit mod event in such case so volume-operator was timing out waiting for the event. The fix is to enforce deterministic order of entries in replicas array so that deep-equal compares the objects correctly. Co-authored-by: Jan Kryl <[email protected]>
dsavitskiy
added a commit
to dsavitskiy/mayastor
that referenced
this pull request
Oct 7, 2021
dsavitskiy
added a commit
to dsavitskiy/mayastor
that referenced
this pull request
Oct 7, 2021
dsavitskiy
added a commit
to dsavitskiy/mayastor
that referenced
this pull request
Oct 11, 2021
dsavitskiy
added a commit
to dsavitskiy/mayastor
that referenced
this pull request
Oct 12, 2021
dsavitskiy
added a commit
to dsavitskiy/mayastor
that referenced
this pull request
Oct 25, 2021
dsavitskiy
added a commit
to dsavitskiy/mayastor
that referenced
this pull request
Oct 25, 2021
dsavitskiy
added a commit
that referenced
this pull request
Nov 2, 2022
Signed-off-by: Dmitry Savitskiy <[email protected]>
dsavitskiy
added a commit
that referenced
this pull request
Nov 15, 2022
Signed-off-by: Dmitry Savitskiy <[email protected]>
dsavitskiy
added a commit
that referenced
this pull request
Dec 5, 2022
Signed-off-by: Dmitry Savitskiy <[email protected]>
dsavitskiy
added a commit
to dsavitskiy/mayastor
that referenced
this pull request
Oct 28, 2023
…rors NVMF subsystem will select different preconfigured CRDs for certain cases: openebs#1 is selected for all errors on nexus target except ENOSPC and reservation conflict openebs#2 is selected for ENOSPC and reservation conflict errors on nexus targets openebs#3 is selected for replica targets Signed-off-by: Dmitry Savitskiy <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Your FOSSA integration was successful! Attached in this PR is a badge and license report to track scan status in your README.
Below are docs for integrating FOSSA license checks into your CI: