LVM Merge hangs at 100%

[Sreyan Chakravarty]

LVM merging from snapshots don't work.

I have two logical volume - one is for the entire system and one is a
snapshot that I have created if I want to revert things if an upgrade
breaks them.

This is the output of *lvs*

LV             VG       Attr       LSize  Pool Origin Data%  Meta%  Move
Log Cpy%Sync Convert
  before_upgrade vgfedora swi-a-s--- 30.00g      fedora 22.84

fedora         vgfedora owi-aos--- 50.00g

Now I perform my upgrade by running *sudo dnf upgrade -y*, the upgrade
completes without any problems.

Now if I want to revert back to my old system state that is the snapshot
*before_upgrade*, I boot into a Live Fedora 31 environment and open my
encrypted partition using

$ cryptsetup open /dev/sda3 dm_crypt

And I issue the command:

$ lvconvert --merge /dev/vgfedora/before_upgrade

This works as expected until it hits 100%:

vgfedora/fedora: Merged: 99.59%
vgfedora/fedora: Merged: 99.90%
vgfedora/fedora: Merged: 100.00%

It hangs completely.

It has been almost 3 hours and I have not seen the status change.

Hitting *Ctrl + C* now will produce the following output:

^C  Interrupted...
  Giving up waiting for lock.
  Can't get lock for vgfedora
  Can't reread VG for vgfedora/fedora error flags 2

If I reboot the restoration has not been done and the logical volume
*before_upgrade* has vanished.

Here is my layout:

lsblk -f

NAME FSTYPE LABEL UUID                                   FSAVAIL FSUSE%
MOUNTPOINT
sda
├─sda1
│    ext4         2ea20bf9-ee56-490f-b12d-bd8d34e2fa3f    694.3M    22%
/boot
└─sda2
     crypto       b09a1a64-9b05-4c23-b048-1eacd03cf60b
  └─luks-b09a1a64-9b05-4c23-b048-1eacd03cf60b
     LVM2_m       B0i0fa-Yxme-Yntt-9uwM-VpFU-3xSB-K774pD
    ├─vgfedora-fedora-real
    │
    │ ├─vgfedora-fedora
    │ │  ext4   root  1176ad7d-d3e7-4062-b799-8e2b761f10af     39.5G    14%
/
    │ └─vgfedora-before_upgrade
    │    ext4   root  1176ad7d-d3e7-4062-b799-8e2b761f10af
    └─vgfedora-before_upgrade-cow

└─vgfedora-before_upgrade
         ext4   root  1176ad7d-d3e7-4062-b799-8e2b761f10af

What is going on ?

Interestingly I have tried the same thing in other distributions like
Ubuntu and this works. So seems like a Fedora specific issue.

Let me know if any other information is required, like any other log files.

Thanks.

[stan]

On Sun, 5 Apr 2020 12:56:35 -0400
Sreyan Chakravarty  wrote:
> LVM merging from snapshots don't work.
>
> I have two logical volume - one is for the entire system and one is a
> snapshot that I have created if I want to revert things if an upgrade
> breaks them.

[snip]
> And I issue the command:
>
> $ lvconvert --merge /dev/vgfedora/before_upgrade
>
> This works as expected until it hits 100%:
>
> vgfedora/fedora: Merged: 99.59%
> vgfedora/fedora: Merged: 99.90%
> vgfedora/fedora: Merged: 100.00%
>
> It hangs completely.

[snip]
> If I reboot the restoration has not been done and the logical volume
> *before_upgrade* has vanished.

[snip]
> What is going on ?

You might get an answer here on the users' list, but it is more likely
you will get help if you open a bugzilla.  You will have to create a
login, which will require an email address.

https://bugzilla.redhat.com/

I checked and there isn't an open bug for lvconvert for this. Open the
ticket for fedora, component lvm2.  Put a summary of the lvconvert
problem in the subject. Put the information from your post into the
ticket (additional info) so whoever looks at it can see the problem,
and has enough information to duplicate the problem.

