Cannot update to fcos 37, invalid context system_u:object_r:targetd_var_t:s0

greeting, my server is running fedora:fedora/x86_64/coreos/next

update to f37 did not work:

systemd[1]: Finished ostree-finalize-staged.service - OSTree Finalize Staged Deployment.
systemd[1]: Stopping ostree-finalize-staged.service - OSTree Finalize Staged Deployment...
ostree[4664]: Finalizing staged deployment
ostree[4664]: Copying /etc changes: 12 modified, 0 removed, 60 added
ostree[4664]: Copying /etc changes: 12 modified, 0 removed, 60 added
ostree[4673]: The --rebuild-if-modules-changed option is deprecated. Use --refresh instead.
ostree[4674]: libsepol.context_from_record: type targetd_var_t is not defined
ostree[4674]: libsepol.context_from_record: could not create context structure
ostree[4674]: libsepol.context_from_string: could not create context structure
ostree[4674]: libsepol.sepol_context_to_sid: could not convert system_u:object_r:targetd_var_t:s0 to sid
ostree[4674]: invalid context system_u:object_r:targetd_var_t:s0
ostree[4673]: libsemanage.semanage_validate_and_compile_fcontexts: setfiles returned error code 255.
ostree[4673]: semodule:  Failed!
ostree[4664]: error: Child process exited with code 1
systemd[1]: ostree-finalize-staged.service: Control process exited, code=exited, status=1/FAILURE
systemd[1]: ostree-finalize-staged.service: Failed with result 'exit-code'.
systemd[1]: Stopped ostree-finalize-staged.service - OSTree Finalize Staged Deployment.
systemd[1]: ostree-finalize-staged.service: Consumed 2.480s CPU time.

I don’t have /var/targetd folder. This selinux type was introduced in selinux-policy 37.6-1.

EDIT:
I must have done something wrong installing/uninstalling custom SELinux modules. I ran

semodule --rebuild-if-modules-changed -vvv -C

under f36 and then the update happened properly. I had some extra troubles:

  • 1024 bits RSA key are not supported anymore under f37
  • rpm-ostree rollback requires the user to enter the grub password

it’s all good now anyway.

Please report Fedora CoreOS issues in the tracker: GitHub - coreos/fedora-coreos-tracker: Issue tracker for Fedora CoreOS

I am not sure there is any issue to report here.