-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Ready for review] Fixed e2e tests #964
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -128,6 +128,9 @@ function scrutinizeForAdmintools() { | |
OP_FILE="$ns.$v.scrutinize.tar" | ||
logInfo "Running scrutinize" | ||
set -o xtrace | ||
# scrutinize needs to be able to ssh to the pod | ||
POD_IP=$(kubectl get pod -n $ns $pod -o jsonpath='{.status.podIP}') | ||
kubectl exec -t -n $ns $pod -- bash -c "ssh-keyscan $POD_IP >> ~/.ssh/known_hosts" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why do we need this now? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Scrutinize still has a bug. See my comment under this Jira: https://jira.verticacorp.com/jira/browse/VER-96447. This is a workaround before client team fixed the scrutinize. |
||
# We only need 1 pod because scrutinize will collect for the entire VerticaDB | ||
kubectl exec -t -n $ns $pod -- /opt/vertica/bin/scrutinize --output_dir $POD_OP_DIR --output_file $OP_FILE --vsql-off | ||
scrut_res=$? | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
# (c) Copyright [2021-2024] Open Text. | ||
# Licensed under the Apache License, Version 2.0 (the "License"); | ||
# You may not use this file except in compliance with the License. | ||
# You may obtain a copy of the License at | ||
# | ||
# http://www.apache.org/licenses/LICENSE-2.0 | ||
# | ||
# Unless required by applicable law or agreed to in writing, software | ||
# distributed under the License is distributed on an "AS IS" BASIS, | ||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
# See the License for the specific language governing permissions and | ||
# limitations under the License. | ||
|
||
apiVersion: kuttl.dev/v1beta1 | ||
kind: TestStep | ||
commands: | ||
# Copy vdb-gen into the container. We run it in the container so that it has | ||
# access to k8s network. Running it outside k8s, it would only have access to | ||
# what is exposed. | ||
- command: kubectl -n $NAMESPACE cp ../../../bin/vdb-gen v-vdb-gen-revive-sc1-0:/tmp/vdb-gen | ||
- command: kubectl -n $NAMESPACE exec v-vdb-gen-revive-sc1-0 -- chmod +x /tmp/vdb-gen | ||
- command: kubectl -n $NAMESPACE cp run-vdb-gen.sh v-vdb-gen-revive-sc1-0:/tmp/run-vdb-gen.sh | ||
- command: kubectl -n $NAMESPACE exec v-vdb-gen-revive-sc1-0 -- chmod +x /tmp/run-vdb-gen.sh | ||
- script: sh -c "kubectl -n $NAMESPACE exec v-vdb-gen-revive-sc1-0 -- sh -c \"/tmp/run-vdb-gen.sh $NAMESPACE $(cd ../../.. && make echo-images | grep ^VERTICA_IMG= | cut -d'=' -f2) v-vdb-gen-revive2 v-vdb-gen-revive-ca-cert ${VERTICA_DEPLOYMENT_METHOD:-admintools} ${VERTICA_SUPERUSER_NAME:-dbadmin} v-vdb-gen-revive-sc2-0 v-vdb-gen-revive\" > /tmp/$NAMESPACE-vdb-gen.yaml" | ||
- command: cat /tmp/$NAMESPACE-vdb-gen.yaml | ||
# Remove the old vdb | ||
- command: kubectl -n $NAMESPACE delete vdb v-vdb-gen-revive |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
# (c) Copyright [2021-2024] Open Text. | ||
# Licensed under the Apache License, Version 2.0 (the "License"); | ||
# You may not use this file except in compliance with the License. | ||
# You may obtain a copy of the License at | ||
# | ||
# http://www.apache.org/licenses/LICENSE-2.0 | ||
# | ||
# Unless required by applicable law or agreed to in writing, software | ||
# distributed under the License is distributed on an "AS IS" BASIS, | ||
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
# See the License for the specific language governing permissions and | ||
# limitations under the License. | ||
|
||
apiVersion: kuttl.dev/v1beta1 | ||
kind: TestStep | ||
commands: | ||
# Apply the generated CR | ||
- command: kubectl -n $NAMESPACE apply -f /tmp/$NAMESPACE-vdb-gen.yaml | ||
- command: rm /tmp/$NAMESPACE-vdb-gen.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the difference between the sha-legacy and the latest-legacy-master image?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sha-legacy image will be built by e2e tests, and latest-legacy-master is built by devops and already exists before e2e tests run.