Thanks.

[Sreyan Chakravarty]

So you mean this is a problem with lvconvert itself ?

On Mon, Apr 6, 2020 at 12:22 AM stan via users <
[e-mail]> wrote:
> On Sun, 5 Apr 2020 12:56:35 -0400
> Sreyan Chakravarty  wrote:
> > LVM merging from snapshots don't work.
> >
> > I have two logical volume - one is for the entire system and one is a
> > snapshot that I have created if I want to revert things if an upgrade
> > breaks them.
>
> [snip]
> > And I issue the command:
> >
> > $ lvconvert --merge /dev/vgfedora/before_upgrade
> >
> > This works as expected until it hits 100%:
> >
> > vgfedora/fedora: Merged: 99.59%
> > vgfedora/fedora: Merged: 99.90%
> > vgfedora/fedora: Merged: 100.00%
> >
> > It hangs completely.
>
> [snip]
> > If I reboot the restoration has not been done and the logical volume
> > *before_upgrade* has vanished.
>
> [snip]
> > What is going on ?
>
> You might get an answer here on the users' list, but it is more likely
> you will get help if you open a bugzilla.  You will have to create a
> login, which will require an email address.
>
> https://bugzilla.redhat.com/
>
> I checked and there isn't an open bug for lvconvert for this. Open the
> ticket for fedora, component lvm2.  Put a summary of the lvconvert
> problem in the subject. Put the information from your post into the
> ticket (additional info) so whoever looks at it can see the problem,
> and has enough information to duplicate the problem.
>
> Thanks.
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

[stan]

On Mon, 6 Apr 2020 03:30:23 +0530
Sreyan Chakravarty  wrote:
> So you mean this is a problem with lvconvert itself ?

I don't know that for sure since I am not familiar with lvconvert.  But,
the fact that it is hanging while doing its job suggests that it is a
good place to start.
> Giving up waiting for lock.

This says that lvconvert can't complete because it is waiting for a
resource that is locked.  Something else has that lock, and it seems
to be something in the lvconvert chain, or it would be released and
lvconvert could complete. This is known as deadlock, and is a resource
contention error, and usually is a bug.

e.g.  A starts and runs, and triggers B to run.  B grabs a lock on
resource X while running and then waits for completion of A in order
to finish. A gets to the end of its tasks, and needs a lock on resource
X to finish. But B has that lock, and is waiting for A to complete to
finish and release X. =><=

[Sreyan Chakravarty]

You think it may be a kernel bug ? It happens in Fedora, Ubuntu 19.10 does
not have this.

On Mon, Apr 6, 2020 at 6:27 AM stan via users 
wrote:
> On Mon, 6 Apr 2020 03:30:23 +0530
> Sreyan Chakravarty  wrote:
> > So you mean this is a problem with lvconvert itself ?
>
> I don't know that for sure since I am not familiar with lvconvert.  But,
> the fact that it is hanging while doing its job suggests that it is a
> good place to start.
> > Giving up waiting for lock.
>
> This says that lvconvert can't complete because it is waiting for a
> resource that is locked.  Something else has that lock, and it seems
> to be something in the lvconvert chain, or it would be released and
> lvconvert could complete. This is known as deadlock, and is a resource
> contention error, and usually is a bug.
>
> e.g.  A starts and runs, and triggers B to run.  B grabs a lock on
> resource X while running and then waits for completion of A in order
> to finish. A gets to the end of its tasks, and needs a lock on resource
> X to finish. But B has that lock, and is waiting for A to complete to
> finish and release X. =><=
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Sreyan Chakravarty]

The problem with Bugzilla is that there are no replies there at all.

On Mon, Apr 6, 2020 at 10:54 AM Sreyan Chakravarty 
wrote:
> You think it may be a kernel bug ? It happens in Fedora, Ubuntu 19.10 does
> not have this.
>
> On Mon, Apr 6, 2020 at 6:27 AM stan via users <
> [e-mail]> wrote:
> > On Mon, 6 Apr 2020 03:30:23 +0530
> > Sreyan Chakravarty  wrote:
> > > So you mean this is a problem with lvconvert itself ?
> >
> > I don't know that for sure since I am not familiar with lvconvert.  But,
> > the fact that it is hanging while doing its job suggests that it is a
> > good place to start.
> > > Giving up waiting for lock.
> >
> > This says that lvconvert can't complete because it is waiting for a
> > resource that is locked.  Something else has that lock, and it seems
> > to be something in the lvconvert chain, or it would be released and
> > lvconvert could complete. This is known as deadlock, and is a resource
> > contention error, and usually is a bug.
> >
> > e.g.  A starts and runs, and triggers B to run.  B grabs a lock on
> > resource X while running and then waits for completion of A in order
> > to finish. A gets to the end of its tasks, and needs a lock on resource
> > X to finish. But B has that lock, and is waiting for A to complete to
> > finish and release X. =><=
> > _______________________________________________
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > Fedora Code of Conduct:
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://lists.fedoraproject.org/archives/list/[e-mail]
>
> --
> Regards,
> Sreyan Chakravarty

[Sreyan Chakravarty]

Do you know how to install the latest version of Rawhide ? I mean from
where in the latest Anaconda installer do i select "Installation source" ?

On Mon, Apr 6, 2020 at 11:17 AM Sreyan Chakravarty 
wrote:
> The problem with Bugzilla is that there are no replies there at all.
>
> On Mon, Apr 6, 2020 at 10:54 AM Sreyan Chakravarty 
> wrote:
> > You think it may be a kernel bug ? It happens in Fedora, Ubuntu 19.10
> > does not have this.
> >
> > On Mon, Apr 6, 2020 at 6:27 AM stan via users <
> > [e-mail]> wrote:
> > > On Mon, 6 Apr 2020 03:30:23 +0530
> > > Sreyan Chakravarty  wrote:
> > > > So you mean this is a problem with lvconvert itself ?
> > >
> > > I don't know that for sure since I am not familiar with lvconvert.  But,
> > > the fact that it is hanging while doing its job suggests that it is a
> > > good place to start.
> > > > Giving up waiting for lock.
> > >
> > > This says that lvconvert can't complete because it is waiting for a
> > > resource that is locked.  Something else has that lock, and it seems
> > > to be something in the lvconvert chain, or it would be released and
> > > lvconvert could complete. This is known as deadlock, and is a resource
> > > contention error, and usually is a bug.
> > >
> > > e.g.  A starts and runs, and triggers B to run.  B grabs a lock on
> > > resource X while running and then waits for completion of A in order
> > > to finish. A gets to the end of its tasks, and needs a lock on resource
> > > X to finish. But B has that lock, and is waiting for A to complete to
> > > finish and release X. =><=
> > > _______________________________________________
> > > users mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > Fedora Code of Conduct:
> > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > List Archives:
> > > https://lists.fedoraproject.org/archives/list/[e-mail]
> >
> > --
> > Regards,
> > Sreyan Chakravarty
>
> --
> Regards,
> Sreyan Chakravarty

[Sreyan Chakravarty]

The problem is with the LVM version that comes with the stock install. This
is the version:

LVM Version: 2.03.05(2)
Library Version: 1.02.163
Driver Configuration: 4.40.0

Using a linux distro that uses a more recent version solves the problem.
For me, I used ArcoLinux which uses a more recent version by default:

LVM version: 2.02.186(2)
Library version: 1.02.164
Driver Version: 4.41.0

The driver are however updated in Fedora after a fresh install my running
sudo dnf upgrade or my upgrading from the Software Centre.

