- ARCHIVED: Uyuni Users

[uyuni-users] spacewalk-common-channels
by Huber, Peter 13 Jul '20

13 Jul '20

Till now I managed to setup a uyuni server with two clients, one CentOS7 and one CentOS8. Everything is working as expected. I imported the channels via spacewalk-common-channels, e.g. spacewalk-common-channels -v -u admin -p <password> -a x86_64 -k unlimited 'centos7*' This worked in the same way as on our spacewalk server. Now I want to add some additional channels / repos in the same way and I got an error message: spacewalk-common-channels -v -u admin -p <password> -a x86_64 -k unlimited 'oraclelinux7*' Connecting to http://localhost/rpc/api Error: redstone.xmlrpc.XmlRpcFault: Either the password or username is incorrect. The password and the username is correct, I can login on the website with these credentials. I few days ago I used this to add a lot of channels/repos, what can be wrong? Any idea? Thank you, Peter -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

3 2

[uyuni-users] Upgrade registered Uyuni client from 15.1 to 15.2
by Bidault, Philippe 08 Jul '20

08 Jul '20

Hi all, I have seen documentation were the zypper repo file needs to be modified by hand to upgrade from Leap 15.1 to 15.2, and was now wondering, how the upgrade could be done on a registered Uyuni client ? Just by modifying the registered repo from the Uyuni web console does the trick ? Regards, Philippe. Philippe Bidault | Unix Engineer Getronics ________________________________ M. 34617301667 | E. Philippe.Bidault(a)Getronics.com | W. www.getronics.com [cid:M17520GetronicsConnectingPossibilitiesE-Sig425x204_e1803ca0-99a5-4a65-abd8-074c86bf11aa.png]<http://www.getronics.com/> <http://www.linkedin.com/company/2077785>[cid:LinkedIn_4aeb630a-f385-4f22-927e-31323d2554b8.png]<https://www.linkedin.com/company/2077785> [cid:Twitter_6c9cce61-b2e3-49d4-991c-e799d031f1ae.png] <https://twitter.com/Getronics> <http://twitter.com/Getronics> [cid:Youtube_5150f807-4ba8-46a3-bbbf-038ccfdc2793.png] <https://www.youtube.com/user/getronicsonline?feature=results_main> <http://www.youtube.com/user/getronicsonline?feature=results_main> sign-info <http://www.getronics.com/knowledge-share/news-and-events/ovum.php#sthash.cb…> Getronics CMC Service Desk Iberia S.L - VAT No:S.L.: B66686262. Registered Office - Getronics CMC Service Desk Iberia S.L, C/Rosselloi, Porcel, 21 planta 11, 08016 Barcelona, Spain. The information transmitted is intended only for use by the addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. Thank you. Legal disclaimer: http://www.getronics.com/legal/

3 5

[uyuni-users] Re-registration of system with the same minion-id results in unmanagable system
by Mattias Giese 06 Jul '20

06 Jul '20

Heya, running Uyuni 2020.04 we encounter the following issue: If a user 'recycles' a system (through reprovisioning) the following happens: 1) We do not explicitly remove the current system profile in Uyuni nor remove the minion from salt 2) The system will be reprovisioned through our internal deployment system 3) After successful provisioning, we bootstrap the host with the same minion-id The result: The already existing system profile is not updated. Crucial information (like the dbus/systemd machine-id) is not refreshed in the profile leading to 'interesting' errors like these: ``` local: Data failed to compile: ---------- Specified SLS packages.packages_b60982e0e0334b5baffb24ca15e2b98a in saltenv base is not available on the salt master or through a configured fileserver ---------- Specified SLS custom.custom_b60982e0e0334b5baffb24ca15e2b98a in saltenv base is not available on the salt master or through a configured fileserver ``` This is happening because Uyuni is still using the machine-id of the previously deployed system for the generation of salt states. I raised the Taskomatic log level to debug in the hopes of seeing 'something' [TM], but grepping these logs using the machine-ids/hostnames didn't help me either. It seems as if Uyuni is simply skipping the bootstrap/registration procedure if the minion-id is already existing. There does not seem to be the possibility to 'force' a re-registration. So, my question to the Uyuni devs would be: Is the only way to work around this the complete deletion of the system profile or is there a magic flag/configuration setting hidden somewhere that i could specify? Regards, Mattias

2 2

[uyuni-users] Channel subscription after registering
by Huber, Peter 06 Jul '20

06 Jul '20

Hello, we are on a process to migrate our old spacewalk installation to uyuni or foreman. At the moment we are evaluating uyuni against foreman/katello. Till now a lot of things are working fine, but I found one thing, I don't understand. I configured all Centos 7 and Centos 8 channels and they are updated daily, this part is working fine. Now I want to subscribe a Centos test system. I do so by editing a salt config file in this way: master: <our uyuni server name> server_id_use_src: adler32 enable_legacy_startup_events: False enable_fqdns_grains: False grains: susemanager: activation-key: "1-centos8-x86_64" After starting salt-minion, a key is generated and I can see the key under Software => Keys. My expectation is that the server will be added by accepting the key. This works fine, but the server has no base channel and no child channels.. When I look at the activation key (1-centos8-x86_64) I see a base channel and a lot of child channels activated for this key. Why are these channels not activated after registering a new server? Thank you, Peter

5 13

[uyuni-users] Raspbian in Uyuni
by Javier.Flores＠gmz.migros.ch 29 Jun '20

29 Jun '20

Hello Before spending a lot of time trying I thought I ask. Has anyone tried to sync Raspbian repositories and manage Raspberry Pi clients with Uyuni? Regards, Javier

3 2

Re: [uyuni-users] Problem syncing channels
by Len Ewen 26 Jun '20

26 Jun '20

