Bug 1771245 - UI created template cannot be used in cli
Summary: UI created template cannot be used in cli
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.3.0
Assignee: Yaacov Zamir
QA Contact: Nelly Credi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-12 03:07 UTC by Guohua Ouyang
Modified: 2020-01-23 11:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-23 11:12:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:0062 0 None None None 2020-01-23 11:12:36 UTC

Description Guohua Ouyang 2019-11-12 03:07:25 UTC
Description of problem:
Create a template 'ccc' from template wizard on web console, try to use it from cli get below error:

$ oc process ccc -p NAME=test123 | oc create -f -
The  "" is invalid: spec.running: One of Running or RunStrategy must be specified

Add "running: false" to the template can make it work.
----------------------
  spec:
    running: false
    template:
----------------------

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-11-02-092336

How reproducible:
100%

Steps to Reproduce:
1. Create a template 'ccc' from ui
2. Use it to create VM from cli via `oc process ccc -p NAME=test123 | oc create -f -`
3.

Actual results:


Expected results:


Additional info:

Comment 1 Yaacov Zamir 2019-11-12 13:13:45 UTC
submitted upstream:
https://github.com/openshift/console/pull/3355

Comment 2 Yaacov Zamir 2019-11-14 07:13:27 UTC
merged upstream:
https://github.com/openshift/console/pull/3355

Comment 4 Radim Hrazdil 2019-11-29 11:50:25 UTC
Verified
4.3.0-0.nightly-2019-11-21-122827

Comment 6 errata-xmlrpc 2020-01-23 11:12:18 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0062


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