#47494 RFE : Upgrade of Passsync should display a warning message as existing passsync will be upgraded.
Closed: wontfix None Opened 10 years ago by rmeggins.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Directory Server): Bug 986856

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem: When upgrading the existing version of Passsync on
windows, it just blindly upgrades the existing component. It doesn't display
any error/warning message as the existing version will be upgraded.

Version-Release number of selected component (if applicable):
RedHat-PassSync-1.1.5


How reproducible: Consistently


Steps to Reproduce:
1. Install passsync-1.1.4 version from - http://wiki.idm.lab.bos.redhat.com/sha
re/builds/components/winsync/passsync/20100512.1/release/
2. Upgrade the Passsync component by installing the newer version of
Passsync-1.1.5
3. Upgrade of Passsync successful. But, the installation should give a warning
message as "Existing version of Passsync will be upgraded", and it should ask
the user to select whether you want to continue "Yes" or "No".

Actual results: No message displayed.

Expected results: Upgrade of passsync should give a warning message as
"Existing version of Passsync will be upgraded", and it should ask the user to
select whether you want to continue "Yes" or "No".


Additional info:

Per triage, no plan to fix this.

Metadata Update from @nhosoi:
- Issue set to the milestone: FUTURE

7 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/831

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Invalid)

3 years ago

Login to comment on this ticket.

Metadata