-
Notifications
You must be signed in to change notification settings - Fork 592
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
fix(nms): nginx ssl issue #15215
fix(nms): nginx ssl issue #15215
Conversation
Thanks for opening a PR! 💯
Howto
More infoPlease take a moment to read through the Magma project's
If this is your first Magma PR, also consider reading
|
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.
Code changes look good.
Signed-off-by: prabina pattnaik <prabinak@wavelabs.ai>
9a45078
to
2874ad9
Compare
CI is red, due to out of disk space in a build: and nms yarn test is red: https://github.com/magma/magma/actions/runs/5280377687/jobs/9558018580?pr=15215 |
@maxhbr , any idea why "nms yarn test" is failed. Is it lint error or test case failed error. |
you can look in the log and see the test summary:
there are test failures |
Yes, I have seen yesterday on that logs but could not get the clue for whether these errors are link with changes or existing error. |
it seems to be a general issue that needs to be resolved. Also other PRs have the same issues in the log https://github.com/magma/magma/actions/runs/5247558970/jobs/9477884882?pr=15211 |
@maxhbr , can we do force merge the changes as both CI checks are failing because of one is know issue and another is disk space issue. |
see https://magmacore.slack.com/archives/C01Q1T14YJ2/p1686916038724709?thread_ts=1686905954.161159&cid=C01Q1T14YJ2, since there is no process for force merges. |
Signed-off-by: prabina pattnaik <prabinak@wavelabs.ai>
@@ -318,6 +318,8 @@ describe('<TrafficDashboard APNs/>', () => { | |||
const networkId = 'test'; | |||
|
|||
beforeEach((): void => { | |||
// @ts-ignore | |||
delete window.location; |
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.
if you start working on fixing CI runs, force merges are no longer an option. Would also fit to be put into its own PR?
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.
Hey, can you remove that commit again, so that the impact of a potential force merge is smaller? Also: the commit message is not very helpful.
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.
Sure.
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.
ping: can someone drop that commit, so that we can move forward?
Seems like the underlying failure is meaningful:
However, the code in this commit doesn't do anything in NMS, so the problem must be a prior commit. Do you agree? |
see: #15215 (comment) the NMS error already appeared in other CI runs before this change. So, for NMS the answer is probably yes. |
I have raised new PR for this issue fix. |
Good, that change can be discussed there and the decision whether it is appropriate does not block this PR. |
@prabinakpattnaik : you still need to drop 34da9f8 from this PR to unblock it. |
@maxhbr , I am doing now. |
Signed-off-by: prabina pattnaik <prabinak@wavelabs.ai>
now it does the change, and reverts it again. But after squashing that should be hidden. Now we just need to find someone that is able to force-merge. This was made harder with some of the recent policy changes (ping @lucasgonze). see also: https://magmacore.slack.com/archives/C01Q1T14YJ2/p1687165644395929?thread_ts=1686905954.161159&cid=C01Q1T14YJ2 |
Force merge with go from Lucas Gonze: https://magmacore.slack.com/archives/C01Q1T14YJ2/p1687184855726759 * fix(nms): nginx ssl issue Signed-off-by: prabina pattnaik <prabinak@wavelabs.ai> * fix(nms): nginx ssl issue Signed-off-by: prabina pattnaik <prabinak@wavelabs.ai> * fix(nms): nginx ssl issue Signed-off-by: prabina pattnaik <prabinak@wavelabs.ai> --------- Signed-off-by: prabina pattnaik <prabinak@wavelabs.ai>
Below error is observed when creating orc8r pods:
2023/06/15 13:34:36 [emerg] 1#1: unknown directive "ssl" in /etc/nginx/conf.d/nginx_proxy_ssl.conf:3
nginx: [emerg] unknown directive "ssl" in /etc/nginx/conf.d/nginx_proxy_ssl.conf:3
orc8r nms-nginx-proxy-7454448447-xzc8l 0/1 CrashLoopBackOff 7 (119s ago) 16m