On Mon, Apr 6, 2020 at 11:52 AM Sreyan Chakravarty 
wrote:
> Do you know how to install the latest version of Rawhide ? I mean from
> where in the latest Anaconda installer do i select "Installation source" ?
>
> On Mon, Apr 6, 2020 at 11:17 AM Sreyan Chakravarty 
> wrote:
> > The problem with Bugzilla is that there are no replies there at all.
> >
> > On Mon, Apr 6, 2020 at 10:54 AM Sreyan Chakravarty 
> > wrote:
> > > You think it may be a kernel bug ? It happens in Fedora, Ubuntu 19.10
> > > does not have this.
> > >
> > > On Mon, Apr 6, 2020 at 6:27 AM stan via users <
> > > [e-mail]> wrote:
> > > > On Mon, 6 Apr 2020 03:30:23 +0530
> > > > Sreyan Chakravarty  wrote:
> > > > > So you mean this is a problem with lvconvert itself ?
> > > >
> > > > I don't know that for sure since I am not familiar with lvconvert.  But,
> > > > the fact that it is hanging while doing its job suggests that it is a
> > > > good place to start.
> > > > > Giving up waiting for lock.
> > > >
> > > > This says that lvconvert can't complete because it is waiting for a
> > > > resource that is locked.  Something else has that lock, and it seems
> > > > to be something in the lvconvert chain, or it would be released and
> > > > lvconvert could complete. This is known as deadlock, and is a resource
> > > > contention error, and usually is a bug.
> > > >
> > > > e.g.  A starts and runs, and triggers B to run.  B grabs a lock on
> > > > resource X while running and then waits for completion of A in order
> > > > to finish. A gets to the end of its tasks, and needs a lock on resource
> > > > X to finish. But B has that lock, and is waiting for A to complete to
> > > > finish and release X. =><=
> > > > _______________________________________________
> > > > users mailing list -- [e-mail]
> > > > To unsubscribe send an email to [e-mail]
> > > > Fedora Code of Conduct:
> > > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > > > List Archives:
> > > > https://lists.fedoraproject.org/archives/list/[e-mail]
> > >
> > > --
> > > Regards,
> > > Sreyan Chakravarty
> >
> > --
> > Regards,
> > Sreyan Chakravarty
>
> --
> Regards,
> Sreyan Chakravarty

[stan]

On Mon, 6 Apr 2020 17:53:13 +0530
Sreyan Chakravarty  wrote:
> The problem is with the LVM version that comes with the stock
> install. This is the version:
>
> LVM Version: 2.03.05(2)
> Library Version: 1.02.163

Where did you get this?  My F31 has librarys
/usr/lib64/libdevmapper-event-lvm2.so.2.03
/usr/lib64/liblvm2cmd.so.2.03
from lvm2-libs.
Are you looking at a different library?
> Driver Configuration: 4.40.0

What is this a driver for?  Where did it come from?
You need to include more information.
> Using a linux distro that uses a more recent version solves the
> problem. For me, I used ArcoLinux which uses a more recent version by
> default:
>
> LVM version: 2.02.186(2)
> Library version: 1.02.164
> Driver Version: 4.41.0
>
> The driver are however updated in Fedora after a fresh install my
> running sudo dnf upgrade or my upgrading from the Software Centre.

Yes, just as a general rule, always update immediately after install.
The install image has gone through testing, so is frozen at some moment
in the past.  But updates continue piling up, and bugs continue getting
fixed, even while testing is going on; they just don't make it to the
image, or testing would never finish.  So, if you have a problem, first
update everything to the latest versions, and test again.

[Sreyan Chakravarty]

I got it by running

lvconvert --version

I can't update the ISO image now can I ?

Which means I have to use a completely different distro for LVM snapshots
and merging.

On Mon, Apr 6, 2020 at 10:21 PM stan via users <
[e-mail]> wrote:
> On Mon, 6 Apr 2020 17:53:13 +0530
> Sreyan Chakravarty  wrote:
> > The problem is with the LVM version that comes with the stock
> > install. This is the version:
> >
> > LVM Version: 2.03.05(2)
> > Library Version: 1.02.163
>
> Where did you get this?  My F31 has librarys
> /usr/lib64/libdevmapper-event-lvm2.so.2.03
> /usr/lib64/liblvm2cmd.so.2.03
> from lvm2-libs.
> Are you looking at a different library?
> > Driver Configuration: 4.40.0
>
> What is this a driver for?  Where did it come from?
> You need to include more information.
> > Using a linux distro that uses a more recent version solves the
> > problem. For me, I used ArcoLinux which uses a more recent version by
> > default:
> >
> > LVM version: 2.02.186(2)
> > Library version: 1.02.164
> > Driver Version: 4.41.0
> >
> > The driver are however updated in Fedora after a fresh install my
> > running sudo dnf upgrade or my upgrading from the Software Centre.
>
> Yes, just as a general rule, always update immediately after install.
> The install image has gone through testing, so is frozen at some moment
> in the past.  But updates continue piling up, and bugs continue getting
> fixed, even while testing is going on; they just don't make it to the
> image, or testing would never finish.  So, if you have a problem, first
> update everything to the latest versions, and test again.
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

[stan]

On Tue, 7 Apr 2020 01:12:01 +0530
Sreyan Chakravarty  wrote:
> I got it by running
>
> lvconvert --version
>
> I can't update the ISO image now can I ?

Actually, I think you can, since the live images are fully functional
in order to be installed.  At least I have a memory of doing so years
ago. After the ISO image is running, you should be able to run a dnf
update for the lvm2 packages if you have access to the internet. It
will be temporary, and you shouldn't do large updates in order not to
stress your system (I think it all happens in memory), but just the lvm2
packages should be fine. Worth a try, at least.

[Joe Zeff]

On 04/06/2020 04:22 PM, stan via users wrote:
> Actually, I think you can, since the live images are fully functional
> in order to be installed.  At least I have a memory of doing so years
> ago. After the ISO image is running, you should be able to run a dnf
> update for the lvm2 packages if you have access to the internet. It
> will be temporary, and you shouldn't do large updates in order not to
> stress your system (I think it all happens in memory), but just the lvm2
> packages should be fine. Worth a try, at least.

My understanding is that you can update the live system or even install 
packages, but that the changes go away when you reboot.  However, if you 
install to disk, your new system will have any changes you'd made that 
way.  Just don't reboot before installing, unless you didn't like some 
of your changes.  YMMV, and don't blame me if anything goes wrong, as 
I've never tried this myself.

[Sreyan Chakravarty]

Well I tried that it told me that I did not have enough space.

The easiest option is use a distro which uses the updated version. I have
no clue why Fedora a distro that lives on the bleeding edge does not update
its ISO images.

On Tue, Apr 7, 2020 at 3:53 AM stan via users 
wrote:
> On Tue, 7 Apr 2020 01:12:01 +0530
> Sreyan Chakravarty  wrote:
> > I got it by running
> >
> > lvconvert --version
> >
> > I can't update the ISO image now can I ?
>
> Actually, I think you can, since the live images are fully functional
> in order to be installed.  At least I have a memory of doing so years
> ago. After the ISO image is running, you should be able to run a dnf
> update for the lvm2 packages if you have access to the internet. It
> will be temporary, and you shouldn't do large updates in order not to
> stress your system (I think it all happens in memory), but just the lvm2
> packages should be fine. Worth a try, at least.
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Samuel Sieb]

On 4/6/20 9:52 PM, Sreyan Chakravarty wrote:
> Well I tried that it told me that I did not have enough space.
>
> The easiest option is use a distro which uses the updated version. I 
> have no clue why Fedora a distro that lives on the bleeding edge does 
> not update its ISO images.

Because releasing new official images requires running the whole QA 
process on them and QA is busy working on the next release.  There are 
unofficial respins that are done regularly for the workstation live 
image though.

[Sreyan Chakravarty]

I though Fedora KDE was an official image, are you saying that its not ?

