Bug 1564849
| Summary: | Command in warning message is incomplete | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Wenjing Zheng <wzheng> |
| Component: | oc | Assignee: | Maciej Szulik <maszulik> |
| Status: | CLOSED ERRATA | QA Contact: | Wenjing Zheng <wzheng> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 3.10.0 | CC: | aos-bugs, jokerman, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | 4.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-04 10:40:21 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: | |||
Verified with below version:
Client Version: v4.0.22
Server Version: v1.12.4+0ba401e
* WARNING: The Dockerfile has some invalid ports in EXPOSE instruction: [failed to parse port /tcp: [port number must be in range 0 - 65535]]
* The image does not expose any ports - if you want to load balance or send traffic to this component
you will need to create a service with 'oc expose dc/ocnewappexpose --port=[port]' later
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 |
Description of problem: Command in warning message is incomplete like below: * WARNING: The Dockerfile has some invalid ports in EXPOSE instruction: [failed to parse port /tcp: [port number must be in range 0 - 65535]] * The image does not expose any ports - if you want to load balance or send traffic to this component you will need to create a service with 'expose dc/ocnewappexpose --port=[port]' later Version-Release number of selected component (if applicable): oc v3.10.0-0.16.0 How reproducible: always Steps to Reproduce: 1.Define incorrect port in Dockerfile 2.Build with it 3. Actual results: Command in warning is like below: expose dc/ocnewappexpose --port=[port] Expected results: It should be oc expose dc/ocnewappexpose --port=[port] Additional info: