Log: /mnt/jenkins/workspace/cloud-psmdb-operator_PR-1352/e2e-tests/logs/security-context.log
-----------------------------------------------------------------------------------
get and delete old CRDs and RBAC
-----------------------------------------------------------------------------------
error: the server doesn't have a resource type "perconaservermongodbbackups"
+ kubectl patch perconaservermongodbbackups.psmdb.percona.com -n sh --type=merge -p '{"metadata":{"finalizers":[]}}'
error: the server doesn't have a resource type "perconaservermongodbbackups"
error: the server doesn't have a resource type "perconaservermongodbrestores"
+ kubectl patch perconaservermongodbrestores.psmdb.percona.com -n sh --type=merge -p '{"metadata":{"finalizers":[]}}'
error: the server doesn't have a resource type "perconaservermongodbrestores"
error: the server doesn't have a resource type "perconaservermongodbs"
+ kubectl patch perconaservermongodbs.psmdb.percona.com -n sh --type=merge -p '{"metadata":{"finalizers":[]}}'
error: the server doesn't have a resource type "perconaservermongodbs"
Error from server (NotFound): customresourcedefinitions.apiextensions.k8s.io "null" not found
Error from server (NotFound): customresourcedefinitions.apiextensions.k8s.io "null" not found
Error from server (NotFound): customresourcedefinitions.apiextensions.k8s.io "null" not found
Error from server (NotFound): customresourcedefinitions.apiextensions.k8s.io "null" not found
-----------------------------------------------------------------------------------
destroy chaos-mesh
-----------------------------------------------------------------------------------
error: resource(s) were provided, but no name was specified
error: resource(s) were provided, but no name was specified
error: resource(s) were provided, but no name was specified
error: resource(s) were provided, but no name was specified
error: resource(s) were provided, but no name was specified
error: resource(s) were provided, but no name was specified
-----------------------------------------------------------------------------------
cleaned up all old namespaces
-----------------------------------------------------------------------------------
-----------------------------------------------------------------------------------
cleaned up old namespaces security-context-21069
-----------------------------------------------------------------------------------
error: resource(s) were provided, but no name was specified
-----------------------------------------------------------------------------------
create namespace security-context-21069
-----------------------------------------------------------------------------------
namespace/security-context-21069 created
Context "gke_cloud-dev-112233_us-central1-a_jen-psmdb-1352-9793733e-5-cluster8" modified.
-----------------------------------------------------------------------------------
start PSMDB operator
-----------------------------------------------------------------------------------
customresourcedefinition.apiextensions.k8s.io/perconaservermongodbbackups.psmdb.percona.com serverside-applied
customresourcedefinition.apiextensions.k8s.io/perconaservermongodbrestores.psmdb.percona.com serverside-applied
customresourcedefinition.apiextensions.k8s.io/perconaservermongodbs.psmdb.percona.com serverside-applied
role.rbac.authorization.k8s.io/percona-server-mongodb-operator created
serviceaccount/percona-server-mongodb-operator created
rolebinding.rbac.authorization.k8s.io/service-account-percona-server-mongodb-operator created
deployment.apps/percona-server-mongodb-operator created
waiting for pod/percona-server-mongodb-operator-6b6bcb669-kmdgx to be ready.OK
-----------------------------------------------------------------------------------
create secrets and start client
-----------------------------------------------------------------------------------
secret/some-users created
deployment.apps/psmdb-client created
secret/minio-secret created
-----------------------------------------------------------------------------------
create additional service account
-----------------------------------------------------------------------------------
serviceaccount/percona-server-mongodb-operator-workload created
-----------------------------------------------------------------------------------
create first PSMDB cluster sec-context
-----------------------------------------------------------------------------------
-----------------------------------------------------------------------------------
create first PSMDB cluster
-----------------------------------------------------------------------------------
perconaservermongodb.psmdb.percona.com/sec-context created
-----------------------------------------------------------------------------------
check if Pod is started
-----------------------------------------------------------------------------------
waiting for pod/sec-context-rs0-0 to be ready......OK
waiting for pod/sec-context-rs0-1 to be ready.......OK
waiting for pod/sec-context-rs0-2 to be ready......OK
Waiting for cluster readyness
-----------------------------------------------------------------------------------
write data
-----------------------------------------------------------------------------------
Percona Server for MongoDB shell version v4.4.24-23
connecting to: mongodb://sec-context-rs0-0.sec-context-rs0.security-context-21069.svc.cluster.local:27017,sec-context-rs0-1.sec-context-rs0.security-context-21069.svc.cluster.local:27017,sec-context-rs0-2.sec-context-rs0.security-context-21069.svc.cluster.local:27017/admin?compressors=disabled&gssapiServiceName=mongodb&replicaSet=rs0&ssl=false
Implicit session: session { "id" : UUID("c20bcc19-c671-4b88-a631-19dc4aa19cde") }
Percona Server for MongoDB server version: v5.0.20-17
WARNING: shell and server versions do not match
Successfully added user: {
"user" : "myApp",
"roles" : [
{
"db" : "myApp",
"role" : "readWrite"
}
]
}
bye
Percona Server for MongoDB shell version v4.4.24-23
connecting to: mongodb://sec-context-rs0-1.sec-context-rs0.security-context-21069.svc.cluster.local:27017,sec-context-rs0-2.sec-context-rs0.security-context-21069.svc.cluster.local:27017,sec-context-rs0-0.sec-context-rs0.security-context-21069.svc.cluster.local:27017/admin?compressors=disabled&gssapiServiceName=mongodb&replicaSet=rs0&ssl=false
Implicit session: session { "id" : UUID("d40aabd0-d19c-433f-94ab-ab2a63eb5a6f") }
Percona Server for MongoDB server version: v5.0.20-17
WARNING: shell and server versions do not match
switched to db myApp
WriteResult({ "nInserted" : 1 })
bye
-----------------------------------------------------------------------------------
check if statefulset created with expected config
-----------------------------------------------------------------------------------
-----------------------------------------------------------------------------------
install Minio
-----------------------------------------------------------------------------------
Error: uninstall: Release not loaded: minio-service: release: not found
"minio" has been removed from your repositories
"minio" has been added to your repositories
NAME: minio-service
LAST DEPLOYED: Thu Oct 5 15:21:49 2023
NAMESPACE: security-context-21069
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
Minio can be accessed via port 9000 on the following DNS name from within your cluster:
minio-service.security-context-21069.svc.cluster.local
To access Minio from localhost, run the below commands:
1. export POD_NAME=$(kubectl get pods --namespace security-context-21069 -l "release=minio-service" -o jsonpath="{.items[0].metadata.name}")
2. kubectl port-forward $POD_NAME 9000 --namespace security-context-21069
Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/kubectl_port-forward/
You can now access Minio server on http://localhost:9000. Follow the below steps to connect to Minio server with mc client:
1. Download the Minio mc client - https://docs.minio.io/docs/minio-client-quickstart-guide
2. Get the ACCESS_KEY=$(kubectl get secret minio-service -o jsonpath="{.data.accesskey}" | base64 --decode) and the SECRET_KEY=$(kubectl get secret minio-service -o jsonpath="{.data.secretkey}" | base64 --decode)
3. mc alias set minio-service-local http://localhost:9000 "$ACCESS_KEY" "$SECRET_KEY" --api s3v4
4. mc ls minio-service-local
Alternately, you can use your browser or the Minio SDK to access the server - https://docs.minio.io/categories/17
waiting for pod/minio-service-5fc4dc898-wr7xs to be ready.....OK
pod "aws-cli" deleted
If you don't see a command prompt, try pressing enter.
-----------------------------------------------------------------------------------
change security context
-----------------------------------------------------------------------------------
perconaservermongodb.psmdb.percona.com/sec-context configured
waiting for pod/sec-context-rs0-0 to be ready.OK
waiting for pod/sec-context-rs0-1 to be ready.OK
waiting for pod/sec-context-rs0-2 to be ready..OK
Waiting for cluster readyness...............
-----------------------------------------------------------------------------------
check if statefulset created with expected config
-----------------------------------------------------------------------------------
-----------------------------------------------------------------------------------
destroy cluster/operator and all other resources
-----------------------------------------------------------------------------------
-----------------------------------------------------------------------------------
get and delete old CRDs and RBAC
-----------------------------------------------------------------------------------
customresourcedefinition.apiextensions.k8s.io "perconaservermongodbbackups.psmdb.percona.com" deleted
customresourcedefinition.apiextensions.k8s.io "perconaservermongodbrestores.psmdb.percona.com" deleted
customresourcedefinition.apiextensions.k8s.io "perconaservermongodbs.psmdb.percona.com" deleted
error: the server doesn't have a resource type "perconaservermongodbbackups"
+ kubectl patch perconaservermongodbbackups.psmdb.percona.com -n sh --type=merge -p '{"metadata":{"finalizers":[]}}'
error: the server doesn't have a resource type "perconaservermongodbbackups"
error: the server doesn't have a resource type "perconaservermongodbrestores"
+ kubectl patch perconaservermongodbrestores.psmdb.percona.com -n sh --type=merge -p '{"metadata":{"finalizers":[]}}'
error: the server doesn't have a resource type "perconaservermongodbrestores"
error: the server doesn't have a resource type "perconaservermongodbs"
+ kubectl patch perconaservermongodbs.psmdb.percona.com -n sh --type=merge -p '{"metadata":{"finalizers":[]}}'
error: the server doesn't have a resource type "perconaservermongodbs"
role.rbac.authorization.k8s.io "percona-server-mongodb-operator" deleted
serviceaccount "percona-server-mongodb-operator" deleted
rolebinding.rbac.authorization.k8s.io "service-account-percona-server-mongodb-operator" deleted
-----------------------------------------------------------------------------------
test passed
-----------------------------------------------------------------------------------