Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1508391 - [CRI-O] ASB etcd container cannot start in cri-o environment, but can work well in docker env
[CRI-O] ASB etcd container cannot start in cri-o environment, but can work we...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Containers (Show other bugs)
3.7.0
Unspecified Unspecified
high Severity high
: ---
: 3.8.0
Assigned To: Antonio Murdaca
Zhang Cheng
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-11-01 07:22 EDT by Zhang Cheng
Modified: 2018-03-28 10:09 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-03-28 10:08:55 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
cri-o.log (5.28 MB, application/x-gzip)
2017-11-01 22:19 EDT, DeShuai Ma
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 None None None 2018-03-28 10:09 EDT

  None (edit)
Comment 2 DeShuai Ma 2017-11-01 22:19 EDT
Created attachment 1346826 [details]
cri-o.log
Comment 3 Antonio Murdaca 2017-11-03 12:29:31 EDT
Reproduced, fix coming.
Comment 4 Antonio Murdaca 2017-11-03 14:04:53 EDT
Fix is upcoming in CRI-O v1.0.3: https://github.com/kubernetes-incubator/cri-o/pull/1118
Comment 6 Zhang Cheng 2018-01-03 01:52:09 EST
Verified and passed.
CRI-O version: v1.0.4

Service-catalog & ASB critical test pass in CRI-O environment. LGTM
Comment 9 errata-xmlrpc 2018-03-28 10:08:55 EDT
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-2018:0489

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