| Summary: | [Dedicated]Template mysql-ephemeral/persistent template should be bumped into ded-stage-aws from origin | ||
|---|---|---|---|
| Product: | OpenShift Online | Reporter: | Wenjing Zheng <wzheng> |
| Component: | Website | Assignee: | Dan Mace <dmace> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Yanping Zhang <yanpzhan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.x | CC: | abhgupta, aos-bugs, dmace, jokerman, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-23 15:10:18 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: | |
|
Description
Wenjing Zheng
2016-04-01 09:30:18 UTC
There's a quoting issue in the readiness checks for the mysql-* templates which was fixed in https://github.com/openshift/openshift-ansible/commit/de133ff75c912c588dc05ac8b9f9b6a6d29a9f99. Ops has deployed the fix to ded-stage-aws and the template now seems to work well. Pod keeps in ContainerCreating in ded-stage-aws for cannot find volume, this seems an env issue:
Events:
FirstSeen LastSeen Count From SubobjectPath Type Reason Message
--------- -------- ----- ---- ------------- -------- ------ -------
28s 28s 1 {default-scheduler } Normal Scheduled Successfully assigned mysql-1-vi57b to ip-172-31-2-204.ec2.internal
<invalid> <invalid> 2 {kubelet ip-172-31-2-204.ec2.internal} Warning FailedMount Unable to mount volumes for pod "mysql-1-vi57b_wzheng1(5bf9a1b2-fbde-11e5-89b5-0eb4d24322f9)": Could not attach EBS Disk "aws://us-east-1c/vol-a598950c": Error attaching EBS volume: InvalidVolume.NotFound: The volume 'vol-a598950c' does not exist.
status code: 400, request id:
<invalid> <invalid> 2 {kubelet ip-172-31-2-204.ec2.internal} Warning FailedSync Error syncing pod, skipping: Could not attach EBS Disk "aws://us-east-1c/vol-a598950c": Error attaching EBS volume: InvalidVolume.NotFound: The volume 'vol-a598950c' does not exist.
status code: 400, request id:
(In reply to Wenjing Zheng from comment #2) > Pod keeps in ContainerCreating in ded-stage-aws for cannot find volume, this > seems an env issue: > Events: > FirstSeen LastSeen Count From SubobjectPath Type Reason Message > --------- -------- ----- ---- ------------- -------- ------ ------- > 28s 28s 1 {default-scheduler } Normal Scheduled Successfully > assigned mysql-1-vi57b to ip-172-31-2-204.ec2.internal > <invalid> <invalid> 2 {kubelet ip-172-31-2-204.ec2.internal} Warning > FailedMount Unable to mount volumes for pod > "mysql-1-vi57b_wzheng1(5bf9a1b2-fbde-11e5-89b5-0eb4d24322f9)": Could not > attach EBS Disk "aws://us-east-1c/vol-a598950c": Error attaching EBS volume: > InvalidVolume.NotFound: The volume 'vol-a598950c' does not exist. > status code: 400, request id: > <invalid> <invalid> 2 {kubelet ip-172-31-2-204.ec2.internal} Warning > FailedSync Error syncing pod, skipping: Could not attach EBS Disk > "aws://us-east-1c/vol-a598950c": Error attaching EBS volume: > InvalidVolume.NotFound: The volume 'vol-a598950c' does not exist. > status code: 400, request id: This is a different error than the reported bug which was a general readiness check failure affecting both the mysql-ephemeral and myst-persistent templates. I split off the new error into https://bugzilla.redhat.com/show_bug.cgi?id=1324492. Please verify the fix for the reported bug, and let's track the new error (which is specific to mysql-persistent) in the new report. Thanks! Verified with latest ded-stage-aws, no such issue now. |