-
|
hi, I restored a snapshot, so uyuni is up an running again, but I would love to get a hint, what is going wrong there :) thank you! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 13 replies
-
|
@1of16 when you were prompted for @mbussolotto FYI |
Beta Was this translation helpful? Give feedback.
-
|
ok, one step closer: we are getting closer :) |
Beta Was this translation helpful? Give feedback.
-
|
I would say you should look which image version is running on the main container, maybe it was not updated correctly. For the error it suggests that you have the new container with the database, but maybe the main container is still in the old version when it also have the database in there, and are using the same port. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
I think I've solved it now! note: the keys aren't encrypted!
and then I waited....and waited and then: EC Certificates aren't a problem, but your upgrade documentation could be a little bit improved :) thank you for your patients and tips! |
Beta Was this translation helpful? Give feedback.
-
|
Hi, this isn't working for me. I ran the commands to create the secrets and the new ones seem OL. The uyuni-ca/uyuni-db-ca are a combined intermediate+root CA bag. But I still get prompted for a CA key password, which I shouldn't have to do since I'm providing signed key/cert pairs and the CA certs to avoid that. ca07uyuni1:/home/itadmin # mgradm upgrade podman --logLevel=trace While SELinux is running, it doesn't seem to be the problem as the only selinux errors I see in the audit log have to do with the qemu guest agent. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your workings on this.
To the devs:
I’ve just attempted to upgrade Uyuni and hit the same problem as 1of16
The transactional-update went fine, and I saw that mgradm was upgraded.
The following 7 packages are going to be upgraded:
mgradm mgrctl zabbix-agent2 zabbix-agent2-plugin-ember-plus zabbix-agent2-plugin-mongodb zabbix-agent2-plugin-mssql zabbix-agent2-plugin-postgresql
But after rebooting and running mgradm upgrade podman
2:29PM INF Welcome to mgradm
2:29PM INF Executing command: podman
Password for the CA key to generate:
Hitting newline results in “A value is required” and I’ve stopped there.
My question: Is recreating the certs as given by 1of16 going to break the SSL trust between my 200-odd clients and Uyuni, or are these purely internal to the containers and safe to replace?
Thanks.
From: 1of16 ***@***.***>
Sent: 03 June 2025 12:33
To: uyuni-project/uyuni ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [uyuni-project/uyuni] Uyuni Podman Upgrade 2025.05 on Ubuntu host not successful (Discussion #10402)
I think I've solved it now!
what I did (after reverting to a snapshot with uyuni server 2024.12):
podman secret create uyuni-ca /usr/local/share/ca-certificates/mhh/pki-sub.crt
podman secret create uyuni-db-ca /usr/local/share/ca-certificates/mhh/pki-sub.crt
podman secret create uyuni-cert /root/certificate_uyuni.cer
podman secret create uyuni-key /root/certificate_uyuni.key
podman secret create uyuni-db-cert /root/certificate_uyuni.cer
podman secret create uyuni-db-key /root/certificate_uyuni.key
note: the keys aren't encrypted!
mgradm upgrade podman
and then I waited....and waited and then:
podman ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
08b229a84186 registry.opensuse.org/uyuni/server-postgresql:latest postgres 3 minutes ago Up 3 minutes (healthy) 0.0.0.0:5432->5432/tcp uyuni-db
2acab78d4b87 registry.opensuse.org/uyuni/server:latest /usr/lib/systemd/... 2 minutes ago Up 2 minutes (healthy) 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp, 0.0.0.0:4505-4506->4505-4506/tcp, 0.0.0.0:5556-5557->5556-5557/tcp, 0.0.0.0:9100->9100/tcp, 0.0.0.0:9187->9187/tcp, 0.0.0.0:9800->9800/tcp, 0.0.0.0:25151->25151/tcp, 0.0.0.0:69->69/udp, :::80->80/tcp, :::443->443/tcp, :::4505-4506->4505-4506/tcp, :::5556-5557->5556-5557/tcp, :::9100->9100/tcp, :::9187->9187/tcp, :::9800->9800/tcp, :::25151->25151/tcp, :::69->69/udp uyuni-server
EC Certificates aren't a problem, but your upgrade documentation could be a little bit improved :)
thank you for your patients and tips!
—
Reply to this email directly, view it on GitHub<#10402 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A7AIN5MJXHVJYWE3BKBVKCT3BWBVLAVCNFSM6AAAAAB6OY5M32VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMZVGQ3TCMY>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>
|
Beta Was this translation helpful? Give feedback.
-
as fas as I understand it, the certificate is used to validate the https connection between client ans uyuni server. so if you’re using a new, trusted (not self signed) one, you should be fine. |
Beta Was this translation helpful? Give feedback.
-
the message is misleading and it will be fixed in next version by uyuni-project/uyuni-tools#584. The password is requested to create a new ssl certificate for the db container (before it wasn't required since it was on the same container of the server) and the server one should be provided (to use the same CA to create the new certificate). No changes in server certificate. |
Beta Was this translation helpful? Give feedback.
-
|
(Sorry - Creating new issue as error is slightly different and this is marked as answered) |
Beta Was this translation helpful? Give feedback.
I think I've solved it now!
what I did (after reverting to a snapshot with uyuni server 2024.12):
note: the keys aren't encrypted!
mgradm upgrade podmanand then I waited....and waited and then: