Troubleshooting empty HDI if subscribed on Windows#2550
Troubleshooting empty HDI if subscribed on Windows#2550
Conversation
| ``` | ||
| On macOS and Linux, the built-in implementation continues to be used. | ||
|
|
||
| ### Why are tenant HDI containers empty after subscription on Windows? |
There was a problem hiding this comment.
This is only valid for hybrid testing, right?
There was a problem hiding this comment.
yes, in production you usually sibscribe in CF cockpit
There was a problem hiding this comment.
what difference does this make? If you have built your app on windows, then the resources.tgz is missing (or empty), and then nothing gets deployed to the HDI container, no matter how you subscribe.
So I think this applies also to production.
Or am I wrong here?
There was a problem hiding this comment.
What I mean: it doesn't matter how you subscribe, but how the app is built
There was a problem hiding this comment.
@stewsk: Agree, then we should change from "troubleshooting empty HDI" - just copied it from the issue :) - to "issues building MTX resources". And for the last one we already have troubleshooting item above - I will modify it.
There was a problem hiding this comment.
But the visible impact is on the deployed application
There was a problem hiding this comment.
@ecklie: In some cases we obtain an explicite error "tar: Error is not recoverable" by cds build. In some other cases cds build may silently fail, which can be seen only on the deployed application. My question for now: In troubleshooting guide - should it be one or two sections?
There was a problem hiding this comment.
For the error message we do have the troubleshooting info already. So this can be found. How would we describe the other case? How would one notice on the deployed application if the build doesn't throw an error?
There was a problem hiding this comment.
How would we describe the other case? How would one notice on the deployed application if the build doesn't throw an error?
This is exactly what the newly added section does: "Why are tenant HDI containers empty after building app on Windows?"
My question was if we should merge those two section?
ecklie
left a comment
ecklie
left a comment
There was a problem hiding this comment.
Yes, the problem is caused by the build. It also has impact on the productive app. We need to check if we can improve the build and add a consistency check.
| ``` | ||
| On macOS and Linux, the built-in implementation continues to be used. | ||
|
|
||
| ### Why are tenant HDI containers empty after building app on Windows? |
There was a problem hiding this comment.
I might be wrong or simplify it too much, but to me this reads as if there's is already a first analysis done and I found that HDI containers are empty.
What is it that makes me investigate? Like "Can't get/read data from customer tenant"?. So folks who have not done an initial analysis and found the empty containers, what would they look for in our troubleshooting?
There was a problem hiding this comment.
Here the ticket describibg the issue: https://github.tools.sap/cap/issues/issues/19999.
There was a problem hiding this comment.
in my case the "symptom" was that I got funny runtime errors from the Node.js runtime saying that table xyz is not there (don't remember the precise error message)
There was a problem hiding this comment.
Right. It is not after building an app but after subscription.
"Why are tenant HDI containers empty after tenant subscription"
It think the error message is something like "table not found". I will check it.
There was a problem hiding this comment.
SqlError: invalid table name: Could not find table/view ...
4 participants
No description provided.