Bug 1358152
| Summary: | [infrastructure_public_41]Create a petset can't create any pet | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | DeShuai Ma <dma> |
| Component: | Node | Assignee: | Clayton Coleman <ccoleman> |
| Status: | CLOSED ERRATA | QA Contact: | DeShuai Ma <dma> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.3.0 | CC: | agoldste, aos-bugs, ccoleman, jchaloup, jokerman, mmccomas, tdawson, wmeng |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| 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: | 2016-09-27 09:41:09 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
DeShuai Ma
2016-07-20 08:03:02 UTC
Test on openshift v3.3.0.14, still same issue, high this bug. We just merged support for PetSets to origin - https://github.com/openshift/origin/pull/9972 This has been merged and is in OSE v3.3.0.17 or newer. Test on v3.3.0.17 on aws, two issue for petset now:
1) There is pvc, but event show pvc not found. like:"FailedCreate pvc: usr-vm-0, error: persistentvolumeclaims "usr-vm-0" not found"
[root@dhcp-128-7 dma]# oc describe petset vm
Name: vm
Namespace: dma1
Image(s): ubuntu:15.10
Selector: app=ub
Labels: app=ub
Replicas: 2 current / 2 desired
Annotations: <none>
CreationTimestamp: Tue, 09 Aug 2016 15:17:52 +0800
Pods Status: 0 Running / 1 Waiting / 0 Succeeded / 0 Failed
No volumes.
Events:
FirstSeen LastSeen Count From SubobjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
48s 48s 1 {petset } Warning FailedCreate pvc: usr-vm-0, error: persistentvolumeclaims "usr-vm-0" not found
48s 48s 1 {petset } Warning FailedCreate pvc: lib-vm-0, error: persistentvolumeclaims "lib-vm-0" not found
48s 48s 1 {petset } Warning FailedCreate pvc: etc-vm-0, error: persistentvolumeclaims "etc-vm-0" not found
48s 48s 1 {petset } Normal SuccessfulCreate pet: vm-0
48s 48s 1 {petset } Warning FailedCreate pvc: usr-vm-1, error: persistentvolumeclaims "usr-vm-1" not found
47s 47s 1 {petset } Warning FailedCreate pvc: lib-vm-1, error: persistentvolumeclaims "lib-vm-1" not found
47s 47s 1 {petset } Warning FailedCreate pvc: etc-vm-1, error: persistentvolumeclaims "etc-vm-1" not found
[root@dhcp-128-7 dma]# oc get pvc
NAME STATUS VOLUME CAPACITY ACCESSMODES AGE
etc-vm-0 Bound pvc-62d5dd73-5e01-11e6-9640-0e64fc40c135 0 1m
etc-vm-1 Bound pvc-62feecd8-5e01-11e6-9640-0e64fc40c135 0 1m
lib-vm-0 Bound pvc-62d23bf0-5e01-11e6-9640-0e64fc40c135 0 1m
lib-vm-1 Bound pvc-62fc6678-5e01-11e6-9640-0e64fc40c135 0 1m
usr-vm-0 Bound pvc-62ce0215-5e01-11e6-9640-0e64fc40c135 0 1m
usr-vm-1 Bound pvc-62f755b9-5e01-11e6-9640-0e64fc40c135 0 1m
2) There is bug about dynamically provisioning persistent volumes, so the petset with pv always failed.
https://bugzilla.redhat.com/show_bug.cgi?id=1365398
BZ1365398 is closed. I test petset with pv, it can works well. But now still has some persistentvolumeclaims not found event as comment5. If you think those event is normal, this bug can be verified. thanks. DeShuai, can you: 1) reproduce the same with kubernetes kubernetes v1.3.0+57fb9ac only? 2) do the same with pre-created claims? (In reply to Jan Chaloupka from comment #8) > DeShuai, can you: > > 1) reproduce the same with kubernetes kubernetes v1.3.0+57fb9ac only? > 2) do the same with pre-created claims? 1) This is the result of openshift 3.3 not kubernetes 2) not pre-created claims. All the resource create by: oc create -f https://raw.githubusercontent.com/kubernetes/kubernetes.github.io/release-1.3/docs/user-guide/petset/bootstrapping/petset_vm.yaml As petset now works fine, for the event issue will do a deep research, if still a issue will file a separate bug. Verify this bug. 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-2016:1933 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |