#6913 Staging OpenShift seems to deny and not-deny the Bodhi deployment
Closed: Fixed 5 years ago Opened 5 years ago by bowlofeggs.

  • Describe what you need us to do:
    I've been unable to deploy my new Bodhi to staging this morning. There are a few odd things I've noticed:

    • Bodhi's staging-sync playbook fails to stop Bodhi on OS. It runs oc scale dc/bodhi-web --replicas=0 and gets the error Error from server (NotFound): deploymentconfigs.apps.openshift.io "bodhi-web" not found.
    • The above prompted me to have a look at the web interface. When I visited it, it told me "The project bodhi does not exist or you are not authorized to view it."
    • Strangely, oc get dc does seem to show the bodhi-web that oc scale says is not found:
$ oc get dc
NAME        REVISION   DESIRED   CURRENT   TRIGGERED BY
bodhi-web   5          2         2         config,image(bodhi-web:latest)
  • When do you need this? (YYYY/MM/DD)
    ASAP.

  • When is this no longer needed or useful? (YYYY/MM/DD)
    It will be useful as long as we are using OpenShift.

  • If we cannot complete your request, what is the impact?
    I cannot test the Bodhi beta in staging, which will block me from releasing it to production, which will block us from fixing test gating usability issues.


Metadata Update from @bowlofeggs:
- Issue tagged with: OpenShift, bodhi

5 years ago

Patrick fixed this up for me. Thanks!

Metadata Update from @bowlofeggs:
- Issue assigned to puiterwijk
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

5 years ago

For the record: the scale issue was because there was a -n bodhi missing to select the openshift project.
The web interface was because of more permissions getting namespaced where appowner needed updating.

Login to comment on this ticket.

Metadata