| Summary: | swap partitions should be indicated by UUID | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Stodola <jstodola> | ||||
| Component: | anaconda | Assignee: | David Lehman <dlehman> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 6.1 | CC: | atodorov | ||||
| Target Milestone: | rc | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | anaconda-13.21.125-1 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-12-06 10:32:15 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Bug Depends On: | |||||||
| Bug Blocks: | 670159, 705163 | ||||||
| Attachments: |
|
||||||
|
Description
Jan Stodola
2011-04-12 14:51:20 UTC
Tested once more and this is more detailed reproducer: 1. install RHEL-5.7 on two zFCP LUNs, create a swap area on a plain partition (for example sdb2) 2. reboot into RHEL5 system, and run "blkid". The swap partition has no UUID defined: [root@rtt5 ~]# blkid /dev/sdb2: LABEL="SWAP-sdb2" TYPE="swap" /dev/sdb1: LABEL="/" UUID="0627e41e-6ab7-44a9-aa30-6bf9a9b74dbf" TYPE="ext3" /dev/sda1: LABEL="/boot" UUID="2deb0960-f66d-4a65-8d0a-7b5172db94f6" TYPE="ext3" 3. start installation of RHEL-6.1 4. select custom partitioning, reuse existing partitions for / and /boot, but do not format the swap partition. 5. finish the installation, reboot system and check /etc/fstab Created attachment 517598 [details]
screenshot of swap warning
In anaconda-13.21.126 there's a warning about swap partition not having UUID assigned.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1565.html |