Hello all One of my servers has an internal and an external ip address. The hostname belongs to the external address, while the prometheus server should connect to the internal address. myserver.domain.com -> 10.0.0.1 external example myserver.domain -> 192.168.0.1 internal example Hostname defined in Uyuni = myserver.domain.com IP Address defined in Uyuni = 192.168.0.1 The server has only one ip - the external ip ends on the firewall (NAT) and is forwarded to the internal ip. When I activate the prometheus node exporter formula on this server, the prometheus server tries to connect the external ip with this error: Get "http://myserver.domain.com:9100/metrics": dial tcp 10.0.0.1:9100: connect: connection refused What can I do to change the connection string to: http://myserver.domain:9100/metrics or http://192.168.0.1:9100/metrics that is accessible from the prometheus server? I tried to change the prometheus_exporter Address: field from :9100 to myserver.domain:9100 and the Argument field from --web.listen-address=":9100" to --web.listen-address="myserver.domain:9100", but that changes nothing. The prometheus server catches the mgr-clients from the uyuni server: # -------------------- # Auto discover clients of uyuni # -------------------- - job_name: 'mgr-clients' uyuni_sd_configs: - host: https://uyuni.domain username: admin password: <password> Same problem with the apache Exporter :) Some ideas? Best regards Martin
On 4/21/21 1:25 PM, Martin Willisegger wrote:
Hello all
One of my servers has an internal and an external ip address. The hostname belongs to the external address, while the prometheus server should connect to the internal address.
myserver.domain.com -> 10.0.0.1 external example myserver.domain -> 192.168.0.1 internal example Hostname defined in Uyuni = myserver.domain.com IP Address defined in Uyuni = 192.168.0.1
The server has only one ip - the external ip ends on the firewall (NAT) and is forwarded to the internal ip.
When I activate the prometheus node exporter formula on this server, the prometheus server tries to connect the external ip with this error:
Get "http://myserver.domain.com:9100/metrics": dial tcp 10.0.0.1:9100: connect: connection refused
What can I do to change the connection string to:
http://myserver.domain:9100/metrics or http://192.168.0.1:9100/metrics
that is accessible from the prometheus server?
Hi Martin, please try setting the primary FQDN in `System > Details > Hardware > Networking`. The feature is being released in Uyuni 2021.04 (released but not announced yet). Hope it helps. Witek
On miércoles, 21 de abril de 2021 15:07:27 (CEST) Witek Bedyk wrote:
On 4/21/21 1:25 PM, Martin Willisegger wrote:
Hello all
One of my servers has an internal and an external ip address. The hostname belongs to the external address, while the prometheus server should connect to the internal address.
myserver.domain.com -> 10.0.0.1 external example myserver.domain -> 192.168.0.1 internal example Hostname defined in Uyuni = myserver.domain.com IP Address defined in Uyuni = 192.168.0.1
The server has only one ip - the external ip ends on the firewall (NAT) and is forwarded to the internal ip.
When I activate the prometheus node exporter formula on this server, the prometheus server tries to connect the external ip with this error:
Get "http://myserver.domain.com:9100/metrics": dial tcp 10.0.0.1:9100: connect: connection refused
What can I do to change the connection string to:
http://myserver.domain:9100/metrics or http://192.168.0.1:9100/metrics
that is accessible from the prometheus server?
Hi Martin,
please try setting the primary FQDN in `System > Details > Hardware > Networking`. The feature is being released in Uyuni 2021.04 (released but not announced yet).
Seems this wasn't noticed when the release notes were reviewed by the team, so this feature is in 2021.04, but will show at the release notes for the next release. Sorry about the inconvenience.
Hope it helps. Witek
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
Hello Witek I still use 2021.03. There is also no upgrade after zypper refresh available at: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable/... In 2021.03 - there is a selection filed with myserver.domain.com but no entry with myserver.domain, so I can't select the right option. It is also not possible to add an own value. What is the data source for that selection field? Best regards Martin Am 21.04.21 um 15:07 schrieb Witek Bedyk:
On 4/21/21 1:25 PM, Martin Willisegger wrote:
Hello all
One of my servers has an internal and an external ip address. The hostname belongs to the external address, while the prometheus server should connect to the internal address.
myserver.domain.com -> 10.0.0.1 external example myserver.domain -> 192.168.0.1 internal example Hostname defined in Uyuni = myserver.domain.com IP Address defined in Uyuni = 192.168.0.1
The server has only one ip - the external ip ends on the firewall (NAT) and is forwarded to the internal ip.
When I activate the prometheus node exporter formula on this server, the prometheus server tries to connect the external ip with this error:
Get "http://myserver.domain.com:9100/metrics": dial tcp 10.0.0.1:9100: connect: connection refused
What can I do to change the connection string to:
http://myserver.domain:9100/metrics or http://192.168.0.1:9100/metrics
that is accessible from the prometheus server?
Hi Martin,
please try setting the primary FQDN in `System > Details > Hardware > Networking`. The feature is being released in Uyuni 2021.04 (released but not announced yet).
Hope it helps. Witek
On jueves, 22 de abril de 2021 11:14:23 (CEST) Martin Willisegger <Martin Willisegger wrote:
Hello Witek
I still use 2021.03. There is also no upgrade after zypper refresh available at: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable/ images/repo/Uyuni-Server-POOL-x86_64-Media1/
Warning: 2021.03 was never released as Stable, that was only at Master. Maybe you mean you are using 2021.02? About no upgrade about zypper refresh, seems we had a problem with the release at OBS, and I am now talking to the OBS experts to fix it. Meanwhile that repo still has 2021.02, so it won't break any installations. It's just that you can get 2021.04 yet. I will post an update to Twitter, Mailing lists and gitter as soon as we have this fixed. Sorry about the inconvenience.
In 2021.03 - there is a selection filed with myserver.domain.com but no entry with myserver.domain, so I can't select the right option. It is also not possible to add an own value. What is the data source for that selection field?
Best regards
Martin
Am 21.04.21 um 15:07 schrieb Witek Bedyk:
On 4/21/21 1:25 PM, Martin Willisegger wrote:
Hello all
One of my servers has an internal and an external ip address. The hostname belongs to the external address, while the prometheus server should connect to the internal address.
myserver.domain.com -> 10.0.0.1 external example myserver.domain -> 192.168.0.1 internal example Hostname defined in Uyuni = myserver.domain.com IP Address defined in Uyuni = 192.168.0.1
The server has only one ip - the external ip ends on the firewall (NAT) and is forwarded to the internal ip.
When I activate the prometheus node exporter formula on this server, the prometheus server tries to connect the external ip with this error:
Get "http://myserver.domain.com:9100/metrics": dial tcp 10.0.0.1:9100: connect: connection refused
What can I do to change the connection string to:
http://myserver.domain:9100/metrics or http://192.168.0.1:9100/metrics
that is accessible from the prometheus server?
Hi Martin,
please try setting the primary FQDN in `System > Details > Hardware > Networking`. The feature is being released in Uyuni 2021.04 (released but not announced yet).
Hope it helps. Witek
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
Hello Julio When I did a zypper refresh and zypper dup yesterday with the repository below some patches were installed and after a reboot the web GUI showed version 2021.03. I did not actively search for and install a beta version but used the normal upstream. Isn't the repository given the official location for uyuni upgrades? Best regards Martin Am 22.04.21 um 12:29 schrieb Julio González Gil:
On jueves, 22 de abril de 2021 11:14:23 (CEST) Martin Willisegger <Martin Willisegger wrote:
Hello Witek
I still use 2021.03. There is also no upgrade after zypper refresh available at: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable/ images/repo/Uyuni-Server-POOL-x86_64-Media1/ Warning: 2021.03 was never released as Stable, that was only at Master. Maybe you mean you are using 2021.02?
About no upgrade about zypper refresh, seems we had a problem with the release at OBS, and I am now talking to the OBS experts to fix it.
Meanwhile that repo still has 2021.02, so it won't break any installations. It's just that you can get 2021.04 yet.
I will post an update to Twitter, Mailing lists and gitter as soon as we have this fixed.
Sorry about the inconvenience.
In 2021.03 - there is a selection filed with myserver.domain.com but no entry with myserver.domain, so I can't select the right option. It is also not possible to add an own value. What is the data source for that selection field?
Best regards
Martin
Am 21.04.21 um 15:07 schrieb Witek Bedyk:
On 4/21/21 1:25 PM, Martin Willisegger wrote:
Hello all
One of my servers has an internal and an external ip address. The hostname belongs to the external address, while the prometheus server should connect to the internal address.
myserver.domain.com -> 10.0.0.1 external example myserver.domain -> 192.168.0.1 internal example Hostname defined in Uyuni = myserver.domain.com IP Address defined in Uyuni = 192.168.0.1
The server has only one ip - the external ip ends on the firewall (NAT) and is forwarded to the internal ip.
When I activate the prometheus node exporter formula on this server, the prometheus server tries to connect the external ip with this error:
Get "http://myserver.domain.com:9100/metrics": dial tcp 10.0.0.1:9100: connect: connection refused
What can I do to change the connection string to:
http://myserver.domain:9100/metrics or http://192.168.0.1:9100/metrics
that is accessible from the prometheus server? Hi Martin,
please try setting the primary FQDN in `System > Details > Hardware > Networking`. The feature is being released in Uyuni 2021.04 (released but not announced yet).
Hope it helps. Witek
https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable/... Is the official Stable version, yes. But I the WebUI is controlled by spacewalk-web: https://build.opensuse.org/package/revisions/systemsmanagement:Uyuni:Stable/... And checking the OBS cpio files I don't see 2021.03 anywhere at any of the spacewalk-web/conf/rhn_web.conf files. Rev62 was 2021.02, and Rev63 (yesterday) jumps to 2021.04 2021.03 was only on Master, so I am not sure how you get it. Can you run "zypper info spacewalk-web" and "rpm -qa|grep spacewalk-web"? On jueves, 22 de abril de 2021 14:30:02 (CEST) Martin Willisegger wrote:
Hello Julio
When I did a zypper refresh and zypper dup yesterday with the repository below some patches were installed and after a reboot the web GUI showed version 2021.03. I did not actively search for and install a beta version but used the normal upstream.
Isn't the repository given the official location for uyuni upgrades?
Best regards
Martin
Am 22.04.21 um 12:29 schrieb Julio González Gil:
On jueves, 22 de abril de 2021 11:14:23 (CEST) Martin Willisegger <Martin
Willisegger wrote:
Hello Witek
I still use 2021.03. There is also no upgrade after zypper refresh available at: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stab le/ images/repo/Uyuni-Server-POOL-x86_64-Media1/
Warning: 2021.03 was never released as Stable, that was only at Master. Maybe you mean you are using 2021.02?
About no upgrade about zypper refresh, seems we had a problem with the release at OBS, and I am now talking to the OBS experts to fix it.
Meanwhile that repo still has 2021.02, so it won't break any installations. It's just that you can get 2021.04 yet.
I will post an update to Twitter, Mailing lists and gitter as soon as we have this fixed.
Sorry about the inconvenience.
In 2021.03 - there is a selection filed with myserver.domain.com but no entry with myserver.domain, so I can't select the right option. It is also not possible to add an own value. What is the data source for that selection field?
Best regards
Martin
Am 21.04.21 um 15:07 schrieb Witek Bedyk:
On 4/21/21 1:25 PM, Martin Willisegger wrote:
Hello all
One of my servers has an internal and an external ip address. The hostname belongs to the external address, while the prometheus server should connect to the internal address.
myserver.domain.com -> 10.0.0.1 external example myserver.domain -> 192.168.0.1 internal example Hostname defined in Uyuni = myserver.domain.com IP Address defined in Uyuni = 192.168.0.1
The server has only one ip - the external ip ends on the firewall (NAT) and is forwarded to the internal ip.
When I activate the prometheus node exporter formula on this server, the prometheus server tries to connect the external ip with this error:
Get "http://myserver.domain.com:9100/metrics": dial tcp 10.0.0.1:9100: connect: connection refused
What can I do to change the connection string to:
http://myserver.domain:9100/metrics or http://192.168.0.1:9100/metrics
that is accessible from the prometheus server?
Hi Martin,
please try setting the primary FQDN in `System > Details > Hardware > Networking`. The feature is being released in Uyuni 2021.04 (released but not announced yet).
Hope it helps. Witek
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
I can't find spacewalk-web package on server, at least on my 15.2 instalation Cristian Gherman On 4/22/21 4:39 PM, Julio González Gil wrote:
https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable/...
Is the official Stable version, yes. But I the WebUI is controlled by spacewalk-web:
https://build.opensuse.org/package/revisions/systemsmanagement:Uyuni:Stable/...
And checking the OBS cpio files I don't see 2021.03 anywhere at any of the spacewalk-web/conf/rhn_web.conf files.
Rev62 was 2021.02, and Rev63 (yesterday) jumps to 2021.04
2021.03 was only on Master, so I am not sure how you get it.
Can you run "zypper info spacewalk-web" and "rpm -qa|grep spacewalk-web"?
On jueves, 22 de abril de 2021 14:30:02 (CEST) Martin Willisegger wrote:
Hello Julio
When I did a zypper refresh and zypper dup yesterday with the repository below some patches were installed and after a reboot the web GUI showed version 2021.03. I did not actively search for and install a beta version but used the normal upstream.
Isn't the repository given the official location for uyuni upgrades?
Best regards
Martin
Am 22.04.21 um 12:29 schrieb Julio González Gil:
On jueves, 22 de abril de 2021 11:14:23 (CEST) Martin Willisegger <Martin
Willisegger wrote:
Hello Witek
I still use 2021.03. There is also no upgrade after zypper refresh available at: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stab le/ images/repo/Uyuni-Server-POOL-x86_64-Media1/ Warning: 2021.03 was never released as Stable, that was only at Master. Maybe you mean you are using 2021.02?
About no upgrade about zypper refresh, seems we had a problem with the release at OBS, and I am now talking to the OBS experts to fix it.
Meanwhile that repo still has 2021.02, so it won't break any installations. It's just that you can get 2021.04 yet.
I will post an update to Twitter, Mailing lists and gitter as soon as we have this fixed.
Sorry about the inconvenience.
In 2021.03 - there is a selection filed with myserver.domain.com but no entry with myserver.domain, so I can't select the right option. It is also not possible to add an own value. What is the data source for that selection field?
Best regards
Martin
Am 21.04.21 um 15:07 schrieb Witek Bedyk:
On 4/21/21 1:25 PM, Martin Willisegger wrote:
Hello all
One of my servers has an internal and an external ip address. The hostname belongs to the external address, while the prometheus server should connect to the internal address.
myserver.domain.com -> 10.0.0.1 external example myserver.domain -> 192.168.0.1 internal example Hostname defined in Uyuni = myserver.domain.com IP Address defined in Uyuni = 192.168.0.1
The server has only one ip - the external ip ends on the firewall (NAT) and is forwarded to the internal ip.
When I activate the prometheus node exporter formula on this server, the prometheus server tries to connect the external ip with this error:
Get "http://myserver.domain.com:9100/metrics": dial tcp 10.0.0.1:9100: connect: connection refused
What can I do to change the connection string to:
http://myserver.domain:9100/metrics or http://192.168.0.1:9100/metrics
that is accessible from the prometheus server? Hi Martin,
please try setting the primary FQDN in `System > Details > Hardware > Networking`. The feature is being released in Uyuni 2021.04 (released but not announced yet).
Hope it helps. Witek
On jueves, 22 de abril de 2021 15:57:00 (CEST) Cristian Gherman wrote:
I can't find spacewalk-web package on server, at least on my 15.2 instalation
True, that's the name for the source package, and in this case it seems we don't install a binary with that name. My mistake :-) In the end: /usr/share/rhn/config-defaults/rhn_web.conf Is owned by: spacewalk-base-minimal-config Whi currently at stable (because of the publishing problem I just announced it still contains 2021.02) is: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable/... And shows that indeed it contains '2021.03' which is a typo, and shows that Martin Willisegger was right, and nothing is wrong with his setup. Seems that with all the back and forth to integrate the salt CVE fixes, we got this typo included, as 2021.02 was released on 2021/03/01 (and originally we thought about releasing it 2021.02 as 2021.03) Nothing to worry about. It's just cosmetic.
Cristian Gherman
On 4/22/21 4:39 PM, Julio González Gil wrote:
https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stabl e/images/repo/Uyuni-Server-POOL-x86_64-Media1/
Is the official Stable version, yes. But I the WebUI is controlled by spacewalk-web:
https://build.opensuse.org/package/revisions/systemsmanagement:Uyuni:Stabl e/spacewalk-web
And checking the OBS cpio files I don't see 2021.03 anywhere at any of the spacewalk-web/conf/rhn_web.conf files.
Rev62 was 2021.02, and Rev63 (yesterday) jumps to 2021.04
2021.03 was only on Master, so I am not sure how you get it.
Can you run "zypper info spacewalk-web" and "rpm -qa|grep spacewalk-web"?
On jueves, 22 de abril de 2021 14:30:02 (CEST) Martin Willisegger wrote:
Hello Julio
When I did a zypper refresh and zypper dup yesterday with the repository below some patches were installed and after a reboot the web GUI showed version 2021.03. I did not actively search for and install a beta version but used the normal upstream.
Isn't the repository given the official location for uyuni upgrades?
Best regards
Martin
Am 22.04.21 um 12:29 schrieb Julio González Gil:
On jueves, 22 de abril de 2021 11:14:23 (CEST) Martin Willisegger <Martin
Willisegger wrote:
Hello Witek
I still use 2021.03. There is also no upgrade after zypper refresh available at: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/St ab le/ images/repo/Uyuni-Server-POOL-x86_64-Media1/
Warning: 2021.03 was never released as Stable, that was only at Master. Maybe you mean you are using 2021.02?
About no upgrade about zypper refresh, seems we had a problem with the release at OBS, and I am now talking to the OBS experts to fix it.
Meanwhile that repo still has 2021.02, so it won't break any installations. It's just that you can get 2021.04 yet.
I will post an update to Twitter, Mailing lists and gitter as soon as we have this fixed.
Sorry about the inconvenience.
In 2021.03 - there is a selection filed with myserver.domain.com but no entry with myserver.domain, so I can't select the right option. It is also not possible to add an own value. What is the data source for that selection field?
Best regards
Martin
Am 21.04.21 um 15:07 schrieb Witek Bedyk:
On 4/21/21 1:25 PM, Martin Willisegger wrote: > Hello all > > One of my servers has an internal and an external ip address. The > hostname belongs to the external address, while the prometheus server > should connect to the internal address. > > myserver.domain.com -> 10.0.0.1 external example > myserver.domain -> 192.168.0.1 internal example > Hostname defined in Uyuni = myserver.domain.com > IP Address defined in Uyuni = 192.168.0.1 > > The server has only one ip - the external ip ends on the firewall > (NAT) > and is forwarded to the internal ip. > > When I activate the prometheus node exporter formula on this server, > the > prometheus server tries to connect the external ip with this error: > > Get "http://myserver.domain.com:9100/metrics": dial tcp > 10.0.0.1:9100: > connect: connection refused > > What can I do to change the connection string to: > > http://myserver.domain:9100/metrics or > http://192.168.0.1:9100/metrics > > that is accessible from the prometheus server?
Hi Martin,
please try setting the primary FQDN in `System > Details > Hardware > Networking`. The feature is being released in Uyuni 2021.04 (released but not announced yet).
Hope it helps. Witek
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
After a successful update to 2021.04, the desired FQDN can unfortunately still not be selected or added (System -> Hardware -> Networking). Where does the data in the selection field come from? Best regards Martin Am 22.04.21 um 16:29 schrieb Julio González Gil:
On jueves, 22 de abril de 2021 15:57:00 (CEST) Cristian Gherman wrote:
I can't find spacewalk-web package on server, at least on my 15.2 instalation True, that's the name for the source package, and in this case it seems we don't install a binary with that name. My mistake :-)
In the end:
/usr/share/rhn/config-defaults/rhn_web.conf
Is owned by:
spacewalk-base-minimal-config
Whi currently at stable (because of the publishing problem I just announced it still contains 2021.02) is:
https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable/...
And shows that indeed it contains '2021.03' which is a typo, and shows that Martin Willisegger was right, and nothing is wrong with his setup.
Seems that with all the back and forth to integrate the salt CVE fixes, we got this typo included, as 2021.02 was released on 2021/03/01 (and originally we thought about releasing it 2021.02 as 2021.03)
Nothing to worry about. It's just cosmetic.
Cristian Gherman
On 4/22/21 4:39 PM, Julio González Gil wrote:
https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stabl e/images/repo/Uyuni-Server-POOL-x86_64-Media1/
Is the official Stable version, yes. But I the WebUI is controlled by spacewalk-web:
https://build.opensuse.org/package/revisions/systemsmanagement:Uyuni:Stabl e/spacewalk-web
And checking the OBS cpio files I don't see 2021.03 anywhere at any of the spacewalk-web/conf/rhn_web.conf files.
Rev62 was 2021.02, and Rev63 (yesterday) jumps to 2021.04
2021.03 was only on Master, so I am not sure how you get it.
Can you run "zypper info spacewalk-web" and "rpm -qa|grep spacewalk-web"?
On jueves, 22 de abril de 2021 14:30:02 (CEST) Martin Willisegger wrote:
Hello Julio
When I did a zypper refresh and zypper dup yesterday with the repository below some patches were installed and after a reboot the web GUI showed version 2021.03. I did not actively search for and install a beta version but used the normal upstream.
Isn't the repository given the official location for uyuni upgrades?
Best regards
Martin
Am 22.04.21 um 12:29 schrieb Julio González Gil:
On jueves, 22 de abril de 2021 11:14:23 (CEST) Martin Willisegger <Martin
Willisegger wrote:
Hello Witek
I still use 2021.03. There is also no upgrade after zypper refresh available at: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/St ab le/ images/repo/Uyuni-Server-POOL-x86_64-Media1/ Warning: 2021.03 was never released as Stable, that was only at Master. Maybe you mean you are using 2021.02?
About no upgrade about zypper refresh, seems we had a problem with the release at OBS, and I am now talking to the OBS experts to fix it.
Meanwhile that repo still has 2021.02, so it won't break any installations. It's just that you can get 2021.04 yet.
I will post an update to Twitter, Mailing lists and gitter as soon as we have this fixed.
Sorry about the inconvenience.
In 2021.03 - there is a selection filed with myserver.domain.com but no entry with myserver.domain, so I can't select the right option. It is also not possible to add an own value. What is the data source for that selection field?
Best regards
Martin
Am 21.04.21 um 15:07 schrieb Witek Bedyk: > On 4/21/21 1:25 PM, Martin Willisegger wrote: >> Hello all >> >> One of my servers has an internal and an external ip address. The >> hostname belongs to the external address, while the prometheus server >> should connect to the internal address. >> >> myserver.domain.com -> 10.0.0.1 external example >> myserver.domain -> 192.168.0.1 internal example >> Hostname defined in Uyuni = myserver.domain.com >> IP Address defined in Uyuni = 192.168.0.1 >> >> The server has only one ip - the external ip ends on the firewall >> (NAT) >> and is forwarded to the internal ip. >> >> When I activate the prometheus node exporter formula on this server, >> the >> prometheus server tries to connect the external ip with this error: >> >> Get "http://myserver.domain.com:9100/metrics": dial tcp >> 10.0.0.1:9100: >> connect: connection refused >> >> What can I do to change the connection string to: >> >> http://myserver.domain:9100/metrics or >> http://192.168.0.1:9100/metrics >> >> that is accessible from the prometheus server? > Hi Martin, > > please try setting the primary FQDN in `System > Details > Hardware > > Networking`. The feature is being released in Uyuni 2021.04 (released > but not announced yet). > > Hope it helps. > Witek
Witek, any of why is it happening? Was the patch really included in 2021.04? On viernes, 23 de abril de 2021 16:42:23 (CEST) Martin Willisegger wrote:
After a successful update to 2021.04, the desired FQDN can unfortunately still not be selected or added (System -> Hardware -> Networking).
Where does the data in the selection field come from?
Best regards Martin
Am 22.04.21 um 16:29 schrieb Julio González Gil:
On jueves, 22 de abril de 2021 15:57:00 (CEST) Cristian Gherman wrote:
I can't find spacewalk-web package on server, at least on my 15.2 instalation
True, that's the name for the source package, and in this case it seems we don't install a binary with that name. My mistake :-)
In the end:
/usr/share/rhn/config-defaults/rhn_web.conf
Is owned by:
spacewalk-base-minimal-config
Whi currently at stable (because of the publishing problem I just announced it still contains 2021.02) is:
https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stabl e/images/repo/Uyuni-Server-POOL-x86_64-Media1/noarch/spacewalk-base-minima l-config-4.2.11-1.2.uyuni.noarch.rpm
And shows that indeed it contains '2021.03' which is a typo, and shows that Martin Willisegger was right, and nothing is wrong with his setup.
Seems that with all the back and forth to integrate the salt CVE fixes, we got this typo included, as 2021.02 was released on 2021/03/01 (and originally we thought about releasing it 2021.02 as 2021.03)
Nothing to worry about. It's just cosmetic.
Cristian Gherman
On 4/22/21 4:39 PM, Julio González Gil wrote:
https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Sta bl e/images/repo/Uyuni-Server-POOL-x86_64-Media1/
Is the official Stable version, yes. But I the WebUI is controlled by spacewalk-web:
https://build.opensuse.org/package/revisions/systemsmanagement:Uyuni:Sta bl e/spacewalk-web
And checking the OBS cpio files I don't see 2021.03 anywhere at any of the spacewalk-web/conf/rhn_web.conf files.
Rev62 was 2021.02, and Rev63 (yesterday) jumps to 2021.04
2021.03 was only on Master, so I am not sure how you get it.
Can you run "zypper info spacewalk-web" and "rpm -qa|grep spacewalk-web"?
On jueves, 22 de abril de 2021 14:30:02 (CEST) Martin Willisegger wrote:
Hello Julio
When I did a zypper refresh and zypper dup yesterday with the repository below some patches were installed and after a reboot the web GUI showed version 2021.03. I did not actively search for and install a beta version but used the normal upstream.
Isn't the repository given the official location for uyuni upgrades?
Best regards
Martin
Am 22.04.21 um 12:29 schrieb Julio González Gil:
On jueves, 22 de abril de 2021 11:14:23 (CEST) Martin Willisegger <Martin
Willisegger wrote: > Hello Witek > > I still use 2021.03. There is also no upgrade after zypper refresh > available at: > https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/ > St > ab > le/ images/repo/Uyuni-Server-POOL-x86_64-Media1/
Warning: 2021.03 was never released as Stable, that was only at Master. Maybe you mean you are using 2021.02?
About no upgrade about zypper refresh, seems we had a problem with the release at OBS, and I am now talking to the OBS experts to fix it.
Meanwhile that repo still has 2021.02, so it won't break any installations. It's just that you can get 2021.04 yet.
I will post an update to Twitter, Mailing lists and gitter as soon as we have this fixed.
Sorry about the inconvenience.
> In 2021.03 - there is a selection filed with myserver.domain.com but > no > entry with myserver.domain, so I can't select the right option. It is > also not possible to add an own value. What is the data source for > that > selection field? > > Best regards > > Martin > > Am 21.04.21 um 15:07 schrieb Witek Bedyk: >> On 4/21/21 1:25 PM, Martin Willisegger wrote: >>> Hello all >>> >>> One of my servers has an internal and an external ip address. The >>> hostname belongs to the external address, while the prometheus >>> server >>> should connect to the internal address. >>> >>> myserver.domain.com -> 10.0.0.1 external example >>> myserver.domain -> 192.168.0.1 internal example >>> Hostname defined in Uyuni = myserver.domain.com >>> IP Address defined in Uyuni = 192.168.0.1 >>> >>> The server has only one ip - the external ip ends on the firewall >>> (NAT) >>> and is forwarded to the internal ip. >>> >>> When I activate the prometheus node exporter formula on this >>> server, >>> the >>> prometheus server tries to connect the external ip with this error: >>> >>> Get "http://myserver.domain.com:9100/metrics": dial tcp >>> 10.0.0.1:9100: >>> connect: connection refused >>> >>> What can I do to change the connection string to: >>> >>> http://myserver.domain:9100/metrics or >>> http://192.168.0.1:9100/metrics >>> >>> that is accessible from the prometheus server? >> >> Hi Martin, >> >> please try setting the primary FQDN in `System > Details > Hardware >> > >> Networking`. The feature is being released in Uyuni 2021.04 >> (released >> but not announced yet). >> >> Hope it helps. >> Witek
-- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez@suse.com
Sorry but from my end on: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable/... last changes in in this folder are 8 March (for rpms and repodata) and in console: salt:~ # zypper lr -E -e - --- [uyuni-server-stable] name=Uyuni Server Stable enabled=1 autorefresh=0 baseurl=https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable/... type=rpm-md salt:~ # zypper in patterns-uyuni_server Loading repository data... Reading installed packages... 'patterns-uyuni_server' is already installed. No update candidate for 'patterns-uyuni_server-2021.02-2.1.uyuni.x86_64'. The highest available version is already installed. Resolving package dependencies... Nothing to do. Cristian Gherman On 4/22/21 4:39 PM, Julio González Gil wrote:
https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable/...
Is the official Stable version, yes. But I the WebUI is controlled by spacewalk-web:
https://build.opensuse.org/package/revisions/systemsmanagement:Uyuni:Stable/...
And checking the OBS cpio files I don't see 2021.03 anywhere at any of the spacewalk-web/conf/rhn_web.conf files.
Rev62 was 2021.02, and Rev63 (yesterday) jumps to 2021.04
2021.03 was only on Master, so I am not sure how you get it.
Can you run "zypper info spacewalk-web" and "rpm -qa|grep spacewalk-web"?
On jueves, 22 de abril de 2021 14:30:02 (CEST) Martin Willisegger wrote:
Hello Julio
When I did a zypper refresh and zypper dup yesterday with the repository below some patches were installed and after a reboot the web GUI showed version 2021.03. I did not actively search for and install a beta version but used the normal upstream.
Isn't the repository given the official location for uyuni upgrades?
Best regards
Martin
Am 22.04.21 um 12:29 schrieb Julio González Gil:
On jueves, 22 de abril de 2021 11:14:23 (CEST) Martin Willisegger <Martin
Willisegger wrote:
Hello Witek
I still use 2021.03. There is also no upgrade after zypper refresh available at: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stab le/ images/repo/Uyuni-Server-POOL-x86_64-Media1/ Warning: 2021.03 was never released as Stable, that was only at Master. Maybe you mean you are using 2021.02?
About no upgrade about zypper refresh, seems we had a problem with the release at OBS, and I am now talking to the OBS experts to fix it.
Meanwhile that repo still has 2021.02, so it won't break any installations. It's just that you can get 2021.04 yet.
I will post an update to Twitter, Mailing lists and gitter as soon as we have this fixed.
Sorry about the inconvenience.
In 2021.03 - there is a selection filed with myserver.domain.com but no entry with myserver.domain, so I can't select the right option. It is also not possible to add an own value. What is the data source for that selection field?
Best regards
Martin
Am 21.04.21 um 15:07 schrieb Witek Bedyk:
On 4/21/21 1:25 PM, Martin Willisegger wrote:
Hello all
One of my servers has an internal and an external ip address. The hostname belongs to the external address, while the prometheus server should connect to the internal address.
myserver.domain.com -> 10.0.0.1 external example myserver.domain -> 192.168.0.1 internal example Hostname defined in Uyuni = myserver.domain.com IP Address defined in Uyuni = 192.168.0.1
The server has only one ip - the external ip ends on the firewall (NAT) and is forwarded to the internal ip.
When I activate the prometheus node exporter formula on this server, the prometheus server tries to connect the external ip with this error:
Get "http://myserver.domain.com:9100/metrics": dial tcp 10.0.0.1:9100: connect: connection refused
What can I do to change the connection string to:
http://myserver.domain:9100/metrics or http://192.168.0.1:9100/metrics
that is accessible from the prometheus server? Hi Martin,
please try setting the primary FQDN in `System > Details > Hardware > Networking`. The feature is being released in Uyuni 2021.04 (released but not announced yet).
Hope it helps. Witek
participants (5)
-
Cristian Gherman -
Julio González Gil -
Martin Willisegger -
Martin Willisegger <Martin Willisegger
-
Witek Bedyk