Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Julio González Gil
    @juliogonzalez
    @jkinning on paper Uyuni should be able to handle it, but the problem is that we don't have access to ULN to actually test it and fix problems
    jkinning
    @jkinning
    Gotcha... good to know.
    Back to CentOS 7 :) I registered a device and I see it under the Salt|Keys but it isn't hyperlinked like the other CentOS 7 servers I have. From what I found is cloning may cause this but the fingerprint on them all are different. Is there something else I need to do so this server gets "pushed" over to the Systems area where I can add the channels and all the other good stuff? I tried registering it with the bootstrap script that I used for other CentOS 7 servers. Deleted it from the Salt|Keys and then attempted to register it from the Systems|Bootstraping within the UI. I can interact it from Salt just not the Systems or add channels as the server listed in Salt Keys is just text and no link like the others, if that make sense.
    Julio González Gil
    @juliogonzalez
    if you are using cloned servers, did you regenerate the UUID?
    ewenf-uindy
    @ewenf-uindy
    @jkinning I added # Rebuild uuid since vms were cloned and causes issue with registration.
    rm -f /etc/machine-id
    rm -f /var/lib/dbus/machine-id
    dbus-uuidgen --ensure
    systemd-machine-id-setup to my boostrap
    that way the UUID changes when the bootstrap is run
    jkinning
    @jkinning
    Yes, I just checked and that was all changed. However, my clients are not shown in the Systems just under the Salt|Keys and while the others have the blue text, hyperlinks, a couple are just black text. I have restarted the salt-minion removed and deleted stuff a few times and still the same result. Very strange so been looking at the docs to figure out logs to look at to help troubleshoot. Not sure if I can run the highstate on them, not sure how I would even do that since I am just learning about Salt. :)
    Julio González Gil
    @juliogonzalez
    according to that doc, you could rerun the bootstrap procedure, but make sure you generate a new UUID
    (ahead of the bootstrap)
    jkinning
    @jkinning
    I've ran the bootstrap several times along with the UI bootstrapping. I've also manually run the command to change the UUID's but one of the machines is bare metal and giving me the same problems. Looks like it is alright with Salt but not the other parts to manage packages and such. These were registered with Spacewalk previously but using @ewenf-uindy helpful suggestions it removes all the rhn stuff. I even rebooted the machine and it still isn't kicking over and just Salt aware. I guess that is what you'd call it.
    Shirocco88
    @Shirocco88

    Question: how can I change "package download endpoint override":

    Release Notes:
    It is now possible to set a custom protocol, host and path for minions to download packages at installation time. This will override the default setting of the Uyuni Server or Uyuni Proxy used at registration time.

    jkinning
    @jkinning
    All - I was able to correct my issue be stopping the salt-minion and rm -rf /etc/salt and then re-running the bootstrap script. That was a doozy!
    ewenf-uindy
    @ewenf-uindy
    hold on, let me go back through my notes, there was something I had to delete to get the minion to reregister correctly
    Shirocco88
    @Shirocco88
    If it is a cloned system, then you should clean your client system before bootstrapping:
    rm /etc/salt/pki/minion/minion*
    rm -r /var/cache/salt/minion
    ewenf-uindy
    @ewenf-uindy
    That's what I was about to post
    Shirocco88
    @Shirocco88
    rm /etc/salt/minion_id
    systemctl stop salt-minion.service
    ewenf-uindy
    @ewenf-uindy
    has anyone gotten the centos6 bootstrap to work?
    jkinning
    @jkinning
    I got an Oracle Linux 6 bootstrap to work, shouldn't be too much different.
    ewenf-uindy
    @ewenf-uindy
    what magic voodoo did you have to do, did it just install right out of thee box?
    jkinning
    @jkinning
    I created the bootstrap script and then added your voodoo to the script and then on my client ran 'curl -Sks https://uyuniserver/pub/bootstrap/bootstrap.sh | /bin/bash' then under the Salt keys accepted my client.
    Shirocco88
    @Shirocco88

    Again:
    Question: how can I change "package download endpoint override":

    Release Notes:
    It is now possible to set a custom protocol, host and path for minions to download packages at installation time. This will override the default setting of the Uyuni Server or Uyuni Proxy used at registration time.

    is it possible to define special settings (custom protocol, host and path) whitin /etc/zypp/repos.d/susemanager:channel.repo on a per client basis ?
    is there anyone, who can give me a hint;

    igorgolm
    @igorgolm
    Hi, is there any way to proxy master gpg keys, which are in /srv/www/htdocs/pub/, also?
    Julio González Gil
    @juliogonzalez
    question: is anyone here using Uyuni 2020.07 with the patch for the CVE we released last week?
    I am asking because I'd like to know if anyone else is affected by uyuni-project/uyuni#2623 before releasing Uyuni 2020.09
    Julio González Gil
    @juliogonzalez
    @igorgolm it should be doing it automatically, isn't?
    mmmm, or maybe not
    I see the same things on my server and proxy, but maybe they synced initially
    igorgolm
    @igorgolm
    @juliogonzalez seems like not
    Julio González Gil
    @juliogonzalez
    seems /pub is served by apache, so not proxied
    on paper you could change apache and squid configurations to do it, but I am not sure about the consequences
    well, maybe only apache and not even squid, but again: not sure about the consequences
    igorgolm
    @igorgolm
    @juliogonzalez but anyway - I'd like to try
    Julio González Gil
    @juliogonzalez
    @igorlm are you by any chance using Uyuni 2020.07 with the patch for the CVE we released last week? ^
    igorgolm
    @igorgolm
    @juliogonzalez I didnt yet installed this patch :) because with docker it is more difficult
    Julio González Gil
    @juliogonzalez
    ah, right, you were experimenting that
    didn't remember
    ok, anyone else? :-D
    would be great having some feedback for this
    jkinning
    @jkinning
    I just recently stood up uyuni, not sure about the patch but when I run rpm -qa | grep 2020.07-86.3.uyuni I get back Uyuni-Server-release-2020.07-86.3.uyuni.x86_64 what are you looking for?
    Julio González Gil
    @juliogonzalez
    we didn't change the Uyuni version, since it's a patch, just updated some spacewalk-java packages and salt-netapi-client
    ewenf-uindy
    @ewenf-uindy
    @jkinning I am not getting the script to even complete and had to install salt by hand. Are you using salt?
    Julio González Gil
    @juliogonzalez
    but now I can confirm that if you apply the original instructions, you should have problems with the services not starting
    I sent an email a few minutes ago with the fix :-)
    igorgolm
    @igorgolm
    @juliogonzalez Please, check also https://www.uyuni-project.org/ "Get new 2020.09" link
    As I understood, 2020.09 is out, but link goes to 2020.07 version release notes etc.
    Julio González Gil
    @juliogonzalez
    ooops... not really
    the link is fine, but I didn't bump the version at https://www.uyuni-project.org/pages/stable-version.html (the titles)
    will do it right now, thanks for pinging me about it :-D