Closed sienna-oldaccountdontuse closed 2 years ago
@kialj876 @thorwolpert .
I checked this corp_num doesn't exist in CPROD. Is this a known issue?
@stevenc987 sound like maybe the call to MRAS hub isn't working. Perhaps this didn't get hooked up properly as part of OCP4 migration to PROD?
The UI responded as it did because the network call to fetch the MRAS profile failed. (The UI actually saw a "CORS error" but that's possibly because the API did not respond with a correct HTTP code.)
I saw this in the namex api logs:
Calling MRAS Jurisdictions API using [corp_num: 2023326222]
https://prodapi.mrasservice.ca//api/v1/xpr/jurisdictions/2023326222
{'x-api-key': 'BC:0d9524df-(snipped)', 'Accept': 'application/xml'}
Is it correct?
The MRAS_SVC_URL secret in OCP has a trailing /
. Maybe it shouldn't?
@pwei1018 @rarmitag could you confirm whether the MRAS hookup was reconnected with the OCP4 upgrade?
was this resolved?
The value for the MRAS_SVC_URL is the same as it was in OC3, so there would be no reason for it to stop working by moving it to OC4.
I don't think it's been resolved yet, has it @severinbeauvais ?
Reproduction Steps:
After about 15 seconds, this fails ("Corporate Number Not Found") and an error is printed to the dev console:
Access to XMLHttpRequest at 'https://namex.apps.silver.devops.gov.bc.ca/api/v1/mras-profile/AB/2023326222' from origin 'https://www.bcregistry.ca' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
14:27:55.260 instrument.js?ea14:109 fetchMRASProfile() = Error: Network Error [ Could not fetch mras profile ]
14:27:55.444 VM11:1 GET https://namex.apps.silver.devops.gov.bc.ca/api/v1/mras-profile/AB/2023326222 net::ERR_FAILED
So not yet fixed.
As I heard the MRAS keys were recently updated, I just tested this again. It still fails.
See also #7632 which was opened May 18th.
this looks like a bug that should be prioritized if tis broken? not sure why it has the blocked label on it? @jdyck-fw
I just pulled the 'blocked' label off of this one. I believe it may have been leftover from being blocked and tied to the answer required on "Home Jurisdiction needs to be written back to NamesP database".
@Sienna-Blumstengel any chance you might be able to confirm?
Was this related to Andre's ticket #6566?
@rarmitag It's not related to #6566. The issue is probably related to MRAS configuration or network access. Can you please check the conf props below from PROD and compare to other environments?
MRAS_SVC_API_KEY
MRAS_SVC_URL
The request to PROD (https://namex.apps.silver.devops.gov.bc.ca/api/v1/mras-profile/AB/2023326222) is having:
504 Gateway Time-out
The server didn't respond in time.
While in dev (https://namex-dev.apps.silver.devops.gov.bc.ca/api/v1/mras-profile/AB/2023326222) immediately brings the response:
{"error":"No profile found for the jurisdiction, registration number pair."}
It can be also firewall access from namex-api to mras service.
@lmcclung will get some test MRAS NRs for this. Also check with home team to see if mras is hooked up for Test.
@lmcclung FYI I just verified the getProfile in NRO prod for this company and it's working. This points to the namex/MRAS integration.
@eve-git Hi Eve, can you look at this one for your next ticket since it's about the MRAS hookup not working correctly?
Thanks.
The production issue does not like invalid-corp-number issue because instead of an error message returns, there is no response returned from hub.
I tested in test with Alberta 2110166911 and it works. I suppose that the code in test and prod are the same in this part. Probably the request URL has no problem.
An api-key should be in header for a MRAS request. I wonder if it is correct in prod. The api-key in oracle is at cprd-> SYSTEM_VARIABLES.SYSCHAR_CD='MRAS_API_KEY'
I am looking for the api-key in the app.
It is proved that the api-key in namerequest app are different from what in oracle database. Update the api-key in app environment should solve the problem. No code change needed.
Can someone on Ops pick this up as Eve doesn't have access to PROD yet?
please do not do that
@pwei1018 I understand you received a new key around May 11th. Could you update it?
@lmcclung @thorwolpert @eve-git @rarmitag According May 11th Update key email, our existing api key in Namex API is a new key. The key in COLIN is the old one we used before.
@andrepestana-aot had noted the issue a while back now.
@pwei1018 has opened a FW change to fix this.
@lmcclung @thorwolpert Firewall rule got change in both bcgov and MRAS. I verified it with new and old keys. Both works. Please verify it inside the application.
Good find Patrick. Firewall rules can be a real pain.
Woohoo thanks Patrick, I tested and it looks like it works! Will reach out to the client to see if this is resolved and can be closed. @pwei1018 could you please add an estimate on how long this ticket took to complete (maybe add buffer for other's contibutions?)
@Sienna-Blumstengel if you don't hear back from the client be EOD July 22, I recommend moving this one to done.
ServiceNow incident:
INC0086708
Contact information
Staff Name: Jennifer Weldon
Description
Before closing this ticket, remember to ask Sienna or Linda to inform IT Ops that this has been resolved!