Bug 1671948
| Summary: | ConfigMap pod crashed due to the type conversion | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jian Zhang <jiazha> |
| Component: | OLM | Assignee: | Evan Cordell <ecordell> |
| Status: | CLOSED ERRATA | QA Contact: | Jian Zhang <jiazha> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.1.0 | CC: | jpeeler, vdinh |
| Target Milestone: | --- | ||
| Target Release: | 4.1.0 | ||
| 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: | 2019-06-04 10:42:31 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: | |
| Embargoed: | |||
|
Description
Jian Zhang
2019-02-02 09:21:04 UTC
I'm not really sure this is a bug. The expected version format is of the form "x.x.x", for example 1.13.0. If you must use a less precise format (I suppose 1.13 could be interpreted as 1.13.0), then just quote the version number in the configmap, like: minKubeVersion: '1.10' Jeff,
> The expected version format is of the form "x.x.x", for example 1.13.0.
Yes, thanks, I know. But, it would be better if it can compatible with something characters like `minKubeVersion: test-v1.xx`.
Hi Jian, As Jeff mentioned above, the minimum k8s version will be Major.Minor.Patch (all integers) format which is standard SemVer format. I have merged a PR to allow the prefix "v" just in case users may add that. However, we will not accept any non-standard format or characters. Please use valid format to test the code. Thanks, Vu Hi, Vu
> However, we will not accept any non-standard format or characters.
Thanks for your information. So does it pop-up a warning when typing the non-standard format to the csv?
Actually, I haven't seen any warnings or forbidden. Correct me if I'm wrong.
Crashing is the expected behavior when invalid csvs are included in a catalog. Evan, Vu Yes, I know, we should fill in the standard format. But, for the users, they may input a variety of formats even if we highlight this in the release document. So, it's better if we can pop-up the forbidden info before they saving the wrong format. > So, it's better if we can pop-up the forbidden info before they saving the wrong format. Fixed PR in bug 1671953 comment 9, hasn't been merged in the current payload, change Status to MODIFIED. [jzhang@dhcp-140-18 ocp-09]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-03-06-074438 True False 35h Cluster version is 4.0.0-0.nightly-2019-03-06-074438 I can see the warning now, LGTM, verify it.
OLM info:
io.openshift.build.commit.id=840d806a3b20e5ebb7229631d0168864b1cfed12
io.openshift.build.commit.url=https://github.com/operator-framework/operator-lifecycle-manager/commit/840d806a3b20e5ebb7229631d0168864b1cfed12
io.openshift.build.source-location=https://github.com/operator-framework/operator-lifecycle-manager
Cluster version: 4.0.0-0.nightly-2019-03-13-233958
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-2019:0758 |