-
Bug
-
Resolution: Done
-
Major
-
1.0.0.GA
-
None
-
OCP v.3.11 deployed to https://master.ndp-test-311.dynamic.xpaas:8443
You need to add next nameserver info into /etc/resolv.conf* file to have an access to OCP:search dynamic.xpaas nameserver 10.8.243.86
Server container: brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/codeready-workspaces/server-container:codeready-1.0-rhel-7-containers-candidate-21574-20190114221556
Operator container: brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/codeready-workspaces/operator-containerOCP v.3.11 deployed to https://master.ndp-test-311.dynamic.xpaas:8443 You need to add next nameserver info into /etc/resolv.conf * file to have an access to OCP: search dynamic.xpaas nameserver 10.8.243.86 Server container : brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/codeready-workspaces/server-container:codeready-1.0-rhel-7-containers-candidate-21574-20190114221556 Operator container : brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/codeready-workspaces/operator-container
There was error of deploying CRW on OCP :
deploy.sh log
[INFO]: Welcome to CodeReady Workspaces Installer
[INFO]: Found oc client in PATH
[INFO]: Checking if you are currently logged in...
[INFO]: Active session found. Your current context is: codeready-new/master-ndp-test-311-dynamic-xpaas:8443/admin
[WARNING]: Namespace 'codeready-new' not found, or current user does not have access to it. Installer will try to create namespace 'codeready-new'
[INFO]: Creating namespace "codeready-new"
[INFO]: Namespace "codeready-new" successfully created
[INFO]: Creating installer service account
serviceaccount/che-operator created
rolebinding.rbac.authorization.k8s.io/che-operator created
configmap/che-operator created
Unable to connect to the server: dial tcp: lookup master.ndp-test-311.dynamic.xpaas on 10.38.5.26:53: no such host
Unable to use a TTY - container che-operator did not allocate one
If you don't see a command prompt, try pressing enter.
time="2019-01-14T22:43:06Z" level=info msg="postgres Successfully deployed"
time="2019-01-14T22:43:06Z" level=info msg="Waiting for pg-job job. Default timeout is 300 seconds"
time="2019-01-14T22:48:06Z" level=error msg="Failed to verify a successful pg-job job execution. Operator is exiting"
time="2019-01-14T22:48:06Z" level=error msg="Check job logs: kubectl logs job/pg-job -n=%!(EXTRA string=codeready-new)"
time="2019-01-14T22:48:06Z" level=error msg="Get k8s events: kubectl get events --field-selector involvedObject.name=$(kubectl get pods -l=app=pg-job -n=codeready-new-o=jsonpath='{.items[0].metadata.name}') -n=%!(EXTRA string=codeready-new)"
panic: nil
goroutine 1 [running]:
github.com/eclipse/che-operator/pkg/util.GetJobStatus(0xc420098400)
/go/src/github.com/eclipse/che-operator/pkg/util/util.go:206 +0xa5f
github.com/eclipse/che-operator/pkg/operator.CreatePgJob()
/go/src/github.com/eclipse/che-operator/pkg/operator/deployment_postgres.go:196 +0x61
github.com/eclipse/che-operator/pkg/operator.ReconsileChe()
/go/src/github.com/eclipse/che-operator/pkg/operator/reconsile.go:43 +0xa89
main.main()
/go/src/github.com/eclipse/che-operator/cmd/che-operator/main.go:50 +0x25
pod codeready-new/che-operator terminated (Error)
[ERROR]: Failed to deploy CodeReady Workspaces. Inspect error log.
There was warning in postgres pod event:
postrgres container events
11:42:56 PM Warning Unhealthy Readiness probe failed: sh: cannot set terminal process group (-1): Inappropriate ioctl for device sh: no job control in this shell psql: could not connect to server: Connection refused Is the server running on host "127.0.0.1" and accepting TCP/IP connections on port 5432? 11:42:41 PM Normal Started Started container 11:42:41 PM Normal Created Created container 11:42:36 PM Normal Pulled Container image "registry.access.redhat.com/rhscl/postgresql-96-rhel7:1-25" already present on machine 11:42:30 PM Normal Scheduled Successfully assigned codeready-new/postgres-56c6bb5699-8rs6t to node1.ndp-test-311.dynamic.xpaas
postgres pod log
he files belonging to this database system will be owned by user "postgres".
This user must also own the server process.
The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".
Data page checksums are disabled.
fixing permissions on existing directory /var/lib/pgsql/data/userdata ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok
Success. You can now start the database server using:
WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
pg_ctl -D /var/lib/pgsql/data/userdata -l logfile start
waiting for server to start....LOG: redirecting log output to logging collector process
HINT: Future log output will appear in directory "pg_log".
done
server started
=> sourcing /usr/share/container-scripts/postgresql/start/set_passwords.sh ...
ALTER ROLE
ALTER ROLE
waiting for server to shut down.... done
server stopped
Starting server...
LOG: redirecting log output to logging collector process
HINT: Future log output will appear in directory "pg_log".