-
Notifications
You must be signed in to change notification settings - Fork 243
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
unable to push component created with beta3 version #1910
Comments
@kadel , can you point me to example java repo ? |
@kadel , your |
@kadel I am not able to reproduce this. Steps i followed:
@kadel Can please provide the detail steps
@surajnarwade See the config file i pasted above. That also does not have the |
/me on latest master
@amitkrout I followed your steps for java s2i image here's my localconfig with ports
cc @amitkrout @kadel |
I tested it on beta-3 bits. Then the changes of port info in the config file is not the part of beta-3 releases. |
@amitkrout because there's no release after my PR got merged |
To reproduce the issue you have to create a component using beta3 and then run push using the latest master. |
push expects the ports to be in the local config, but the older version was not adding it when
|
yes, overall what that PR is doing is right. What if |
@kadel ,
|
Though I agree with this 😺
|
the problem is that when the component was created with older odo versions (beta3 and older) push won't work. |
We need to include some upgrade path test in our test. |
adapter will be released with beta4 so we dont need to provide a upgrade path |
This is probably due to latest chnages in #1828
ping @surajnarwade
The text was updated successfully, but these errors were encountered: