odo: wildfly component gets broken after storage is added
Steps to reproduce
git clone https://github.com/marekjelen/katacoda-odo-backend.git
cd /katacoda-odo-backend.
odo create wildfly
odo push
odo url create
# go to `<url>/counter`
# counter works
odo storage create data --path /data --size 100M
# wait a bit
# go to `<url>/counter`
# 404 - Not Found
odo push
# go to `<url>/counter`
# counter works
Reason why component gets broken is because widlfly assemble script moves compiled files to /wildfly/standalone/deployments
Moving all war artifacts from /opt/app-root/src/target directory into /wildfly/standalone/deployments for later deployment...
'/opt/app-root/src/target/ROOT.war' -> '/wildfly/standalone/deployments/ROOT.war'
removed '/opt/app-root/src/target/ROOT.war'
Path /wildfly/standalone/deployments
is not backed by persistent volume, so when deploymentConfig is modified (new mount is added) and new deployment is triggered we lose all data that were not in persistent volume.
This is wildfly specific issue. When I tested this with nodejs or php images everything was ok, as they leave and serve all data from /opt/app-root/
and we create persistent volume for this path by default.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 23 (22 by maintainers)
Commits related to this issue
- Resolves wildfly issue Fixes https://github.com/redhat-developer/odo/issues/445 — committed to surajnarwade/odo-supervisord-image by surajnarwade 6 years ago
- Resolves wildfly issue Fixes https://github.com/redhat-developer/odo/issues/445 — committed to surajnarwade/odo-supervisord-image by surajnarwade 6 years ago
- Resolves wildfly issue Fixes https://github.com/redhat-developer/odo/issues/445 — committed to surajnarwade/odo-supervisord-image by surajnarwade 6 years ago
- Resolves wildfly issue Fixes https://github.com/redhat-developer/odo/issues/445 — committed to surajnarwade/odo-supervisord-image by surajnarwade 6 years ago
- Resolves wildfly issue Fixes https://github.com/redhat-developer/odo/issues/445 — committed to surajnarwade/odo-supervisord-image by surajnarwade 6 years ago
- Resolves wildfly issue Fixes https://github.com/redhat-developer/odo/issues/445 — committed to surajnarwade/odo-supervisord-image by surajnarwade 6 years ago
- Resolves wildfly issue Fixes https://github.com/redhat-developer/odo/issues/445 — committed to surajnarwade/odo-supervisord-image by surajnarwade 6 years ago
- Resolves wildfly issue Fixes https://github.com/redhat-developer/odo/issues/445 — committed to surajnarwade/odo-supervisord-image by surajnarwade 6 years ago
this label is not label in imagestream but container (docker) image label
I am pretty sure that if we go down the go binary route, we will be able to make supervisord work seamlessly with s2i in a maintainable manner (much more than the bash scripts that test for the presence directories 😛 )
@kadel
I can confirm that this still does not work…