I uploaded channels from the spacewalk-common channels to populate my channels then I tried the sync command and got RepoMDError: Cannot access repository. Maybe repository GPG keys are not imported After that I tried, per the suggestions of some of the others experiencing the issue, I tried the cli spacewalk-repo-sync -c 'centos7-x86_64' Repository 'centos7-x86_64-extras' is invalid. [centos7-x86_64-extras|http://mirrorlist.centos.org/?release=7&arch=x86_64&r… <http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=extras&proxy=http:…> Valid metadata not found at specified URL History: - [|] Error trying to read from 'http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=extras&proxy=http:… <http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=extras&proxy=http:…>!' - Download (curl) error for 'http://mirrorlist.centos.org/content?release=7&arch=x86_64&repo=extras&prox… <http://mirrorlist.centos.org/content?release=7&arch=x86_64&repo=extras&prox…>: Error code: HTTP response: 400 Error message: The requested URL returned error: 400 Bad Request Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'centos7-x86_64-extras' because of the above error. Could not refresh the repositories because of errors. 11:19:38 RepoMDError: Cannot access repository. Maybe repository GPG keys are not imported --------------- Len Ewen Systems Administrator 1 Information Technology University of Indianapolis (317) 788-3362 [image: UIndyIT.jpg] Confidentiality Notice: This communication and/or its content are for the sole use of the intended recipient, and may be privileged, confidential, or otherwise protected from disclosure by law. If you are not the intended recipient, please notify the sender and then delete all copies of it. Unless you are the intended recipient, your use or dissemination of the information contained in this communication may be illegal. On Fri, Jun 26, 2020 at 11:23 AM Len Ewen <ewenf(a)uindy.edu> wrote: > I uploaded channels from the spacewalk-common channels to populate my > channels then I tried the sync command and got > > RepoMDError: Cannot access repository. Maybe repository GPG keys are not imported > > After that I tried, per the suggestions of some of the others experiencing the issue, I tried the cli > spacewalk-repo-sync -c 'centos7-x86_64' > > Repository 'centos7-x86_64-extras' is invalid. > [centos7-x86_64-extras|http://mirrorlist.centos.org/?release=7&arch=x86_64&r… Valid metadata not found at specified URL > History: > - [|] Error trying to read from 'http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=extras&proxy=http:…!' > - Download (curl) error for 'http://mirrorlist.centos.org/content?release=7&arch=x86_64&repo=extras&prox…: > Error code: HTTP response: 400 > Error message: The requested URL returned error: 400 Bad Request > > > Please check if the URIs defined for this repository are pointing to a valid repository. > Skipping repository 'centos7-x86_64-extras' because of the above error. > Could not refresh the repositories because of errors. > 11:19:38 RepoMDError: Cannot access repository. Maybe repository GPG keys are not imported > > --------------- > > Len Ewen > > Systems Administrator 1 > > Information Technology > > University of Indianapolis > > (317) 788-3362 > > [image: UIndyIT.jpg] > > Confidentiality Notice: This communication and/or its content are for the > sole use of the intended recipient, and may be privileged, confidential, or > otherwise protected from disclosure by law. If you are not the intended > recipient, please notify the sender and then delete all copies of it. > Unless you are the intended recipient, your use or dissemination of the > information contained in this communication may be illegal. > > > On Thu, Jun 25, 2020 at 8:53 PM Julio González Gil <jgonzalez(a)suse.com> > wrote: > >> Please, provide more details: >> >> - What are you trying to sync exactly? >> - Can you paste your call to spacewalk-repo-sync? >> >> On jueves, 25 de junio de 2020 19:41:50 (CEST) Len Ewen wrote: >> > I dropped this into the glitter chat, but I'll try here as well. When I >> > try to sync the repos through the UI, it errors out saying >> > >> > RepoMDError: Cannot access repository. Maybe repository GPG keys are >> > not imported >> > >> > I read in the list serv from previous months that people have seen the >> > problem and >> > the recommended solution is try it from the command line using >> > spacewalk-repo-sync >> > >> > but I am still getting the same error on the command line, so I am >> > unsure what is going >> > >> > on and what I can do to fix it. Does anyone have any suggestions to my >> > problem? >> > >> > >> > --------------- >> > >> > Len Ewen >> > >> > Systems Administrator 1 >> > >> > Information Technology >> > >> > University of Indianapolis >> > >> > (317) 788-3362 >> > >> > [image: UIndyIT.jpg] >> > >> > Confidentiality Notice: This communication and/or its content are for >> the >> > sole use of the intended recipient, and may be privileged, >> confidential, or >> > otherwise protected from disclosure by law. If you are not the intended >> > recipient, please notify the sender and then delete all copies of it. >> > Unless you are the intended recipient, your use or dissemination of the >> > information contained in this communication may be illegal. >> >> >> -- >> Julio González Gil >> Release Engineer, SUSE Manager and Uyuni >> jgonzalez(a)suse.com > >

2 4

[uyuni-users] Problem syncing channels
by Len Ewen 26 Jun '20

26 Jun '20

I dropped this into the glitter chat, but I'll try here as well. When I try to sync the repos through the UI, it errors out saying RepoMDError: Cannot access repository. Maybe repository GPG keys are not imported I read in the list serv from previous months that people have seen the problem and the recommended solution is try it from the command line using spacewalk-repo-sync but I am still getting the same error on the command line, so I am unsure what is going on and what I can do to fix it. Does anyone have any suggestions to my problem? --------------- Len Ewen Systems Administrator 1 Information Technology University of Indianapolis (317) 788-3362 [image: UIndyIT.jpg] Confidentiality Notice: This communication and/or its content are for the sole use of the intended recipient, and may be privileged, confidential, or otherwise protected from disclosure by law. If you are not the intended recipient, please notify the sender and then delete all copies of it. Unless you are the intended recipient, your use or dissemination of the information contained in this communication may be illegal.

2 1

[uyuni-users] Issues Bootstrap Minions - Add with SSH failed with salt permission denied.
by Nuno Higgs 25 Jun '20

25 Jun '20

Hello all, I've been trying to add several clients - centos 7 and leap 15.1 - to my 2020.05 Uyuni fresh implementation and I am getting on both errors using only ssh. It seems to be related to this https://github.com/saltstack/salt/issues/38458. Is there any workaround? I am trying to add a new server, bootstrap, using only ssh. Thanks a lot for your help. Nuno. Error log: 2020-06-08 14:25:39,503 [py.warnings :99 ][WARNING ][3878] /usr/share/susemanager/modules/pillar/suma_minion.py:83: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details. ret.update(yaml.load(open('{0}.yml'.format(static_pillar_filename)).read())) 2020-06-08 14:25:39,508 [py.warnings :99 ][WARNING ][3878] /usr/share/susemanager/modules/pillar/suma_minion.py:91: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details. ret.update(yaml.load(open('{0}.yml'.format(global_pillar_filename)).read())) 2020-06-08 14:25:39,753 [salt.utils.templates:180 ][ERROR ][3878] Rendering exception occurred Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/salt/utils/templates.py", line 392, in render_jinja_tmpl output = template.render(**decoded_context) File "/usr/lib/python3.6/site-packages/jinja2/asyncsupport.py", line 76, in render return original_render(self, *args, **kwargs) File "/usr/lib/python3.6/site-packages/jinja2/environment.py", line 1008, in render return self.environment.handle_exception(exc_info, True) File "/usr/lib/python3.6/site-packages/jinja2/environment.py", line 780, in handle_exception reraise(exc_type, exc_value, tb) File "/usr/lib/python3.6/site-packages/jinja2/_compat.py", line 37, in reraise raise value.with_traceback(tb) File "<template>", line 8, in top-level template code File "/usr/lib/python3.6/site-packages/jinja2/runtime.py", line 579, in _invoke rv = self._func(*arguments) File "<template>", line 2, in template File "/usr/lib/python3.6/site-packages/salt/utils/jinja.py", line 136, in get_source self.check_cache(_template) File "/usr/lib/python3.6/site-packages/salt/utils/jinja.py", line 97, in check_cache self.cache_file(template) File "/usr/lib/python3.6/site-packages/salt/utils/jinja.py", line 90, in cache_file self.file_client().get_file(saltpath, '', True, self.saltenv) File "/usr/lib/python3.6/site-packages/salt/fileclient.py", line 1053, in get_file hash_server, stat_server = self.hash_and_stat_file(path, saltenv) File "/usr/lib/python3.6/site-packages/salt/fileclient.py", line 1312, in hash_and_stat_file hash_result = self.hash_file(path, saltenv) File "/usr/lib/python3.6/site-packages/salt/fileclient.py", line 1305, in hash_file return self.__hash_and_stat_file(path, saltenv) File "/usr/lib/python3.6/site-packages/salt/fileclient.py", line 1297, in __hash_and_stat_file return self.channel.send(load) File "/usr/lib/python3.6/site-packages/salt/fileserver/__init__.py", line 906, in send return getattr(self.fs, cmd)(load) File "/usr/lib/python3.6/site-packages/salt/fileserver/__init__.py", line 681, in file_hash return self.__file_hash_and_stat(load)[0] File "/usr/lib/python3.6/site-packages/salt/fileserver/__init__.py", line 673, in __file_hash_and_stat return self.servers[fstr](load, fnd), stat_result File "/usr/lib/python3.6/site-packages/salt/fileserver/roots.py", line 280, in file_hash os.makedirs(cache_dir) File "/usr/lib64/python3.6/os.py", line 210, in makedirs makedirs(head, mode, exist_ok) File "/usr/lib64/python3.6/os.py", line 210, in makedirs makedirs(head, mode, exist_ok) File "/usr/lib64/python3.6/os.py", line 210, in makedirs makedirs(head, mode, exist_ok) [Previous line repeated 5 more times] File "/usr/lib64/python3.6/os.py", line 220, in makedirs mkdir(name, mode) PermissionError: [Errno 13] Permission denied: '/var/tmp/.root_2c2911_salt/running_data' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/salt/utils/templates.py", line 169, in render_tmpl output = render_str(tmplstr, context, tmplpath) File "/usr/lib/python3.6/site-packages/salt/utils/templates.py", line 441, in render_jinja_tmpl trace=tracestr) salt.exceptions.SaltRenderError: Jinja error: [Errno 13] Permission denied: '/var/tmp/.root_2c2911_salt/running_data' Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/salt/utils/templates.py", line 392, in render_jinja_tmpl output = template.render(**decoded_context) File "/usr/lib/python3.6/site-packages/jinja2/asyncsupport.py", line 76, in render return original_render(self, *args, **kwargs) File "/usr/lib/python3.6/site-packages/jinja2/environment.py", line 1008, in render return self.environment.handle_exception(exc_info, True) File "/usr/lib/python3.6/site-packages/jinja2/environment.py", line 780, in handle_exception reraise(exc_type, exc_value, tb) File "/usr/lib/python3.6/site-packages/jinja2/_compat.py", line 37, in reraise raise value.with_traceback(tb) File "<template>", line 8, in top-level template code File "/usr/lib/python3.6/site-packages/jinja2/runtime.py", line 579, in _invoke rv = self._func(*arguments) File "<template>", line 2, in template File "/usr/lib/python3.6/site-packages/salt/utils/jinja.py", line 136, in get_source self.check_cache(_template) File "/usr/lib/python3.6/site-packages/salt/utils/jinja.py", line 97, in check_cache self.cache_file(template) File "/usr/lib/python3.6/site-packages/salt/utils/jinja.py", line 90, in cache_file self.file_client().get_file(saltpath, '', True, self.saltenv) File "/usr/lib/python3.6/site-packages/salt/fileclient.py", line 1053, in get_file hash_server, stat_server = self.hash_and_stat_file(path, saltenv) File "/usr/lib/python3.6/site-packages/salt/fileclient.py", line 1312, in hash_and_stat_file hash_result = self.hash_file(path, saltenv) File "/usr/lib/python3.6/site-packages/salt/fileclient.py", line 1305, in hash_file return self.__hash_and_stat_file(path, saltenv) File "/usr/lib/python3.6/site-packages/salt/fileclient.py", line 1297, in __hash_and_stat_file return self.channel.send(load) File "/usr/lib/python3.6/site-packages/salt/fileserver/__init__.py", line 906, in send return getattr(self.fs, cmd)(load) File "/usr/lib/python3.6/site-packages/salt/fileserver/__init__.py", line 681, in file_hash return self.__file_hash_and_stat(load)[0] File "/usr/lib/python3.6/site-packages/salt/fileserver/__init__.py", line 673, in __file_hash_and_stat return self.servers[fstr](load, fnd), stat_result File "/usr/lib/python3.6/site-packages/salt/fileserver/roots.py", line 280, in file_hash os.makedirs(cache_dir) File "/usr/lib64/python3.6/os.py", line 210, in makedirs makedirs(head, mode, exist_ok) File "/usr/lib64/python3.6/os.py", line 210, in makedirs makedirs(head, mode, exist_ok) File "/usr/lib64/python3.6/os.py", line 210, in makedirs makedirs(head, mode, exist_ok) [Previous line repeated 5 more times] File "/usr/lib64/python3.6/os.py", line 220, in makedirs mkdir(name, mode) PermissionError: [Errno 13] Permission denied: '/var/tmp/.root_2c2911_salt/running_data' ; line 2 --- {% macro includesls(osfullname, osrelease) -%} {% include 'certs/{0}.sls'.format(osfullname + osrelease.replace('.', '_')) ignore missing -%} <====================== {%- endmacro %} {% if grains['os_family'] == 'Suse' %} {% if grains['osfullname'] == 'openSUSE Tumbleweed' %} {% set sls = includesls('Tumbleweed', '') -%} {% else -%} [...] --- 2020-06-08 14:25:39,754 [salt.state :3516][CRITICAL][3878] Rendering SLS 'base:certs' failed: Jinja error: [Errno 13] Permission denied: '/var/tmp/.root_2c2911_salt/running_data' Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/salt/utils/templates.py", line 392, in render_jinja_tmpl output = template.render(**decoded_context) File "/usr/lib/python3.6/site-packages/jinja2/asyncsupport.py", line 76, in render return original_render(self, *args, **kwargs) File "/usr/lib/python3.6/site-packages/jinja2/environment.py", line 1008, in render return self.environment.handle_exception(exc_info, True) File "/usr/lib/python3.6/site-packages/jinja2/environment.py", line 780, in handle_exception reraise(exc_type, exc_value, tb) File "/usr/lib/python3.6/site-packages/jinja2/_compat.py", line 37, in reraise raise value.with_traceback(tb) File "<template>", line 8, in top-level template code File "/usr/lib/python3.6/site-packages/jinja2/runtime.py", line 579, in _invoke rv = self._func(*arguments) File "<template>", line 2, in template File "/usr/lib/python3.6/site-packages/salt/utils/jinja.py", line 136, in get_source self.check_cache(_template) File "/usr/lib/python3.6/site-packages/salt/utils/jinja.py", line 97, in check_cache self.cache_file(template) File "/usr/lib/python3.6/site-packages/salt/utils/jinja.py", line 90, in cache_file self.file_client().get_file(saltpath, '', True, self.saltenv) File "/usr/lib/python3.6/site-packages/salt/fileclient.py", line 1053, in get_file hash_server, stat_server = self.hash_and_stat_file(path, saltenv) File "/usr/lib/python3.6/site-packages/salt/fileclient.py", line 1312, in hash_and_stat_file hash_result = self.hash_file(path, saltenv) File "/usr/lib/python3.6/site-packages/salt/fileclient.py", line 1305, in hash_file return self.__hash_and_stat_file(path, saltenv) File "/usr/lib/python3.6/site-packages/salt/fileclient.py", line 1297, in __hash_and_stat_file return self.channel.send(load) File "/usr/lib/python3.6/site-packages/salt/fileserver/__init__.py", line 906, in send return getattr(self.fs, cmd)(load) File "/usr/lib/python3.6/site-packages/salt/fileserver/__init__.py", line 681, in file_hash return self.__file_hash_and_stat(load)[0] File "/usr/lib/python3.6/site-packages/salt/fileserver/__init__.py", line 673, in __file_hash_and_stat return self.servers[fstr](load, fnd), stat_result File "/usr/lib/python3.6/site-packages/salt/fileserver/roots.py", line 280, in file_hash os.makedirs(cache_dir) File "/usr/lib64/python3.6/os.py", line 210, in makedirs makedirs(head, mode, exist_ok) File "/usr/lib64/python3.6/os.py", line 210, in makedirs makedirs(head, mode, exist_ok) File "/usr/lib64/python3.6/os.py", line 210, in makedirs makedirs(head, mode, exist_ok) [Previous line repeated 5 more times] File "/usr/lib64/python3.6/os.py", line 220, in makedirs mkdir(name, mode) PermissionError: [Errno 13] Permission denied: '/var/tmp/.root_2c2911_salt/running_data' ; line 2 --- {% macro includesls(osfullname, osrelease) -%} {% include 'certs/{0}.sls'.format(osfullname + osrelease.replace('.', '_')) ignore missing -%} <====================== {%- endmacro %} {% if grains['os_family'] == 'Suse' %} {% if grains['osfullname'] == 'openSUSE Tumbleweed' %} {% set sls = includesls('Tumbleweed', '') -%} {% else -%} [...] --- 2020-06-08 14:25:39,757 [salt.client.ssh :1170][ERROR ][3878] An Exception occurred while executing state.apply: [Errno 13] Permission denied: '/var/tmp/.root_2c2911_salt/running_data'

4 7

[uyuni-users] Can't sync SCLO CentOS repo
by Bidault, Philippe 19 Jun '20

19 Jun '20

Hi all, With Uyuni 2020.05, I am not able to synchronized the CentOS SCL repo: 2020/05/29 01:00:30 -00:00 Command: ['/usr/bin/spacewalk-repo-sync', '--channel', 'centos7-x86_64-sclo', '--type', 'yum', '--non-interactive'] 2020/05/29 01:00:30 -00:00 Sync of channel started. 2020/05/29 01:00:32 -00:00 RepoMDError: Cannot access repository. Maybe repository GPG keys are not imported There already is this open issue https://github.com/uyuni-project/uyuni/issues/1578, but I don't really see a solution for an OpenSuse. Does somebody had and solved this issue ? Regards, Philippe. Philippe Bidault | Unix Engineer Getronics ________________________________ M. 34617301667 | E. Philippe.Bidault(a)Getronics.com | W. www.getronics.com [cid:M17520GetronicsConnectingPossibilitiesE-Sig425x204_e1803ca0-99a5-4a65-abd8-074c86bf11aa.png]<http://www.getronics.com/> <http://www.linkedin.com/company/2077785>[cid:LinkedIn_4aeb630a-f385-4f22-927e-31323d2554b8.png]<https://www.linkedin.com/company/2077785> [cid:Twitter_6c9cce61-b2e3-49d4-991c-e799d031f1ae.png] <https://twitter.com/Getronics> <http://twitter.com/Getronics> [cid:Youtube_5150f807-4ba8-46a3-bbbf-038ccfdc2793.png] <https://www.youtube.com/user/getronicsonline?feature=results_main> <http://www.youtube.com/user/getronicsonline?feature=results_main> sign-info <http://www.getronics.com/knowledge-share/news-and-events/ovum.php#sthash.cb…> Getronics CMC Service Desk Iberia S.L - VAT No:S.L.: B66686262. Registered Office - Getronics CMC Service Desk Iberia S.L, C/Rosselloi, Porcel, 21 planta 11, 08016 Barcelona, Spain. The information transmitted is intended only for use by the addressee and may contain confidential and/or privileged material. Any review, re-transmission, dissemination or other use of it, or the taking of any action in reliance upon this information by persons and/or entities other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. Thank you. Legal disclaimer: http://www.getronics.com/legal/

6 11

[uyuni-users] Uyuni Community Hours 26.06.2020
by Pau Garcia Quiles 17 Jun '20

17 Jun '20

Hello Let's meet again 🙂 Agenda: 1. Uyuni 2020.06 (Julio González, SUSE) 2. Ansible roles to deploy Uyuni (Christian Stankowic, SVA) 3. Q&A Please note this time we are starting at 4pm, since last time it was too early for US West Coast. Uyuni Community Hours Fri, Jun 26, 2020 4:00 PM - 5:00 PM (CEST) Please join my meeting from your computer, tablet or smartphone. https://www.gotomeet.me/pagarcia/uyuni-community-hours-26 You can also dial in using your phone. United States: +1 (571) 317-3129<tel:+15713173129,,714300045#> Access Code: 714-300-045 More phone numbers Australia: +61 2 9087 3604<tel:+61290873604,,714300045#> Austria: +43 7 2081 5427<tel:+43720815427,,714300045#> Belgium: +32 28 93 7018<tel:+3228937018,,714300045#> Brazil: +55 21 3500-3941<tel:+552135003941,,714300045#> Bulgaria: +359 2 906 0605<tel:+35929060605,,714300045#> Canada: +1 (647) 497-9391<tel:+16474979391,,714300045#> Chile: +56 2 3214 9680<tel:+56232149680,,714300045#> Colombia: +57 1 600 9953<tel:+5716009953,,714300045#> Czech Republic: +420 2 55 71 95 02<tel:+420255719502,,714300045#> Denmark: +45 43 31 47 82<tel:+4543314782,,714300045#> Finland: +358 923 17 0568<tel:+358923170568,,714300045#> France: +33 170 950 594<tel:+33170950594,,714300045#> Germany: +49 891 2140 2090<tel:+4989121402090,,714300045#> Greece: +30 21 0 300 2583<tel:+302103002583,,714300045#> Hungary: +36 1 933 3699<tel:+3619333699,,714300045#> Ireland: +353 15 360 728<tel:+35315360728,,714300045#> Israel: +972 3 376 3070<tel:+97233763070,,714300045#> Italy: +39 0 247 92 13 01<tel:+390247921301,,714300045#> Luxembourg: +352 34 2080 9219<tel:+3523420809219,,714300045#> Malaysia: +60 3 7724 4059<tel:+60377244059,,714300045#> Mexico: +52 55 3687 7278<tel:+525536877278,,714300045#> Netherlands: +31 207 941 377<tel:+31207941377,,714300045#> New Zealand: +64 9 280 6302<tel:+6492806302,,714300045#> Norway: +47 23 16 23 30<tel:+4723162330,,714300045#> Panama: +507 308 4334<tel:+5073084334,,714300045#> Peru: +51 1 642 9424<tel:+5116429424,,714300045#> Romania: +40 31 780 1158<tel:+40317801158,,714300045#> South Africa: +27 11 259 4924<tel:+27112594924,,714300045#> Spain: +34 932 75 2004<tel:+34932752004,,714300045#> Sweden: +46 775 757 474<tel:+46775757474,,714300045#> Switzerland: +41 225 4599 78<tel:+41225459978,,714300045#> Turkey: +90 212 900 4807<tel:+902129004807,,714300045#> United Kingdom: +44 330 221 0088<tel:+443302210088,,714300045#> Join from a video-conferencing room or system. Dial in or type: 67.217.95.2 or inroomlink.goto.com Meeting ID: 714 300 045 Or dial directly: 714300045(a)67.217.95.2 or 67.217.95.2##714300045 New to GoToMeeting? Get the app now and be ready when your first meeting starts: https://global.gotomeeting.com/install/714300045 Pau Garcia Quiles SUSE Manager Product Owner & Technical Project Manager SUSE Software Solutions Spain

1 0