Bug 1760586 - odo delete enters an infinite loop after project is delete and component name is set
Summary: odo delete enters an infinite loop after project is delete and component name...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: odo
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
Yana Hontyk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-10 21:20 UTC by Yana Hontyk
Modified: 2022-11-07 08:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-07 08:15:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift odo issues 1952 0 'None' closed odo delete enters an infinite loop after project is deleted and component name is set 2022-11-07 08:15:02 UTC

Description Yana Hontyk 2019-10-10 21:20:30 UTC
Description of problem:
odo delete enters an infinite loop after project is delete and component name is set

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


How reproducible:


Steps to Reproduce:
1. oc delete project/demoproj
2. odo create
3. once you see "What do you wish to name the new component", enter a different name and you will enter the infinite loop

Actual results:
$ odo create
? Which component type do you wish to create java
? Which version of 'java' component type do you wish to create 8
? Which input type do you wish to use for the component local
? Location of path component, relative to 'C:\work\src\tmp\springboot-rest' C:\work\src\tmp\springboot-rest
X Sorry, your reply was invalid: Unable to determine if component 'comp1' exists or not
? What do you wish to name the new component (java-nqmv)

Expected results:
Accept the provided name

Additional info:


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