Skip to content

Conversation

@dustymabe
Copy link
Member

This gets us new networking improvements added in coreos/ignition-dracut#174.

@dustymabe
Copy link
Member Author

CI failed, but I don't understand why:

+ set -xeuo pipefail
+ cd /srv/fcos
+ cosa fetch --strict
info: Missing CAP_SYS_ADMIN; using virt
Formatting 'cache/cache2.qcow2', fmt=qcow2 size=10737418240 cluster_size=65536 lazy_refcounts=off refcount_bits=16
Config commit: 8bd590146d855717cb07c814b1a26439674259da
Using manifest: /srv/fcos/src/config/manifest.yaml
Running: rpm-ostree compose tree --repo=/srv/fcos/tmp/repo --cachedir=/srv/fcos/cache --touch-if-changed /srv/fcos/tmp/build/tmp/treecompose.changed --unified-core /srv/fcos/src/config/manifest.yaml --download-only --ex-lockfile=/srv/fcos/src/config/manifest-lock.x86_64.json --ex-lockfile=/srv/fcos/src/config/manifest-lock.overrides.x86_64.yaml --ex-lockfile-strict
supermin: warning: /boot/System.map-5.5.17-200.fc31.x86_64: Permission denied (ignored)
Some distro files are not public readable, so supermin cannot copy them
into the appliance.  This is a problem with your Linux distro.  Please ask
your distro to stop doing pointless security by obscurity.
You can ignore these warnings.  You *do not* need to use sudo.
supermin: warning: /boot/initramfs-5.5.17-200.fc31.x86_64.img: Permission denied (ignored)
supermin: warning: /usr/libexec/utempter/utempter: Permission denied (ignored)
supermin: warning: /usr/sbin/unix_update: Permission denied (ignored)
supermin: warning: /var/lib/systemd/random-seed: Permission denied (ignored)
tail: cannot open '/srv/fcos/tmp/runvm-cmd-output.txt' for reading: No such file or directory
tail: '/srv/fcos/tmp/runvm-cmd-output.txt' has appeared;  following new file
Loaded lockfiles:
  /srv/fcos/src/config/manifest-lock.x86_64.json
  /srv/fcos/src/config/manifest-lock.overrides.x86_64.yaml
RPM-OSTree Version: 2020.1
No previous commit for fedora/x86_64/coreos/testing-devel
Enabled rpm-md repositories: fedora-coreos-pool fedora fedora-updates fedora-modular fedora-updates-modular
Updating metadata for 'fedora-coreos-pool'...done
rpm-md repo 'fedora-coreos-pool'; generated: 2020-04-20T21:21:14Z
Updating metadata for 'fedora'...done
rpm-md repo 'fedora'; generated: 2019-10-23T22:52:47Z
Updating metadata for 'fedora-updates'...done
rpm-md repo 'fedora-updates'; generated: 2020-04-27T02:36:17Z
Updating metadata for 'fedora-modular'...done
rpm-md repo 'fedora-modular'; generated: 2019-10-23T22:53:13Z
Updating metadata for 'fedora-updates-modular'...done
rpm-md repo 'fedora-updates-modular'; generated: 2020-04-25T05:28:19Z
script returned exit code 1

@dustymabe
Copy link
Member Author

The error is error is:

Couldn't find locked package 'ignition-2.2.1-5.git2d3ff58.fc31.x86_64' (pkgs matching NEVRA: 0; mismatched checksums: 0)

This is because cosa fetch --strict isn't considering the overrides/rpm rpms (fix incoming for that). The other issue is that the error message doesn't show up in the output in CI.

These have made it to bodhi stable now.
This gets us new networking improvements added in
coreos/ignition-dracut#174.
@dustymabe dustymabe force-pushed the dusty-new-ignition branch from 8bd5901 to a7b21c3 Compare April 27, 2020 18:13
@dustymabe
Copy link
Member Author

rebased on top of latest master

jlebon added a commit to jlebon/coreos-assembler that referenced this pull request Apr 27, 2020
By default, `cosa fetch` ignores overrides in `overrides/rpm` since
those are meant to be temporary and might be e.g. locally built
packages. (Otherwise, for example, removing a cosa override might cause
`cosa build` to fail since the no longer overridden package was never
actually downloaded).

However, it can be useful sometimes to not ignore it if we know that
it's not a "temporary" package and that it won't be found otherwise from
the regular repos. This is the case in the CI of `fedora-coreos-config`
where we use `overrides/rpm` to test composes with overrides without
having to tag them into the pool first.

Related: coreos/fedora-coreos-config#365

Closes: coreos#1117
@dustymabe
Copy link
Member Author

with coreos/coreos-assembler#1404 cosa fetch --strict --with-cosa-overrides works

openshift-merge-robot pushed a commit to coreos/coreos-assembler that referenced this pull request Apr 27, 2020
By default, `cosa fetch` ignores overrides in `overrides/rpm` since
those are meant to be temporary and might be e.g. locally built
packages. (Otherwise, for example, removing a cosa override might cause
`cosa build` to fail since the no longer overridden package was never
actually downloaded).

However, it can be useful sometimes to not ignore it if we know that
it's not a "temporary" package and that it won't be found otherwise from
the regular repos. This is the case in the CI of `fedora-coreos-config`
where we use `overrides/rpm` to test composes with overrides without
having to tag them into the pool first.

Related: coreos/fedora-coreos-config#365

Closes: #1117
@jlebon
Copy link
Member

jlebon commented Apr 27, 2020

Do you want to try adding --with-cosa-overrides to .cci.jenkinsfile in this PR?

@dustymabe
Copy link
Member Author

Do you want to try adding --with-cosa-overrides to .cci.jenkinsfile in this PR?

Does that mean we are no longer using fcosBuild?

@dustymabe
Copy link
Member Author

ok extraFetchArgs was added in coreos/coreos-ci-lib#26. I just pushed a commit to use it.

.cci.jenkinsfile Outdated
""")

fcosBuild(skipInit: true)
fcosBuild(make: true, skipKola: true, extraFetchArgs: '--with-cosa-overrides')
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, why are we doing make: true and skipKola: true here and dropping skipInit: true? Was that by mistake?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops.. yeah. copy/paste error.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed!

@dustymabe dustymabe force-pushed the dusty-new-ignition branch from 0bd5bd9 to 7e5800c Compare April 27, 2020 20:56
Copy link
Member

@jlebon jlebon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@dustymabe dustymabe merged commit ebdf706 into coreos:testing-devel Apr 27, 2020
@dustymabe dustymabe deleted the dusty-new-ignition branch April 27, 2020 21:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants