Bug 1726842 - Silverblue install fails in Fedora-Rawhide-20190703.n.0 with "Failed to pull from repository: ... regfile copy: Input/output error (0)"
Summary: Silverblue install fails in Fedora-Rawhide-20190703.n.0 with "Failed to pull ...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: pungi
Version: rawhide
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Lubomír Sedlář
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: openqa
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-03 20:40 UTC by Adam Williamson
Modified: 2019-07-08 17:29 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-08 17:29:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2019-07-03 20:40:30 UTC
In Fedora-Rawhide-21090703.n.0, the Silverblue install tests all started failing during the install process. (There have previously been failures on the same tests in the last few days due to gnome-initial-setup not working properly for some reason, but the install process itself had been working for some time). The error occurs during the 'Writing objects' phase of the install process, and looks like this:

https://openqa.fedoraproject.org/tests/418118#step/_do_install_and_reboot/46

"Failed to pull from repository: g-io-error-quark: Importing 834336861b4da3861dc18debc1e1635b68e729a0253514693cd839eb069 regfile copy: Input/output error (0)"

This seems fully reproducible - I reran the tests on prod and they failed again, and the same tests failed on staging. I checked the checksum of the image tested, and it's correct.

I'm assigning this to pungi because it's the most likely-to-be-related package that changed in the 20190703.n.0 compose - it went from 4.1.37-1 to 4.1.38-1, with a bunch of changes:

  - Remove remaining mentions of runroot option (lsedlar)
  - pkgset: Include module metadata in the repos (lsedlar)
  - config: Deprecate runroot option (hlin)
  - Respect --nomacboot flag when calling isohybrid (dnevil)
  - config: Keep known options defined on CLI (lsedlar)
  - config-dump: Report better error for non-existing sources (lsedlar)
  - config: Improve config validation for anyOf and oneOf (lsedlar)
  - config-validate: Allow defining variables (lsedlar)
  - config: Report validation warning if variants fail to load (lsedlar)
  - Allow customizing nosetests command (lsedlar)
  - scm: Close stdin of processing command (lsedlar)
  - pkgset: Create arch repos in parallel (lsedlar)
  - util: Resolve HEAD in repos that have a remote (lsedlar)
  - tests: Avoid using threads in tests (lsedlar)
  - pkgset: Use highest pickle protocol (lsedlar)
  - gather: fix crash issue when gather_method = "nodeps" (hlin)
  - pkgset: Check for unused module patterns across all tags (lsedlar)
  - util: Fix offline resolving for scm dict (lsedlar)
  - pkgset: Make serialization more resilient (lsedlar)
  - fus: Support HTTP repos (lsedlar)
  - config: Deprecate release_is_layered option (hlin)
  - pkgset: Set correct nsvc for devel modules (lsedlar)
  - Remove unused variable (lsedlar)
  - Whitespace fixes (lsedlar)
  - Whitespace cleanup (lsedlar)
  - Remove unused variables (lsedlar)
  - Remove unused imports (lsedlar)

not sure which is most likely to be the culprit (or if it actually will turn out to be something else entirely).

Comment 1 Lubomír Sedlář 2019-07-08 09:51:26 UTC
Pungi version did not change. There is an update, true, but checking logs from past composes it does not seem to be deployed yet.

All of these were done with pungi-4.1.36-5.fc30.noarch:
Fedora-Rawhide-20190707.n.0
Fedora-Rawhide-20190704.n.1
Fedora-Rawhide-20190703.n.0
Fedora-Rawhide-20190701.n.0

It would be good if someone familiar with ostree repo structure could verify if the files there are correct.

Comment 2 Adam Williamson 2019-07-08 17:29:17 UTC
Ah, hm, good point. In 20190707.n.0 the installs succeeded anyhow, so perhaps this was some weird compose blip? Let's call it a CANTFIX.


Note You need to log in before you can comment on or make changes to this bug.