#7504 Staging OpenShift seems to have a disk space issue
Closed: Fixed 6 months ago by kevin. Opened 6 months ago by bowlofeggs.

  • Describe what you need us to do:
    At the end of a Bodhi container Build in OpenShift, I saw this message:
<snip>
  python3-bodhi-client-3.13.0-0.0.beta.e0ca5bc.fc29.infra.noarch                

Complete!
Removing intermediate container 54e28dafe221
error: build error: devmapper: Thin Pool has 11165 free data blocks which is less than minimum required 11944 free data blocks. Create more free space in thin pool or use dm.min_free_space option to change behavior

It seems that it was not able to store the resulting container.

Do we have monitoring on this storage? If not, it might be good to add.

  • When do you need this? (YYYY/MM/DD)
    Ideally, this week (2019-01-18).

  • When is this no longer needed or useful? (YYYY/MM/DD)
    If staging OpenShift builds start working again, or if we stop using OpenShift, or if we stop using Bodhi.

  • If we cannot complete your request, what is the impact?
    I cannot test a Bodhi 3.13 beta on staging.


I have the same issue with release-monitoring.org on staging openshift.

error: build error: devmapper: Thin Pool has 11004 free data blocks which is less than minimum required 11944 free data blocks. Create more free space in thin pool or use dm.min_free_space option to change behavior

Other the week end I configured in stg a shared volume of type emptyDir for mdapi to store the sqlite meta data database.

I am not sure if this is related or not but I though it was worth mentioning.

PS : This volume does not need to be persistent since we pull the sqlite files from dl.fp.o

ok, I think I have fixed this... can you all confirm?

:passport_control:

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

6 months ago

It's working for me. :-)

I was able to get Bodhi 3.13.0b0 deployed to staging, thanks!

Login to comment on this ticket.

Metadata