Does anyone know if 7.6 is supported? We are having issues capturing a RHEL7.6 image.
Hi, yes, it’s supported:
https://www.ibm.com/support/knowledgecenter/SS63NW_9.5.0/com.ibm.bigfix.lifecycle.doc/Lifecycle/OSD_Users_Guide/c_new_features.html
The following updates were released with OSD 3.10 site 83
Added support
Windows 10 Release ID 1809 and Windows Server 2019 support (deploy to)
Added support
Red Hat Enterprise Linux 7.5 and Red Hat Enterprise Linux 7.6 support (deploy to)
Added support
MDT 8456 support
Thank you for for your response Sergio.
Any ideas why we are getting these errors in the “captureLinux.log” trying to capture RHEL7.6 Server? We are also seeing these errors on RHEL8 captures as well.
[2019/08/29 21:02:11] A Detecting partitions…
[2019/08/29 21:02:11] fstate: convert root with EXT2 attr
[2019/08/29 21:02:11] { }
[2019/08/29 21:02:11] { “loop*” }
[2019/08/29 21:02:11] A Running [fdisk -lu > /tmp/partorder]
[2019/08/29 21:02:11] A *** Output of command [fdisk -lu > /tmp/partorder]^M
[2019/08/29 21:02:11] A *** End of output for [fdisk -lu > /tmp/partorder]^M
[2019/08/29 21:02:11] A Command [fdisk -lu > /tmp/partorder] successfully completed in 0.10 seconds
[2019/08/29 21:02:11] [21:02:11] isUEFITarget>>>
[2019/08/29 21:02:11] [21:02:11] isUEFITarget return false
[2019/08/29 21:02:11] A Running [cp /sys/block/sda/device/model /tmp/sda_tmp]
[2019/08/29 21:02:11] A *** Output of command [cp /sys/block/sda/device/model /tmp/sda_tmp]^M
[2019/08/29 21:02:11] A *** End of output for [cp /sys/block/sda/device/model /tmp/sda_tmp]^M
[2019/08/29 21:02:11] A Command [cp /sys/block/sda/device/model /tmp/sda_tmp] successfully completed in 0.10 seconds
[2019/08/29 21:02:11] A Detected disk model QEMU HARDDISK
[2019/08/29 21:02:11] A Running [cp /sys/block/sda/size /tmp/sda_tmp]
[2019/08/29 21:02:11] A *** Output of command [cp /sys/block/sda/size /tmp/sda_tmp]^M
[2019/08/29 21:02:11] A *** End of output for [cp /sys/block/sda/size /tmp/sda_tmp]^M
[2019/08/29 21:02:11] A Command [cp /sys/block/sda/size /tmp/sda_tmp] successfully completed in 0.11 seconds
[2019/08/29 21:02:11] A Running [find /dev/disk/by-id -lname “*sda” > /tmp/find_id_output]
[2019/08/29 21:02:11] A *** Output of command [find /dev/disk/by-id -lname “*sda” > /tmp/find_id_output]^M
[2019/08/29 21:02:11] A *** End of output for [find /dev/disk/by-id -lname “*sda” > /tmp/find_id_output]^M
[2019/08/29 21:02:11] A Command [find /dev/disk/by-id -lname “*sda” > /tmp/find_id_output] successfully completed in 0.10 seconds
[2019/08/29 21:02:11] A Disk /dev/sda ‘WWN’ = ‘ata-QEMU_HARDDISK_QM00001’
[2019/08/29 21:02:11] A Running [hdparm -g /dev/sda > /tmp/geom.txt]
[2019/08/29 21:02:11] A *** Output of command [hdparm -g /dev/sda > /tmp/geom.txt]^M
[2019/08/29 21:02:11] A *** End of output for [hdparm -g /dev/sda > /tmp/geom.txt]^M
[2019/08/29 21:02:11] A Command [hdparm -g /dev/sda > /tmp/geom.txt] successfully completed in 0.11 seconds
[2019/08/29 21:02:11] A Error raised by TestIniSection in utils.rbc, line 7989 [VM:3372]
[2019/08/29 21:02:11] A No such key in variable
[2019/08/29 21:02:11] A (called from testActIniSection (sequencer.rbc:3943))
[2019/08/29 21:02:11] A (called from LinuxDEGetDisqks (ibm_utils.rbc:1386))
[2019/08/29 21:02:11] A (called from GetPartitionsForAllDisks (ibm_utils.rbc:2022))
[2019/08/29 21:02:11] A (called from getPartFromFdisk (ibm_utils.rbc:2256))
[2019/08/29 21:02:11] A (called from LinuxDEMountAllPartitions (ibm_utils.rbc:1879))
[2019/08/29 21:02:11] A (called from mount (ibm_utils.rbc:1949))
[2019/08/29 21:02:11] A (called from mount (ibm_utils.rbc:2262))
[2019/08/29 21:02:11] A (called from RAD_capturelinux (load.rbc:6871))
[2019/08/29 21:02:11] A (called from AgentDispatch (rbagent.rbc:4402))
[2019/08/29 21:02:11] A (called from --toplevel-- (rbagent.rbc:4829))
[2019/08/29 21:02:11] A Running [hdparm -I /dev/sda | grep Serial > /tmp/serial.txt]
[2019/08/29 21:02:11] A *** Output of command [hdparm -I /dev/sda | grep Serial > /tmp/serial.txt]^M
[2019/08/29 21:02:11] A *** End of output for [hdparm -I /dev/sda | grep Serial > /tmp/serial.txt]^M
[2019/08/29 21:02:11] A Command [hdparm -I /dev/sda | grep Serial > /tmp/serial.txt] successfully completed in 0.10 seconds
[2019/08/29 21:02:11] A serial: QM00001
[2019/08/29 21:02:11] A Multipath check skipped on ‘sda’
[2019/08/29 21:02:11] A Error raised by TestIniSection in utils.rbc, line 7989 [VM:3372]
[2019/08/29 21:02:11] A No such key in variable
[2019/08/29 21:02:11] A (called from testActIniSection (sequencer.rbc:3943))
[2019/08/29 21:02:11] A (called from LinuxDEGetDisks (ibm_utils.rbc:1438))
[2019/08/29 21:02:11] A (called from GetPartitionsForAllDisks (ibm_utils.rbc:2022))
[2019/08/29 21:02:11] A (called from getPartFromFdisk (ibm_utils.rbc:2256))
[2019/08/29 21:02:11] A (called from LinuxDEMountAllPartitions (ibm_utils.rbc:1879))
[2019/08/29 21:02:11] A (called from mount (ibm_utils.rbc:1949))
[2019/08/29 21:02:11] A (called from mount (ibm_utils.rbc:2262))
[2019/08/29 21:02:11] A (called from RAD_capturelinux (load.rbc:6871))
[2019/08/29 21:02:11] A (called from AgentDispatch (rbagent.rbc:4402))
[2019/08/29 21:02:11] A (called from --toplevel-- (rbagent.rbc:4829))
[2019/08/29 21:02:11] A Multipath configuration is not present
[2019/08/29 21:02:11] Valid Disks:
[2019/08/29 21:02:11] { { name: “sda”, nbsects_usable: 62910540, nbsects_full: 62914560, geom_sect: 63, geom_head: 255, geom_cyl: 3916, cylindersize: 16065, type: 2, scsi_id: { id_vendor: “”, id_model: “”, id_wwn_ext: “”, id_wwn: “ata-QEMU_HARDDISK_QM00001” }, index: 0 } }
[2019/08/29 21:02:11] [21:02:11] isUEFITarget>>>
[2019/08/29 21:02:11] [21:02:11] isUEFITarget return false
Hi,
does the capture task finally fail or is it completed successfully? The error could be not meaningful for the final status of the capture task.
The code is checking the multipath and could be that it reports an error if it cannot find it but continuing will take to the success of the capture.
Thanks.
The capture task reports “failed” but the system appears to come up okay.
Failed pause while {pending restart}
//Final check: capturestatus flag set if capture process completed, used in action SuccessCriteria
Hi,
does the entire capture task report “failed” or only the single step you mention?
If it’s the single step, is the global status of the capture task complete?
Thanks.
Yes the final status is Failed but the only failed step in the Action History is the one shared in the previous post.
Hi David,
Even if the action is failed, are on the network share any files of the capture image?
If not, did the capture action start on the target machine after reboot? Or the system rebooted normally to the standard OS?
Thanks
Yes the files are there, but they are a third smaller than previous captures. I was able to deploy the captured image, but I’m going to have to spend some time figuring out why the image is smaller. Very frustrating.
Hi,
What is the size of the lim files?
If you want to be sure they are correct, please check, on the target machine, the content of file “/var/tmp/capturestatus.txt”. If it is “COMPLETED”, the capture is ok.
Furthermore, you can inspect the log file associated with the .lim. This is automatically created on the network share with the same name of the lim file. Errors concerned mount/umount are not important.
I’ve been using OSD for several years to capture/deploy linux images so I’m very familiar with the process.
cat /var/tmp/capturestatus.txt
STARTED
It seems that the action is not yet finished then some issues occurred.
If you want, you could share the log here but I suggest you to open a request to official support and attach there the capture log.