Skip to content
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

Events are reported twice in dev mode #1297

Closed
lburgazzoli opened this issue Feb 25, 2020 · 1 comment
Closed

Events are reported twice in dev mode #1297

lburgazzoli opened this issue Feb 25, 2020 · 1 comment
Labels
good first issue Does not require full understanding of the codebase kind/bug Something isn't working
Milestone

Comments

@lburgazzoli
Copy link
Contributor

Running an integration with --dev flag like:

$ kamel run --dev examples/simple.groovy 

Leads to event being reported twice if the build takes some time:

integration "simple" created
Progress: integration "simple" in phase Initialization
IntegrationPlatformAvailable for Integration simple: camel-k
Integration simple in phase Initialization
Progress: integration "simple" in phase Building Kit
Integration simple in phase Building Kit
No IntegrationKitAvailable for Integration simple: creating a new integration kit
Integration simple dependent resource kit-bpafk8483bbsemjvspv0 (Integration Kit) changed phase to Build Submitted
Integration simple dependent resource kit-bpafk8483bbsemjvspv0 (Build) changed phase to Scheduling
Integration simple dependent resource kit-bpafk8483bbsemjvspv0 (Build) changed phase to Pending
Integration simple dependent resource kit-bpafk8483bbsemjvspv0 (Build) changed phase to Running
Integration simple dependent resource kit-bpafk8483bbsemjvspv0 (Integration Kit) changed phase to Build Running
IntegrationPlatformAvailable for Integration simple: camel-k
Integration simple in phase Initialization
No IntegrationKitAvailable for Integration simple: creating a new integration kit
Integration simple in phase Building Kit
Integration simple dependent resource kit-bpafk8483bbsemjvspv0 (Integration Kit) changed phase to Build Submitted
Integration simple dependent resource kit-bpafk8483bbsemjvspv0 (Build) changed phase to Scheduling
Integration simple dependent resource kit-bpafk8483bbsemjvspv0 (Build) changed phase to Pending
Integration simple dependent resource kit-bpafk8483bbsemjvspv0 (Build) changed phase to Running
Integration simple dependent resource kit-bpafk8483bbsemjvspv0 (Integration Kit) changed phase to Build Running
Integration simple dependent resource kit-bpafk8483bbsemjvspv0 (Build) changed phase to Succeeded
Integration simple dependent resource kit-bpafk8483bbsemjvspv0 (Build) changed phase to Succeeded
Progress: integration "simple" in phase Deploying
Integration simple dependent resource kit-bpafk8483bbsemjvspv0 (Integration Kit) changed phase to Ready
Integration simple dependent resource kit-bpafk8483bbsemjvspv0 (Integration Kit) changed phase to Ready
Integration simple in phase Deploying
Integration simple in phase Deploying
IntegrationKitAvailable for Integration simple: kit-bpafk8483bbsemjvspv0
IntegrationKitAvailable for Integration simple: kit-bpafk8483bbsemjvspv0
Progress: integration "simple" in phase Running
Integration simple in phase Running
Integration simple in phase Running
No ServiceAvailable for Integration simple: no http service required
No ServiceAvailable for Integration simple: no http service required
No ExposureAvailable for Integration simple: no host or service defined
No ExposureAvailable for Integration simple: no host or service defined
No CronJobAvailable for Integration simple: different controller strategy used (deployment)
No CronJobAvailable for Integration simple: different controller strategy used (deployment)
DeploymentAvailable for Integration simple: deployment name is simple
DeploymentAvailable for Integration simple: deployment name is simple

Looks like the event watch restarts after a timeout but the old watcher is still runnig.

@lburgazzoli lburgazzoli added the kind/bug Something isn't working label Feb 25, 2020
@lburgazzoli lburgazzoli added this to the 1.0.0 milestone Feb 25, 2020
@nicolaferraro nicolaferraro added the good first issue Does not require full understanding of the codebase label Mar 16, 2020
@nicolaferraro
Copy link
Member

This issue is no longer appearing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Does not require full understanding of the codebase kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants