Bug 1821643 - odo push on .net component tag 2.1+ does not work
Summary: odo push on .net component tag 2.1+ does not work
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat odo for OpenShift Container Platform
Classification: Red Hat
Component: rhodo
Version: 1.1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Girish Ramnani
QA Contact: Amit
Yana Hontyk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-07 09:51 UTC by Yana Hontyk
Modified: 2020-09-02 12:15 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-02 12:15:51 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift odo issues 2563 0 None closed odo push on .net component tag 2.1+ does not work 2020-09-02 12:12:05 UTC

Description Yana Hontyk 2020-04-07 09:51:30 UTC
Description of problem:
`odo push` fails on .NET component tag 2.1+ 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. odo component create dotnet:2.2 --project dotnet --context ../tests/examples/source/dotnet/

2. odo push

Actual results:
Fails to push

Expected results:
Successfully pushes

Additional info:

Comment 1 Tomáš Král 2020-09-02 12:15:13 UTC
https://github.com/openshift/odo/issues/2563#issuecomment-624571857


This can be resolved by specifing DOTNET_STARTUP_PROJECT.

odo config set --env DOTNET_STARTUP_PROJECT=<path to your project file>


This has been documented in odo docs.


Note You need to log in before you can comment on or make changes to this bug.