On Tue, Apr 7, 2020 at 2:13 PM Samuel Sieb  wrote:
> On 4/6/20 9:52 PM, Sreyan Chakravarty wrote:
> > Well I tried that it told me that I did not have enough space.
> >
> > The easiest option is use a distro which uses the updated version. I
> > have no clue why Fedora a distro that lives on the bleeding edge does
> > not update its ISO images.
>
> Because releasing new official images requires running the whole QA
> process on them and QA is busy working on the next release.  There are
> unofficial respins that are done regularly for the workstation live
> image though.
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Samuel Sieb]

On 4/7/20 4:58 AM, Sreyan Chakravarty wrote:
> I though Fedora KDE was an official image, are you saying that its not ?

I don't see how that relates to what I said.  The official images are 
only released once for each release.  There are unofficial respins done 
for the workstation live, but only that one.  It's only 6 months between 
releases, so there's not much point doing respins for everything anyway.
> On Tue, Apr 7, 2020 at 2:13 PM Samuel Sieb <[e-mail] 
> > wrote:
> On 4/6/20 9:52 PM, Sreyan Chakravarty wrote:
>  > Well I tried that it told me that I did not have enough space.
>  >
>  > The easiest option is use a distro which uses the updated version. I
>  > have no clue why Fedora a distro that lives on the bleeding edge
> does
>  > not update its ISO images.
>
> Because releasing new official images requires running the whole QA
> process on them and QA is busy working on the next release.  There are
> unofficial respins that are done regularly for the workstation live
> image though.

[Sreyan Chakravarty]

Thanks

On Tue, Apr 7, 2020 at 10:58 PM Samuel Sieb  wrote:
> On 4/7/20 4:58 AM, Sreyan Chakravarty wrote:
> > I though Fedora KDE was an official image, are you saying that its not ?
>
> I don't see how that relates to what I said.  The official images are
> only released once for each release.  There are unofficial respins done
> for the workstation live, but only that one.  It's only 6 months between
> releases, so there's not much point doing respins for everything anyway.
> > On Tue, Apr 7, 2020 at 2:13 PM Samuel Sieb <[e-mail]
> > > wrote:
> > On 4/6/20 9:52 PM, Sreyan Chakravarty wrote:
> >  > Well I tried that it told me that I did not have enough space.
> >  >
> >  > The easiest option is use a distro which uses the updated
>
> version. I
> >  > have no clue why Fedora a distro that lives on the bleeding edge
> > does
> >  > not update its ISO images.
> >
> > Because releasing new official images requires running the whole QA
> > process on them and QA is busy working on the next release.  There
>
> are
> > unofficial respins that are done regularly for the workstation live
> > image though.
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

[stan]

On Mon, 6 Apr 2020 11:52:15 +0530
Sreyan Chakravarty  wrote:
> Do you know how to install the latest version of Rawhide ? I mean from
> where in the latest Anaconda installer do i select "Installation
> source" ?

You could get a snapshot of rawhide from the Fedora download page,

https://www.happyassassin.net/nightlies.html

but I've always found the best way to get to rawhide was to install the
last numbered Fedora before rawhide, currently the F32 beta, and then
flip the rawhide repositories to active in /etc/yum.repos.d, and run an
update.  I *think* the fedora-gpg-keys are updated for n+1 in the beta,
so that should turn your system into Fedora rawhide.   Beware,
adventurer, there is no return from this!

https://getfedora.org/en/workstation/download/

I do a minimal install from the netinstall image, at the bottom of the
page above or at

https://alt.fedoraproject.org/

In fact, I usually only install without a gui, and update to all the
packages I want after everything is working.  I always have two running
versions of Fedora, n and n-1, so that if something goes wrong with an
install of n+1 (overwriting n-1 install), I have a fall back in order
to troubleshoot.  Disk is cheap, way cheaper than trials and
tribulations for me.  :-)

[stan]

On Mon, 6 Apr 2020 11:17:35 +0530
Sreyan Chakravarty  wrote:
> The problem with Bugzilla is that there are no replies there at all.

Yeah, that's a general issue with open source.  If no one takes an
interest and puts in the work, it doesn't get done.  The Fedora
maintainers tend to be very busy people, so things can slide.