Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1342447 - Ifconfig command is not supported on p2v client
Ifconfig command is not supported on p2v client
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libguestfs (Show other bugs)
7.3
x86_64 Unspecified
low Severity low
: rc
: ---
Assigned To: Richard W.M. Jones
Virtualization Bugs
P2V
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-06-03 05:47 EDT by mxie@redhat.com
Modified: 2016-11-03 14:01 EDT (History)
5 users (show)

See Also:
Fixed In Version: libguestfs-1.32.5-2.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-11-03 14:01:07 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
screenshot (126.54 KB, image/png)
2016-06-03 05:47 EDT, mxie@redhat.com
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2576 normal SHIPPED_LIVE Moderate: libguestfs and virt-p2v security, bug fix, and enhancement update 2016-11-03 08:06:51 EDT

  None (edit)
Description mxie@redhat.com 2016-06-03 05:47:58 EDT
Created attachment 1164413 [details]
screenshot

Description of problem:
Ifconfig command is not supported on p2v client


Version-Release number of selected component (if applicable):
virt-p2v-1.32.5-1.el7.iso


How reproducible:
100%

Steps to Reproduce:
1.Boot the source machine into p2v client via iso
2.Input the ip and password of conversion server
3.At the input conversion info interface, there are many networks listed in network interfaces
4.Exit the p2v GUI interface and enter into p2v console mode, input the command#ifconfig to check network info of machine but p2v shows not support ifconfig command
#ifconfig
ifconfig:command not found

5.Try to use command #ip a list which told by rjones, the network info could be showed normally, pls refer to screenshot

Actual results:
As above description

Expected results:
Although command #ip a list could show network info at p2v console mode, it is known by little people.The command #ifconfig is usually used by most of people for checking network info. so it is better if p2v console mode could support ifconfig command 
 

Additional info:
Comment 1 Richard W.M. Jones 2016-06-03 06:29:22 EDT
I have a trivial patch lined up in my queue for this (not posted).
Comment 3 zhoujunqin 2016-06-22 07:36:33 EDT
I can reproduce this issue with build:
virt-p2v-1.32.4-3.el7.iso

Then try to verify this bug with new build:
virt-p2v-1.32.5-5.el7.iso

Steps:
1. Boot the source machine into p2v client via iso 
2. After virt-p2v client launched, press "Ctrl+Alt+F1[3,4,5,6]" switch to p2v console mode.
3. Input the command: ifconfig

# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.100.187  netmask 255.255.255.0  broadcast 192.168.100.255
        inet6 fe80::5054:ff:febb:c424  prefixlen 64  scopeid 0x20<link>
        ether 52:54:00:bb:c4:24  txqueuelen 1000  (Ethernet)
        RX packets 863  bytes 50544 (49.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 40  bytes 6817 (6.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 4  bytes 352 (352.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4  bytes 352 (352.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Since command ifconfig is added and it works well, move this bug from ON_QA to VERIFIED.
Comment 5 errata-xmlrpc 2016-11-03 14:01:07 EDT
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.

https://rhn.redhat.com/errata/RHSA-2016-2576.html

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