-
Notifications
You must be signed in to change notification settings - Fork 137
kfctl fails because directory not empty if run on kfctl apply #45
Comments
WorkaroundTo work around this put ${KFDEF} in a different directory then ${KFAPP} e.g.
|
/assign @zhenghuiwang |
@zhenghuiwang I think @richardsliu PR kubeflow/kubeflow#4115 fixed this. I think we just need to build and verify that. |
@jlewi I tried to reproduce/verify the issue. I think kubeflow/kubeflow#4115 fixes the dir checking problem mentioned. I think another problem is caused by some checks that I set the following (but not in the
and find things worked. (Also I guess if you pickup my changes on setting default project and zone, it would work too) One issue I find is some error logging missing (should be fixed in kubeflow/kubeflow#4279). With that, it is clear to see why kfApp is nil. Here is the error log with kubeflow/kubeflow#4279 produced when I follow your exact listed steps:
|
I think @richardsliu 's PR partially fixed this but we also need kubeflow/kubeflow#4275 |
picking up image change
There is a bug in kfctl and currently if you do the following
It will fail because the directory ${KFAPP} is non empty. Similarly if you try to rerun kfctl apply from ${KFAPP} it will fail because the directory isn't empty.
The problem is in the implementation of how kfctl gets the appDir. The desired semantics of
are
If the value of ${KFDEF} is a local file path; then we should use the directory of that file as the KFAPP directory regardless of whether it is empty
If the value of ${KFDEF} is a remote URI then we use the current working directory and check that it is empty.
This should be fixed by kubeflow/kubeflow#4115
The text was updated successfully, but these errors were encountered: