-
Notifications
You must be signed in to change notification settings - Fork 23
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
Direct WFS - An error has occurred - Internal domain used? #960
Comments
Dear @joachimnielandt , We have investigated this issue, taking into account your conclusions, but as we checked the requested URL it seemed to be /inspirevalidator. As we see it, it seems that this can be caused due to a temporary unavailability of the Team Engine endpoint while the Validator is started and the ETSs are created in the Validator's instance. If you have tried to redeploy and it still doesn't work, can you check if you has modified the TeamEngine credentials in the config.js? Hope these two advices are of help, if they don't help to solve the issue, please contact us again. Thanks for your attention |
Dear @joachimnielandt , did you have the chance to test the proposed solution? Thanks! |
Dear @jenriquesoriano , sorry for the delay, the holiday period cropped up I'm afraid.
Indeed, I do not see the references to /validator anymore. Perhaps this was unrelated then. I have retried the scenario as I described above and I still get the "An error has occurred" message though.
Indeed, 213, I did not know this aspect of the validator yet.
There hasn't been a deployment in the mean while, although the service has been restarted daily. The pods don't have persistent storage so it's really the following that is running:
I have now tried to redeploy with the teamengine credentials filled in (etf-config.properties). Upon running the 'direct wfs test' again...
... I get the following 404 with responseText (notice the 'url' being the internal hostname, not the external/correct one):
|
Tried the same setup with 2023.2 but this resulted in the same erroneous behaviour (currently deployed on https://metadata.dev-vlaanderen.be/inspirevalidator) |
Using an older account seems to be helping in returning the desired 216 ETSs. However, the direct WFS test still fails, now with the following in console:
Hopefully this gives a further clue on what is going wrong? |
Update when running 2023.3, I am seeing the same behaviour. Currently the ETF credentials are not set, which lead to the original error where the internal domain is used (I am thinking this is the actual issue at hand for me). To reiterate:
Test setup:
Network behaviour:
At some point, the validator tries to retrieve the following url (http://dev.pre.aks-ingress.mdv/validator/v2/TestRuns) and fails, which is to be expected. |
Description
I have set up 2023.1 in a kubernetes environment with modified files (config.js and etf-config.properties) such that the domain is properly configured. I did this by deploying the base docker image and mounting the modified files in the relevant locations.
Most of the tests now function correctly, except for the
Download Service > WFS > Direct WFS
option, which results in 'An error has occurred' message.Reproduction
The deployment can be found here: https://metadata.dev-vlaanderen.be/inspirevalidator/
Using the service url https://geo.api.vlaanderen.be/hy-p/wfs?service=WFS&request=getcapabilities in the
Direct WFS
option results in the error message.Possible issue
I can see in the console some output, which references an internal domain name (in this case the url http://dev.pre.aks-ingress.mdv/validator/v2/TestRuns is shown).
/validator
is not a valid reference here (accessing the internal domain should go through/inspirevalidator
), so I suspect I still miss a configuration property somewhere?The text was updated successfully, but these errors were encountered: