Bug 1821643

Summary: odo push on .net component tag 2.1+ does not work
Product: Red Hat odo for OpenShift Container Platform Reporter: Yana Hontyk <yhontyk>
Component: rhodoAssignee: Girish Ramnani <gramnani>
Status: CLOSED CURRENTRELEASE QA Contact: Amit <arout>
Severity: unspecified Docs Contact: Yana Hontyk <yhontyk>
Priority: unspecified    
Version: 1.1.xCC: tkral
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-02 12:15:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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.