Here it follows additional log info from pod:

--> Scaling postgresql-2 to 1
--> Waiting up to 10m0s for pods in deployment postgresql-2 to become ready
W0327 19:58:46.367143       1 reflector.go:330] github.com/openshift/origin/pkg/deploy/strategy/support/lifecycle.go:468: watch of *api.Pod ended with: too old resource version: 1047728707 (1047752717)
error: update acceptor rejected postgresql-2: pods for deployment "postgresql-2" took longer than 600 seconds to become ready

Can you check if the postgresql-2 deployment created a pod and can you check the logs from that pod? To make sure postgresql is not stuck initializing.

Created attachment 1267320 [details]
trying to create a pod for more than a hour

Created attachment 1267322 [details]
no pod log available information

I´m currently on 6th postgresql deployment with no success. It´s being difficult to scale up a pod and due to this there is no log available. I´m sending some print screen as evidences coz I haven´t got many info on Console.

Thanks! I'm going to ask the Online team to investigate if there are any capacity issues. Also, do you have any other deployments that are failing in similar way?

I can see the pod is in "pending" state, can you please check the "events" for that pod and see why it is pending?

here it goes:


1:56:29 PM	Warning	Failed mount 	Failed to attach volume "pvc-0b930f1d-1303-11e7-b5d1-0ebeb1070c7f" on node "ip-172-31-2-63.ec2.internal" with: Timeout waiting for volume state: actual=detached, desired=attached



1:24:24 PM	Warning	Failed mount 	Failed to attach volume "pvc-0b930f1d-1303-11e7-b5d1-0ebeb1070c7f" on node "ip-172-31-2-63.ec2.internal" with: Error attaching EBS volume: VolumeInUse: vol-0399f530d8c354c39 is already attached to an instance status code: 400, request id:
63 times in the last 2 hours

I removed all postgresql configuration and installed once again, but the problem persists. Here it follows the last log deployment :


--> Scaling postgresql-1 to 1
--> Waiting up to 10m0s for pods in deployment postgresql-1 to become ready
W0329 23:56:48.276495       1 reflector.go:330] github.com/openshift/origin/pkg/deploy/strategy/support/lifecycle.go:468: watch of *api.Pod ended with: too old resource version: 1056886168 (1056911807)
error: update acceptor rejected postgresql-1: pods for deployment "postgresql-1" took longer than 600 seconds to become ready

Thank you - I am working with our team to get relevant logs and see what happened.

I´m sending another print screen from Kibana. I don´t know exactly what is, but the elasticsearch plugin is unavailable. There is a link on Deployment log screen pointed to Kibana status screen. I believe worth a look.

Created attachment 1267611 [details]
kibana screen

I found another log info:

--> Scaling postgresql-5 to 1
--> Waiting up to 10m0s for pods in deployment postgresql-5 to become ready
W0331 11:07:34.314016       1 reflector.go:330] github.com/openshift/origin/pkg/deploy/strategy/support/lifecycle.go:468: watch of *api.Pod ended with: too old resource version: 1063095846 (1063112715)
error: update acceptor rejected postgresql-5: pods for deployment "postgresql-5" took longer than 600 seconds to become ready

We have identified the problem and we are working on deploying a fix. 

The problem stems from the fact that, some volumes in AWS were for force detached. This was done as a last resort to fix some volumes which were stuck. But the problem is - a node must be rebooted to update kernel's view of devices after force detaching a volume.

Thanks for your effort. Do you know how long will take to fix it, roughly?

*** Bug 1435424 has been marked as a duplicate of this bug. ***

We have identified some problems similar to the one reported.  Do you still have an account db2000?   We went looking for logs but couldn't find your username.

After my last post, the problem was solved and deployment service was working perfectly. But now my registration has been cancelled and I´m in a waiting list for a new access.

Cheers,

Davi