I just ran "./setup-ds-admin.pl" on a Fedora 20 virtual machine that was created from using "fedup" on a Fedora 19 virtual machine.
I used all defaults (with the exception of an Administration port of 29000), and it ended with the following:
The interactive phase is complete. The script will now set up your servers. Enter No or go Back if you want to change something. Are you ready to set up your servers? [yes]: Creating directory server . . . Your new DS instance 'dogtag20' was successfully created. Creating the configuration directory server . . . Can't use string ("/usr/share/dirsrv/inf/setup.inf") as a HASH ref while "strict refs" in use at /usr/lib64/dirsrv/perl/DSUtil.pm line 864.
What were the command line arguments to fedup on f19? I just used
fedup --network 20
and it gave me an error - Error: can't get boot images
I believe that Matt used these steps:
Create an F19 machine. In my case, I created a VM in the IDM lab using the f19-developer-template. If you guys have not used the IDM lab, I strongly recommend it.
Add the following file: /etc/yum.repos.d/rhel20.repo
[fedora20] name=Fedora 20 - $basearch failovermethod=priority baseurl=http://download.fedoraproject.org/pub/fedora/linux/development/20/$basearch/os/ mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-20&arch=$basearch enabled=1
gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch
[fedora20-debuginfo] name=Fedora 20 - $basearch - Debug failovermethod=priority baseurl=http://download.fedoraproject.org/pub/fedora/linux/development/20/$basearch/debug/ mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-debug-20&arch=$basearch enabled=0 metadata_expire=7d gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch
[fedora20-source] name=Fedora 20 - Source failovermethod=priority baseurl=http://download.fedoraproject.org/pub/fedora/linux/development/20/source/SRPMS/ mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-source-20&arch=$basearch enabled=0 metadata_expire=7d gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch
I followed those instructions with a few changes (for example, it is easier if you install '''fedup''' before adding the '''fedora20''' repo).
I completely updated my Fedora 19 machine (which contains NFS mounts and utilizes Kerberos/NIS logins) and created a clone of it to be used as my Fedora 20 machine. I then performed the following actions:
'fedup-0.7.3-4.fc19.noarch' will be installed }}}
[fedora20-source] name=Fedora 20 - Source failovermethod=priority baseurl=http://download.fedoraproject.org/pub/fedora/linux/development/20/source/SRPMS/ mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=fedora-source-20&arch=$basearch enabled=0 metadata_expire=7d gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-$basearch }}}
Permissive }}}
}}}
I did have to fix some inconsistencies so that I could simultaneously run my new Fedora 20 machine as well as the Fedora 19 machine from which it was cloned.
Additionally, I did update the following SELinux files (which were not in the yum repo): {{{
selinux-policy-devel-3.12.1-79.fc20.noarch.rpm selinux-policy-targeted-3.12.1-79.fc20.noarch.rpm
(should successfully dump all of the "SELinux Port Type/Proto/Port Number") }}}
{{{ NOTE: After uninstalling things using './remove-ds-admin.pl', removing the '/etc/dirsrv/slapd-<instance>.removed/' directory, and re-installing using './setup-ds-admin.pl', I did not see this issue. }}}
0001-Ticket-47515-Fedora-20-setup-ds-admin.pl.patch 0001-Ticket-47515-Fedora-20-setup-ds-admin.pl.patch
To ssh://git.fedorahosted.org/git/389/ds.git c98d500..31480d9 master -> master commit 31480d9 Author: Rich Megginson rmeggins@redhat.com Date: Mon Oct 7 15:18:12 2013 -0600
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1205365
Metadata Update from @nkinder: - Issue assigned to rmeggins - Issue set to the milestone: 1.3.2 - 09/13 (September)
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/852
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.