• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

zalando-incubator / postgres-operator
11%
master: 24%

Build:
Build:
LAST BUILD BRANCH: set-human-role-var
DEFAULT BRANCH: master
Repo Added 08 Jun 2017 10:56AM CUT
Files 8
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH fix_for_clusters_restored_from_s3
branch: fix_for_clusters_restored_from_s3
CHANGE BRANCH
x
Reset
  • fix_for_clusters_restored_from_s3
  • add-clone-example
  • add-slides
  • api-improvements
  • api-queue-size
  • bugfix/avoid_recreating_empty_master_pod
  • bugfix/close_db_connections
  • bugfix/connection_leak_and_sync_role_options
  • bugfix/fail_to_create_kubernetes_objects_on_sync
  • bugfix/nil_db_connection
  • bugfix/pam_role_name
  • bugfix/replica_service_selector
  • cdp-test
  • cdp/improvements
  • cfg-pod-terminate-grace-period
  • clean-cluster-queue
  • client-go
  • client-go-v4
  • compare-container-names
  • constants-refactor
  • container-name
  • correctly-select-deployed-ns
  • crd
  • create-databases
  • custom-env
  • custom-env-improved
  • custom-resource-definition
  • database-name-fix
  • databases-rest-endpoint
  • dcs-enable-kubernetes-api
  • default-to-watched-ns
  • default_empty_readiness_label
  • diagnostic-api
  • docs/endpoints
  • docs/endpoints-1
  • document-watch-namespace
  • feature/add-unit-tests-build-step
  • feature/configure_replication_role
  • feature/demospilo
  • feature/diagnostic-rest-api
  • feature/dynamic-client
  • feature/fork_clusters
  • feature/interfaces
  • feature/k8s-api
  • feature/lint-fixes
  • feature/refactor-tpr
  • feature/remove-pod-dispatcher
  • feature/restrict_lb_by_default
  • feature/retry_util_tests
  • feature/tests
  • feature/unit-tests-doc
  • feature/unit_tests
  • feature/validate_role_options
  • fix-cluster-delete
  • fix-labels
  • fix-loadbalancer-config
  • fix-pdb-comparison
  • fix-sync-non-existing-statefulset
  • fix/alter-user
  • fix/cluster-event-queue
  • fix/clusterevent-queue
  • fix/graceful-shutdown
  • fix/logger
  • fix/object-deletion
  • fix/queue-consumption
  • fix/skip-empty-config-params
  • fix_env_name
  • fix_not_opening_db_connection
  • fix_pdb_sync
  • fix_pg_retry
  • fix_pod_waits
  • global-min-max-replicas
  • go19
  • improve_behavior_on_node_decomissionining
  • improve_infrastructure_role_definitions
  • inline-custom-variables
  • kube-cluster-upgrade
  • kubernetes-client-v4
  • link-patroni
  • log-method-normalize
  • make-role-public
  • manual-failover-fix
  • master
  • merge_infrastructre_robot_roles
  • migrate_master_without_replicas
  • monitoring-api
  • more-logging
  • move-config
  • no_sync_failure_on_cluster_without_master
  • normalize-log-messages
  • operator_rbac
  • patroni
  • pdb-master-label
  • per-cluster-docker-image
  • pg-retry
  • pick_master_canddidate_on_live_node
  • protected_roles
  • readme-1
  • readme-bump
  • readme-stackenblocken
  • resource-update
  • rolling-upgrade
  • run-local
  • run_on_hosts_with_readiness_label
  • scale-down
  • scalyr-agent-sidecar
  • scalyr-api-key
  • scalyr-pod-name
  • secret-name-template
  • set-status-running
  • set_user_options
  • static-check-fix
  • support-many-namespaces
  • sync
  • sync_databases
  • toggle-superuser
  • travis_ci
  • update-readme-api-1
  • update-readme-status
  • update_documentation
  • wal_bucket_uid_suffix
  • warn-empty-secrets
  • watch_multiple_namespaces
  • worker-assignment
  • zerg-junior-patch-1

pending completion
740

push

travis-ci

alexeyklyukin
Fixes for the case of re-creating the cluster after deletion.

- make sure that the secrets for the system users (superuser, replication)
  are not deleted when the main cluster is. Therefore, we can re-create
  the cluster, potentially forcing Patroni to restore it from the backup
  and enable Patroni to connect, since it will use the old password, not
  the newly generated random one.

- when syncing users, always check whether they are already in the DB.
  Previously, we did this only for the sync cluster case, but the new
  cluster could be actually the one restored from the backup by Patroni,
  having all or some of the users already in place.

 - delete endponts last. Patroni uses the $clustername endpoint in order
   to store the leader related metadata. If we remove it before removing
   all pods, one of those pods running Patroni will re-create it and the
   next attempt to create the cluster with the same name will stuble on
   the existing endpoint.

 - Use db.Exec instead of db.Query for queries that expect no result.
   This also fixes the issue with the DB creation, since we didn't
   release an empty Row object it was not possible to create more than
   one database for a cluster.

33 of 33 new or added lines in 5 files covered. (100.0%)

543 of 4769 relevant lines covered (11.39%)

0.62 hits per line

Relevant lines Covered
Build:
Build:
4769 RELEVANT LINES 543 COVERED LINES
0.62 HITS PER LINE
Source Files on fix_for_clusters_restored_from_s3
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Loading...
Coverage∆FileLinesRelevantCoveredMissedHits/Line
No data available in table
Showing 0 to 0 of 0 entries
  • Previous
  • Next

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
740 fix_for_clusters_restored_from_s3 Fixes for the case of re-creating the cluster after deletion. - make sure that the secrets for the system users (superuser, replication) are not deleted when the main cluster is. Therefore, we can re-create the cluster, potentially forcing Pa... push 13 Dec 2017 02:37PM CUT alexeyklyukin travis-ci pending completion  
See All Builds (1274)
  • Repo on GitHub
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc