Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Test this bug with:
livecd-p2v-201507220606.iso
When launch virt-p2v from iso and enter console mode,check service sshd status,it's active.
Test with:
virt-p2v-livecd-1.28.1-1.49.1.el7.iso
Repeat the above steps,check service sshd status,it's inactive.
Is that enough to verify this bug?
Comment 5Richard W.M. Jones
2015-08-12 10:03:41 UTC
That's basically what I did to verify it as well.
Port 22 is still open on the firewall, but since sshd is not
running it doesn't pose a security risk.
All other firewall ports were closed except a port required for
DHCPv6 to work, which I thought was fair enough since we want that
for IPv6 users.
So yes, that's sufficient to verify it IMHO.
(In reply to Richard W.M. Jones from comment #5)
> That's basically what I did to verify it as well.
>
> Port 22 is still open on the firewall, but since sshd is not
> running it doesn't pose a security risk.
>
> All other firewall ports were closed except a port required for
> DHCPv6 to work, which I thought was fair enough since we want that
> for IPv6 users.
>
> So yes, that's sufficient to verify it IMHO.
Thanks,move this bug to VERIFIED.
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/RHBA-2015-2183.html