Bug 892659 - in gui (not kickstart) mode, cannot reuse swap partition without formatting
Summary: in gui (not kickstart) mode, cannot reuse swap partition without formatting
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1104220 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-07 14:17 UTC by Gene Czarcinski
Modified: 2018-11-30 19:42 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 19:42:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Gene Czarcinski 2013-01-07 14:17:18 UTC
Description of problem:
When you do manual partitioning, you cannot use an existing swap partition without formatting it ... which, of course, assigns it a new UUID.

Therefore, another installed system which is also using that swap partition and referring to it by the old UUID will not find its swap partition.

Using kickstart, there is no problem.

Comment 1 Gene Czarcinski 2013-01-07 14:18:50 UTC
that was with smoke14 netinstall and anaconda 18.37.10-1

Comment 2 Gene Czarcinski 2013-10-19 14:07:57 UTC
I thought the swap "fixes" in 20.25.1 might have addressed this ... it did not.

Comment 3 Gene Czarcinski 2014-05-08 06:08:29 UTC
This is still broken!

Comment 4 Gene Czarcinski 2014-06-17 20:24:59 UTC
*** Bug 1104220 has been marked as a duplicate of this bug. ***

Comment 5 Máirín Duffy 2014-12-11 15:11:16 UTC
Taking a look at this - mockups are going to be here -
http://linuxgrrl.com/fedora-ux/Projects/Anaconda/Sketches/Swap-Situation/

Comment 6 Gene Czarcinski 2014-12-14 17:07:55 UTC
If the mockups correctly imply the new function, then this looks really good!

BTW, even if swap is detected from a previous install, it should be possible to create a new install with no swap defined.

Comment 7 Medic Momcilo 2015-05-20 00:16:22 UTC
I believe that importance of this is undermined.

I recently started doing a lot of testing on my notebook that doesn't have hardware accelerated virtualization so I just install a lot of Fedoras side by side.

This really makes it hard. I have to edit fstab and recreate ramdisk on every installation.

In my opinion, priority for this should be bumped.

Comment 8 Jan Kurik 2015-07-15 14:53:46 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle.
Changing version to '23'.

(As we did not run this process for some time, it could affect also pre-Fedora 23 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23

Comment 9 Lukas Middendorf 2016-11-23 17:25:13 UTC
I did a new install of Fedora 25 today (Everything netinstall disc). This problem still exists. It is not possible to assign an existing swap partition to the newly installed system without reformating (and therefore breaking all other systems that use the UUID). If I add the partition with reformat and then remove the check box again, the swap is not used, even though it is still listed in the partitions to be used for the newly installed system.

Comment 10 Fedora End Of Life 2016-11-24 10:53:33 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 11 Fedora End Of Life 2016-12-20 12:32:44 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 12 Medic Momcilo 2016-12-20 18:46:37 UTC
This is still applicable.

Comment 13 Fedora End Of Life 2017-11-16 19:15:21 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 14 Fedora End Of Life 2017-12-12 10:27:23 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 15 Medic Momcilo 2018-02-08 10:28:51 UTC
This is still applicable.

Comment 16 Ben Cotton 2018-11-27 17:09:44 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 17 Ben Cotton 2018-11-30 19:42:13 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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