-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HDDS-2225. SCM fails to start in most unsecure environments due to leftover secure config #1568
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
Conversation
|
/label ozone |
|
💔 -1 overall
This message was automatically generated. |
arp7
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 pending CI
|
Thanks @arp7 for the review.
|
|
Thanks @adoroszlai to fix this issue. Can you please help me to understand how is it possible. My assumption is that all the |
Thanks @elek for the question. After some more research it turns out that only |
|
Somewhat drastic but effective solution ;-) I am fine with removing it for now, but we need to create a proper ozone-spark later (with smoketest). |
|
💔 -1 overall
This message was automatically generated. |
…ftover secure config
…ue to leftover secure config" This reverts commit 64cc3c05ce2ccfa5746ec5077640f589e4f9517b.
…ftover secure config
|
💔 -1 overall
This message was automatically generated. |
|
@adoroszlai So now we have removed the mount and gen config? I am presuming that +1s were given for the earlier solution, but with force push I am not able to see the older changes. |
|
@anuengineer Thanks for taking a look at this.
The new solution only removes the offending container (spark), which is not required by the test at all. Volume mount and config generation for the other containers is not changed.
Both earlier solution (ff36710) and new one (5caa23a) are visible in the list of commits. The second commit just reverts the first attempt. The force push was needed only to rebase on current trunk. I agree, it makes understanding the conversation harder. I'll try a plain merge next time. Earlier +1s were for the first solution, while @elek's latest comment is for the second one. |
|
Thanks the patch @adoroszlai I am committing it to the trunk. Let's fix Spark later. |
|
Thanks @anuengineer, @arp7 and @elek for the reviews. |
…ftover secure config Closes apache#1568
…ftover secure config Closes apache#1568
What changes were proposed in this pull request?
Remove unnecessary
sparkcontainer fromozonesecure-mrtest, since it generates configs into the wrong directory (a mounted one). These configs are then picked up by other tests and cause failures.https://issues.apache.org/jira/browse/HDDS-2225
How was this patch tested?
Ran
ozonesecure-mrandozone-recontests in this order.