Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • D drupalSite-operator
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • drupal
  • paas
  • drupalSite-operator
  • Merge requests
  • !138

Open
Created Nov 28, 2021 by Konstantinos Samaras-Tsakiris@kosamaraOwner
  • Report abuse
Report abuse

Draft: Fix install job creation

  • Overview 10
  • Commits 4
  • Pipelines 5
  • Changes 4

After changing the install job name in !137 (merged) , I noticed that the new install job was being created for already-installed sites. This is dangerous!

  • Added a check on the Initialized condition before ensuring the install job.
  • Fixed the Initialized condition. It used to be set to false even if the operator simply failed to exec into the pod, which is unintended. Instead, it should be Unknown.
Edited Nov 30, 2021 by Konstantinos Samaras-Tsakiris
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: fix-install-job