Bug 1569684

Summary:	etcd-docker build for 7.5.1
Product:	Red Hat Enterprise Linux 7	Reporter:	Avesh Agarwal <avagarwa>
Component:	etcd-container	Assignee:	Avesh Agarwal <avagarwa>
Status:	CLOSED ERRATA	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.5	CC:	ypu
Target Milestone:	rc	Keywords:	Extras
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	etcd-docker-3.2.18-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-14 17:14:28 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 Avesh Agarwal 2018-04-19 19:32:01 UTC

Description of problem:
etcd-docker build for 7.5.1

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 5 Joy Pu 2018-05-11 05:21:42 UTC

Test the image with following cases:
1. Start etcd container Start the container in following ways
 a) Start etcd container directly
 b) sharing ports with host
 c) sharing network with host
2. Key value test for etcd Star etcd container and sharing network with host and do following tests:
 1) Check etcd version info via curl/etcdctl
 2) Set/get/update/remove key value via curl/etcdctl
 3) Watch key value via curl/etcdctl
 4) TTL test for key value
3.cluster test Set up a etcd cluster with three node
 a) setup with static method
 b) setup with etcd discovery and shared network with host
 c) setup with etcd discovery and shared network without host
4. Etcd server can be access with https
5. Test etcd with kubernetes and flanneld
6. Etcd container running in atomic host.

They are all passed. So set this to verified.

Comment 7 errata-xmlrpc 2018-05-14 17:14:28 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-2018:1440