Hide Forgot
Description of problem: automated build for RHEL 6.4 in AWS failed when swapon -a returned 255 due to /etc/fstab entry Version-Release number of selected component (if applicable): AMI: RHEL-6.4_GA-x86_64-7-Hourly2 (ami-5344d263) How reproducible: Happened 4 times before I figured out what was going on Steps to Reproduce: 1. Build an Instance 2. Create a swap device (LVM typically) 3. Add entry to /etc/fstab for new swap device 4. Run swapon -a to add all swap devices Actual results: Return code 255 with output about /dev/sda3 not existing Expected results: Return code of 0 as the device added should be the only one. Additional info: Workaround: use swapon -a -e
Following the below mentioned procedure, we were not able to reproduce the issue: 1. create an instance of ami-5344d263 (us-west-2 region) 2. once the system is up, attach a new volume to the instance (/dev/xvdj) 3. create a swap partition: fdisk /dev/xvdj 4. mkswap /dev/xvdj1 5. add entry to /etc/fstab /dev/xvdj1 none swap sw 0 0 6. swapon -a 7. exit code is 0 and free -m shows the swap space is in use We also gave it a try on a RHEL 6.8 machine (ami-e017f58f in eu-central-1), the result was the same, exit code 0.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com/