Hi there,
I’m just learning RMT and I’ve got a question. I’ve got an RMT Server running on SLES 15 SP1 (FQDN: [COLOR="#008000"]nsi-rmt.netsysint.net[/COLOR]). And I’m trying to install a SLES 12 SP4 server using RMT for the client’s product registration and repositories.
When I specify regurl=https://nsi-rmt.netsysint.net/ as a boot parameter when starting the installation, I see that the client obtains the certificate from nsi-rmt but then errors stating that no product repository can be found for SLES 12 SP4. However if I do the installation and don’t specify any boot parameters and select to register against a local RMT server and specify the same URL as on the regurl parameter, it works.
I thought that using the “regurl=” parameter and specifying that same RMT server on the Registration installation screen were different ways to do the same thing. Am I completely off-base here - are they not used for the same purpose?
Thanks Rich…
[QUOTE=rich_hanley;58141]Hi there,
I’m just learning RMT and I’ve got a question. I’ve got an RMT Server running on SLES 15 SP1 (FQDN: [COLOR="#008000"]nsi-rmt.netsysint.net[/COLOR]). And I’m trying to install a SLES 12 SP4 server using RMT for the client’s product registration and repositories.
When I specify regurl=https://nsi-rmt.netsysint.net/ as a boot parameter when starting the installation, I see that the client obtains the certificate from nsi-rmt but then errors stating that no product repository can be found for SLES 12 SP4. However if I do the installation and don’t specify any boot parameters and select to register against a local RMT server and specify the same URL as on the regurl parameter, it works.
I thought that using the “regurl=” parameter and specifying that same RMT server on the Registration installation screen were different ways to do the same thing. Am I completely off-base here - are they not used for the same purpose?
Thanks Rich…[/QUOTE]
Hi
According to the documentation, yes 
So you can browse here https://RMT_SERVER/ ok? Do you see the subdirectories including a ‘product’ one for SLE 12 SP4?
Thanks for the reply Malcolm!
If I browse to [COLOR="#008000"]https://nsi-rmt.netsysint.net[/COLOR] I get connected to [COLOR="#008000"]nsi-rmt[/COLOR]; however the page is blank. But I can browse down into [COLOR="#008000"]repo/SUSE/Products/SLE-SERVER/12-SP4/x86_64/product[/COLOR] and see the directories for [COLOR="#008000"]noarch[/COLOR], [COLOR="#008000"]repodata[/COLOR], and[COLOR="#008000"] x86_64[/COLOR] (which contains all the rpms). What I don’t understand is why I can go through the YaST based install (using no boot parameters) get to the registration screen and enter simply: [COLOR="#008000"]https://nsi-rmt.netsysint.net[/COLOR] and it works. I don’t understand how the value for the regurl boot parameter seems to be much more “literal” than what I specify at the YaST Registration Screen?
Thanks,
Rich…
[QUOTE=rich_hanley;58150]Thanks for the reply Malcolm!
If I browse to [COLOR="#008000"]https://nsi-rmt.netsysint.net[/COLOR] I get connected to [COLOR="#008000"]nsi-rmt[/COLOR]; however the page is blank. But I can browse down into [COLOR="#008000"]repo/SUSE/Products/SLE-SERVER/12-SP4/x86_64/product[/COLOR] and see the directories for [COLOR="#008000"]noarch[/COLOR], [COLOR="#008000"]repodata[/COLOR], and[COLOR="#008000"] x86_64[/COLOR] (which contains all the rpms). What I don’t understand is why I can go through the YaST based install (using no boot parameters) get to the registration screen and enter simply: [COLOR="#008000"]https://nsi-rmt.netsysint.net[/COLOR] and it works. I don’t understand how the value for the regurl boot parameter seems to be much more “literal” than what I specify at the YaST Registration Screen?
Thanks,
Rich…[/QUOTE]
Hi
I would have thought it needs the extra part of the url (repo/SUSE/Products/SLE-SERVER/12-SP4/), maybe a bug?