Bug 1382411

Summary:	[TEXT] PKI AIA Validation points to a non existent web page
Product:	[oVirt] ovirt-engine	Reporter:	Sandro Bonazzola <sbonazzo>
Component:	Tools.Rename	Assignee:	Lev Veyde <lveyde>
Status:	CLOSED CURRENTRELEASE	QA Contact:	David Necpal <dnecpal>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.0.4.4	CC:	bugs, lsvaty, lveyde, sbonazzo, ylavi
Target Milestone:	ovirt-4.2.0	Flags:	ylavi: ovirt-4.2+ lsvaty: testing_ack+
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 11:07:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sandro Bonazzola 2016-10-06 15:23:19 UTC

Description of problem:
ovirt-engine/packaging/setup/plugins/ovirt-engine-rename/ovirt-engine/pky.py
contains a check against AIA CA extension.
It points to http://www.ovirt.org/Changing_Engine_Hostname for further details but the page doesn't exist anymore on the new website.

While at it, please check if that code is still relevant.

Version-Release number of selected component (if applicable):
4.0.4.4

Comment 1 David Necpal 2017-09-04 16:15:52 UTC

Can you please provide verification steps?

Comment 2 Sandro Bonazzola 2017-09-20 09:03:23 UTC

The patch fixes the URL pointing to https://www.ovirt.org/documentation/how-to/networking/changing-engine-hostname/ which I can confirm exists today.

As additional verification, you can check that the procedure at this URL still work.

Comment 3 David Necpal 2017-09-20 16:10:22 UTC

Verified on version: 
ovirt-engine-4.2.0-0.0.master.20170919164122.gitefcfffc.el7.centos.noarch

Comment 4 Sandro Bonazzola 2017-12-20 11:07:12 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.