containerized-data-importer
containerized-data-importer copied to clipboard
kubevirt
We need the "upload-pod" to show it's phase when we upload the vm's image
Is your feature request related to a problem? Please describe:
When we upload the image and we can only use what happening in "upload-pod" through using kubectl logs -f --tail 100 -n <namespace> upload-pod. The error cannot be reflected.
Describe the solution you'd like:
There are two soluations for that. The first way is that we use the DV's status or event to reflected the "upload-pod" pahse. And the second way is that we can add annotation for the "upload-pod". So we can get the error info If an error occurs in "upload-pod". I prefer the first way to realize it.
Describe alternatives you've considered:
Additional context: Add any other context or screenshots about the feature request here.
I think we can use a client in upload-pod to show the error info. Is there anybody who can give me any comments?
Hi @matthewei, thanks for opening this issue. Could you specify any particular errors you intend to address or report? Specific errors are more straightforward to report in the DV since we can parse exit codes or messages, and it's something we generally do. However, if it's about reporting the upload status without detailed errors, it might involve overengineering the pod a bit. Personally, I find the logs already provide sufficient information and serve as a solid solution.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kubevirt-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.