no issues noted so far

Pretending to apply this upgrade to my f29 system appears to work:

dnf --releasever 30 upgrade --enablerepo=updates-testing --advisory=FEDORA-2019-919e826bbe

However in the summary I get something strange:

=====================================================================
 Package                                             
=====================================================================
Installing:
 actdiag
     replacing  python2-actdiag.noarch 0.5.4-11.fc29
 nwdiag
     replacing  python2-nwdiag.noarch 1.0.4-11.fc29
 seqdiag
     replacing  python2-seqdiag.noarch 0.9.5-15.fc29
Upgrading:
 fedora-obsolete-packages
     replacing  python2-bodhi.noarch 3.12.0-1.fc29
     replacing  python2-cccolutils.x86_64 1.5-9.fc29
     replacing  python2-dnf.noarch 4.2.2-2.fc29
     replacing  python2-hawkey.x86_64 0.28.1-1.fc29
     replacing  python2-libcomps.x86_64 0.1.11-1.fc29
     replacing  python2-libdnf.x86_64 0.28.1-1.fc29
     replacing  python2-librepo.x86_64 1.9.6-2.fc29
     replacing  python2-rpkg.noarch 1.57-6.fc29
     replacing  python2-smartcols.x86_64 0.3.0-4.fc29
     replacing  python2-xpyb.x86_64 1.3.1-11.fc28
 python3-actdiag
 python3-blockdiag
 python3-nwdiag
 python3-seqdiag
 python2-cairo
Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
 fedora-obsolete-packages
 fedora-obsolete-packages

Transaction Summary
=====================================================================

See fedora-obsolete-packages, it's both upgrading and skipped.

Please note that the following command gives very different results:

dnf --enablerepo=updates-testing --releasever 30 upgrade python2-blockdiag

Finally, when I pretend I want to do a system upgrade and inspect the summary as per bug 1699834 I don't see this happening. The python2-*diag packages go away but aren't replaced.

Here is how I tried:

dnf --enablerepo=updates-testing system-upgrade --releasever 30 download

So I'm assuming that when I try the system upgrade without the possibility to refer to this update's advisory it logically fails to enter the desired scenario for the same reason.

I can only hope this simply can't be tested while the update is still in testing.

I'd like to see the conflict. I don't understand why it is not par of the error message.

Problem: both package blockdiag-1.5.4-4.fc30.noarch and fedora-obsolete-packages-30-40.noarch obsolete python2-blockdiag < 1.5.4-2
 - cannot install both fedora-obsolete-packages-30-40.noarch and fedora-obsolete-packages-30-41.noarch
 - cannot install the best update candidate for package python2-blockdiag-1.5.3-15.fc29.noarch
 - cannot install the best update candidate for package fedora-obsolete-packages-29-22.noarch

"Problem: both package blockdiag-1.5.4-4.fc30.noarch and fedora-obsolete-packages-30-40.noarch obsolete python2-blockdiag < 1.5.4-2" seems like this will get fixed when this is moved form updates testing. I hope.

What does this do (you can N it, when it asks Is this ok [y/N])?

$ sudo dnf --releasever=30 --setopt=module_platform_id=platform:f30 --enablerepo=updates-testing distro-sync

I take it back, both distro-sync and system-upgrade with updates-testing enabled appear to work just fine.