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

odo watch redeploys component during first push #3841

Closed
mik-dass opened this issue Aug 26, 2020 · 4 comments · Fixed by #3860
Closed

odo watch redeploys component during first push #3841

mik-dass opened this issue Aug 26, 2020 · 4 comments · Fixed by #3860
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).

Comments

@mik-dass
Copy link
Contributor

/kind bug

How did you run odo exactly?

odo push
odo watch

Actual behavior

The component is redeployed during the first push triggered by watch.

Expected behavior

The component shouldn't be redeployed.

Any logs, error output, etc?


Executing devfile commands for component nodejs
 ✓  Executing install command "npm install" [8s]
 ✓  Executing run command "npm start" [5s]

Pushing devfile component nodejs
 ✓  Changes successfully pushed to component
[mrinaldas@localhost project]$ odo watch
Waiting for something to change in /home/mrinaldas/project
File /home/mrinaldas/project/check.sh changed
Pushing files...

Validation
 ✓  Validating the devfile [61668ns]

Creating Kubernetes resources for component nodejs
 ✓  Waiting for component to start [6s]        // redeployed

Applying URL changes
 ✓  URLs are synced with the cluster, no changes are required.

Syncing to component nodejs
 ✓  Checking file changes for pushing [1ms]
...
@mik-dass mik-dass added the kind/bug Categorizes issue or PR as related to a bug. label Aug 26, 2020
@mik-dass
Copy link
Contributor Author

Due to the issue mentioned here #3838 (comment), this causes the component to break too.

@devang-gaur
Copy link
Contributor

I think when this redeployment happens, the build command is skipped... and then the run command crashes... (coz build needs to run inside a fresh container)

image

@mik-dass
Copy link
Contributor Author

mik-dass commented Aug 26, 2020

I think when this redeployment happens, the build command is skipped

The build is not skipped, npm install and thus the build doesn't fail when package.json is not present. This is something @kadel found out today.

@jgwest
Copy link
Contributor

jgwest commented Aug 28, 2020

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants