#7242 Build blocking deploy of silverblue website
Closed: Fixed 5 years ago Opened 5 years ago by misc.

  • Describe what you need us to do:

someone with enough access to run:
oc cancel-build silverblue-build-6
in the silverblue project.

  • When do you need this? (YYYY/MM/DD)
    ASAP. I would have done myself if the openshift wasn't fully locked, permitting to create as much build as possible, but not cancelling them.

  • When is this no longer needed or useful? (YYYY/MM/DD)
    Around the heat death of the universe

  • If we cannot complete your request, what is the impact?
    Our website will be locked forever


Looks like someone else canceled it or it finally timed out:

Status: Error (The pod for this build was deleted before the build completed.)
Started: Thu, 13 Sep 2018 03:29:08 UTC
Duration: 11h18m39s

build-7 is running.

:city_sunset:

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

5 years ago

Metadata Update from @misc:
- Issue status updated to: Open (was: Closed)

5 years ago

Now the following build is causing trouble. ( -7 )

And I can't debug the build.

And it work find in staging without any trouble, starting a build do deploy the container so fast that I do not have time to find my terminal to watch the log.

This seems to have been caused by a broken/not working docker daemon on os-node02.

After restarting things are back to normal. Note that we use cri-o for as much as possible, hopefully openshift will get to the point when it uses buildah and cri-o entirely.

:file_folder:

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

5 years ago

Login to comment on this ticket.

Metadata