- ARCHIVED: Uyuni Users

[uyuni-users] API curl example
by Strahil Nikolov 04 Jun '19

04 Jun '19

Hello community, can someone give a short example via curl & xml/json for accessing the API. Sadly my skills in python/perl/ruby are close to 0 . Thanks in advance. Best Regards, Strahil Nikolov -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

2 2

[uyuni-users] Feature: Please add opensuse 15.1 to bootstrap
by Strahil Nikolov 25 May '19

25 May '19

Hello Users,Dev, I have modified my '/usr/share/susemanager/mgr_bootstrap_data.py' in order to bootstrap openSUSE Leap 15.1 , but it will be nice if in the next versions we have that out of the box.I haven't tested my modifications, but I will keep you updated. Do you see any issues with my modification? Here is what I got for openSUSE 15.X: openSUSE-Leap-15.0-x86_64' : { 'BASECHANNEL' : 'opensuse_leap15_0-x86_64', 'PKGLIST' : PKGLIST15 + PKGLIST15_NO_Z, 'DEST' : '/srv/www/htdocs/pub/repositories/opensuse/15/0/bootstrap/' }, 'openSUSE-Leap-15.1-x86_64' : { 'BASECHANNEL' : 'opensuse_leap15_1-x86_64', 'PKGLIST' : PKGLIST15 + PKGLIST15_NO_Z, 'DEST' : '/srv/www/htdocs/pub/repositories/opensuse/15/1/bootstrap/' }, Best Regards, Strahil Nikolov -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

2 2

[uyuni-users] Feature request: Add missing Debian headers to repository metadata before signing
by Robert Paschedag 23 May '19

23 May '19

Hello Uyuni devel, this is a feature request for sysadmins, managing Debian / Ubuntu systems with Uyuni. Although there has been a lot of work to support Ubuntu / Debian, there is still some major thing missing. Several metadata headers are missing for Debian packages, that causes major issues on Debian / Ubuntu systems. One header is the "Multi-Arch" header, that is missing. This missing header causes packages to be installable over and over again. "apt" does not correctly "get it", that this package is already the newest installed and suggests these packages when searching for updates all the time. Also some dependencies cannot be successfully solved, because of this missing header. So the workaround most Debian / Ubuntu admins are doing right now, is to - sync the data into Uyuni - wait for spacewalk to generate the "Packages.gz" file - start - possibly below - script to add the missing "Multi-Arch" header to the "Packages.gz" file - sign the file Currently, I don't think that there are any efforts to tune the Uyuni database to also support the missing headers of Debian packages. So a further workaround could be to include such a script to add the missing headers "while or after" the "Packages.gz" gets created (or has been created), but before the file gets "signed". This could be added somewhere within the "DebRepositoryWriter.java" file, where the "signing" of the channel starts. First, I only had written a script to only add the "Multi-Arch" header. But this script below adds all headers missing for a packages. For this to work, you - of course - need the original "Packages.gz" file from Debian / Ubuntu with *all* headers present. Think about it. Would be cool, if this part could also be integrated into Uyuni. Just an idea and still used as workaround.... Best regards, Robert #!/usr/bin/env python -tt # Basically, this should only add one major header # 'Multi-Arch' to the Debian Packages file, but now # we add all missing headers. # # This only works correctly, if you are syncing the Debian repos # directly to one channel within Spacewalk or Uyuni # # You also need python-debian (which is installed on # Spacewalk server) to run this script # # Author: Robert Paschedag <robert.paschedag(a)netlution.de> # Version: 20181107 import sys import os from debian.deb822 import * if len(sys.argv) < 3: print "Usage: %s <path_to_unzipped_Packages_from_Spacewalk_Uyuni> <path_to_original_Debian_repo>" % sys.argv[0] sys.exit(1) spacewalk_file = sys.argv[1] original_file = sys.argv[2] if not os.path.isfile(spacewalk_file): print "Error: Inputfile '%s' not available." % spacewalk_file sys.exit(1) if not os.path.isfile(original_file): print "Error: Inputfile '%s' not available." % original_file sys.exit(1) spacewalk_packages = {} original_packages = {} with open(spacewalk_file, 'r') as pkgs: for pkg in Packages.iter_paragraphs(pkgs): spacewalk_packages[pkg['Package'] + pkg['Version'] + pkg['Architecture']] = pkg with open(original_file, 'r') as orig_file: for pkg in Packages.iter_paragraphs(orig_file): p = pkg['Package'] v = pkg['Version'] a = pkg['Architecture'] if spacewalk_packages.has_key(p + v + a): # found package. Check for missing headers for header in pkg.keys(): if not header in spacewalk_packages[p + v + a].keys(): spacewalk_packages[p + v + a][header] = pkg[header] # open new file new_package = open(spacewalk_file + '.new', 'w') for pkg in spacewalk_packages.values(): pkg.dump(new_package) new_package.write("\n") new_package.close() sys.exit(0) uyuni-test:/usr/local/sbin # -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

1 0

[uyuni-users] Inactive systems after registration
by Kaercher, Alexander 20 May '19

20 May '19

Hello, i set up a new uyuni and register my test systems. It was possible to registered the server successfully, but all the server are now inactive. After delete and reregistered again, only the salt-key is visible, but the system is not register successfully. After the delete I was also deinstalle the salt-minion, salt and python2-salt from the client and run the bootstrapscript again, without an error on the client side. The salt stack is working, I'm able to contact the minions from the salt-mast and across. The following os-systems are registered to Uyuni and has the same issue: OpenSUSE Leap 15.0 OpenSUSE Leap 15.1 OpenSUSE Leap 42.3 SLES12SP4 By the inactive and registered system it is possible to ask for the salt state from the client side: Salt-call state.highstate: local: ---------- ID: mgrchannels_repo Function: file.managed Name: /etc/zypp/repos.d/susemanager:channels.repo Result: True Comment: File /etc/zypp/repos.d/susemanager:channels.repo is in the correct state Started: 07:43:47.884492 Duration: 181.211 ms Changes: ---------- ID: /etc/pki/trust/anchors/RHN-ORG-TRUSTED-SSL-CERT Function: file.managed Result: True Comment: File /etc/pki/trust/anchors/RHN-ORG-TRUSTED-SSL-CERT is in the correct state Started: 07:43:48.066056 Duration: 1277.558 ms Changes: ---------- ID: update-ca-certificates Function: cmd.run Name: /usr/sbin/update-ca-certificates Result: True Comment: State was not run because none of the onchanges reqs changed Changes: ---------- ID: pkg_installed Function: pkg.installed Result: True Comment: No packages to install provided Started: 07:43:49.383607 Duration: 1.142 ms Changes: ---------- ID: pkg_removed Function: pkg.removed Result: True Comment: All specified packages are already absent Started: 07:43:49.385007 Duration: 1407.343 ms Changes: ---------- ID: pkg_latest Function: pkg.latest Result: True Comment: No packages to install provided Started: 07:43:50.792781 Duration: 0.797 ms Changes: ---------- ID: disable_spacewalksd Function: service.dead Name: rhnsd Result: True Comment: The named service rhnsd is not available Started: 07:43:50.795305 Duration: 17.72 ms Changes: ---------- ID: disable_spacewalk-update-status Function: service.dead Name: spacewalk-update-status Result: True Comment: The named service spacewalk-update-status is not available Started: 07:43:50.813411 Duration: 10.929 ms Changes: ---------- ID: disable_osad Function: service.dead Name: osad Result: True Comment: The named service osad is not available Started: 07:43:50.824714 Duration: 10.748 ms Changes: ---------- ID: remove_traditional_stack Function: pkg.removed Result: True Comment: All specified packages are already absent Started: 07:43:50.835840 Duration: 491.993 ms Changes: ---------- ID: mgr_mine_config Function: file.managed Name: /etc/salt/minion.d/susemanager-mine.conf Result: True Comment: File /etc/salt/minion.d/susemanager-mine.conf is in the correct state Started: 07:43:51.328156 Duration: 8.212 ms Changes: ---------- ID: mgr_salt_minion Function: pkg.installed Name: salt-minion Result: True Comment: All specified packages are already installed Started: 07:43:51.336736 Duration: 28026.016 ms Changes: ---------- ID: mgr_salt_minion Function: service.running Name: salt-minion Result: True Comment: The service salt-minion is already running Started: 07:44:19.363709 Duration: 30.719 ms Changes: Summary for local ------------- Succeeded: 13 Failed: 0 ------------- Total states run: 13 Total run time: 31.464 s >From the Salt-Master: uyuni:~ # salt '*' test.version uyuni-proxy.xxxxx.xxx: 2018.3.0 lxeval02.xxxxx.xxx: 2018.3.0 lxeval01.xxxxx.xxx: 2018.3.0 kvm.xxxxxx.xxx: 2019.2.0 I found no error in the /var/log/salt/master and only the following error is visible in the /etc/var/log/rhn/rhn_web_ui.log: 2019-05-09 07:49:40,330 [salt-event-thread-5] ERROR com.redhat.rhn.frontend.events.TransactionHelper - com.suse.manager.reactor.PGEventListenerException 2019-05-09 07:49:40,350 [salt-event-thread-3] ERROR com.redhat.rhn.frontend.events.TransactionHelper - Additional Exception during Exception handling java.lang.ClassCastException 2019-05-09 07:49:40,352 [salt-event-thread-6] ERROR com.redhat.rhn.frontend.events.TransactionHelper - java.lang.ClassCastException 2019-05-09 07:49:40,352 [salt-event-thread-5] ERROR com.redhat.rhn.frontend.events.TransactionHelper - java.lang.ClassCastException 2019-05-09 07:49:40,353 [salt-event-thread-2] ERROR com.redhat.rhn.frontend.events.TransactionHelper - java.lang.ClassCastException 2019-05-09 07:49:40,353 [salt-event-thread-2] ERROR com.redhat.rhn.frontend.events.TransactionHelper - Additional Exception during Exception handling java.lang.ClassCastException 2019-05-09 07:49:40,353 [salt-event-thread-5] ERROR com.redhat.rhn.frontend.events.TransactionHelper - Additional Exception during Exception handling java.lang.ClassCastException 2019-05-09 07:49:40,353 [salt-event-thread-7] ERROR com.redhat.rhn.frontend.events.TransactionHelper - java.lang.ClassCastException 2019-05-09 07:49:40,354 [salt-event-thread-6] ERROR com.redhat.rhn.frontend.events.TransactionHelper - Additional Exception during Exception handling java.lang.ClassCastException 2019-05-09 07:49:40,355 [salt-event-thread-7] ERROR com.redhat.rhn.frontend.events.TransactionHelper - Additional Exception during Exception handling java.lang.ClassCastException 2019-05-09 07:49:40,368 [salt-event-thread-1] ERROR com.suse.manager.reactor.PGEventListener - Unexpected exception while executing a MessageAction org.hibernate.NonUniqueResultException: query did not return a unique result: 2 at org.hibernate.query.internal.AbstractProducedQuery.uniqueElement(AbstractProducedQuery.java:1468) at org.hibernate.query.internal.AbstractProducedQuery.uniqueResult(AbstractProducedQuery.java:1438) at com.redhat.rhn.domain.server.VirtualInstanceFactory.lookupHostVirtInstanceByHostId(VirtualInstanceFactory.java:370) at com.redhat.rhn.manager.system.VirtualInstanceManager.updateHostVirtualInstance(VirtualInstanceManager.java:60) at com.suse.manager.reactor.messaging.VirtpollerBeaconEventMessageAction.lambda$execute$0(VirtpollerBeaconEventMessageAction.java:36) at java.util.Optional.ifPresent(Optional.java:159) at com.suse.manager.reactor.messaging.VirtpollerBeaconEventMessageAction.execute(VirtpollerBeaconEventMessageAction.java:35) at com.suse.manager.reactor.PGEventListener.lambda$null$1(PGEventListener.java:74) at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382) at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580) at com.suse.manager.reactor.PGEventListener.lambda$notify$2(PGEventListener.java:72) at java.util.stream.Streams$StreamBuilderImpl.forEachRemaining(Streams.java:419) at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580) at com.suse.manager.reactor.PGEventListener.notify(PGEventListener.java:69) at com.suse.salt.netapi.event.AbstractEventStream.notifyListeners(AbstractEventStream.java:64) at com.suse.manager.reactor.PGEventStream.lambda$processEvents$3(PGEventStream.java:147) at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184) at java.util.stream.SortedOps$SizedRefSortingSink.end(SortedOps.java:352) at java.util.stream.Sink$ChainedReference.end(Sink.java:258) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151) at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418) at com.suse.manager.reactor.PGEventStream.processEvents(PGEventStream.java:141) at com.suse.manager.reactor.PGEventStream.lambda$null$0(PGEventStream.java:127) at com.redhat.rhn.frontend.events.TransactionHelper.run(TransactionHelper.java:62) at com.redhat.rhn.frontend.events.TransactionHelper.handlingTransaction(TransactionHelper.java:46) at com.suse.manager.reactor.PGEventStream.lambda$notification$2(PGEventStream.java:126) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) 2019-05-09 07:49:40,386 [salt-event-thread-1] ERROR com.redhat.rhn.frontend.events.TransactionHelper - com.suse.manager.reactor.PGEventListenerException 2019-05-09 07:49:40,386 [salt-event-thread-7] ERROR com.suse.manager.reactor.messaging.JobReturnEventMessageAction - Error mapping action chain result: "'mgractionchains.resume' is not available." com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at path $ at com.google.gson.Gson.fromJson(Gson.java:900) at com.google.gson.Gson.fromJson(Gson.java:953) at com.suse.manager.reactor.messaging.JobReturnEventMessageAction.lambda$execute$7(JobReturnEventMessageAction.java:128) at java.util.Optional.ifPresent(Optional.java:159) at com.suse.manager.reactor.messaging.JobReturnEventMessageAction.execute(JobReturnEventMessageAction.java:114) at com.suse.manager.reactor.PGEventListener.lambda$null$1(PGEventListener.java:74) at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382) at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580) at com.suse.manager.reactor.PGEventListener.lambda$notify$2(PGEventListener.java:72) at java.util.stream.Streams$StreamBuilderImpl.forEachRemaining(Streams.java:419) at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580) at com.suse.manager.reactor.PGEventListener.notify(PGEventListener.java:69) at com.suse.salt.netapi.event.AbstractEventStream.notifyListeners(AbstractEventStream.java:64) at com.suse.manager.reactor.PGEventStream.lambda$processEvents$3(PGEventStream.java:147) at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184) at java.util.stream.SortedOps$SizedRefSortingSink.end(SortedOps.java:352) at java.util.stream.Sink$ChainedReference.end(Sink.java:258) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151) at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418) at com.suse.manager.reactor.PGEventStream.processEvents(PGEventStream.java:141) at com.suse.manager.reactor.PGEventStream.lambda$null$0(PGEventStream.java:127) at com.redhat.rhn.frontend.events.TransactionHelper.run(TransactionHelper.java:62) at com.redhat.rhn.frontend.events.TransactionHelper.handlingTransaction(TransactionHelper.java:46) at com.suse.manager.reactor.PGEventStream.lambda$notification$2(PGEventStream.java:126) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at path $ at com.google.gson.internal.bind.JsonTreeReader.expect(JsonTreeReader.java:161) at com.google.gson.internal.bind.JsonTreeReader.beginObject(JsonTreeReader.java:87) at com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeAdapterFactory.java:183) at com.google.gson.internal.bind.MapTypeAdapterFactory$Adapter.read(MapTypeAdapterFactory.java:145) at com.google.gson.Gson.fromJson(Gson.java:888) For me it looks like an issue on the Uyuni, but can't found the issue. Who can help ? Best regards Alexander DXC Technology Company -- This message is transmitted to you by or on behalf of DXC Technology Company or one of its affiliates. It is intended exclusively for the addressee. The substance of this message, along with any attachments, may contain proprietary, confidential or privileged information or information that is otherwise legally exempt from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate any part of this message. If you have received this message in error, please destroy and delete all copies and notify the sender by return e-mail. Regardless of content, this e-mail shall not operate to bind DXC Technology Company or any of its affiliates to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. --. -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

1 0

[uyuni-users] Minions not connect to server
by Cristian Gherman 20 May '19

20 May '19

Hello, I have 50 systems managed by a Uyuni server. From this 7 of the not reconnect to server from 2 days. (Uyuni is 4.0 RC1 on OpensuseLeap). I restart all, minions and server with same results If I check from salt console they are ok, execute all comands. Where I can check the issue? I deleted the system from Uyuni but I can't readd as managed server. (with same hostname) What you suggest? Thanks in advance for any replay -- Cristian Gherman Support / PHP developer cristian.gherman(a)reea.net | www.reea.net | +4 0365410942

2 3

[uyuni-users] change SUSE products
by Haupt, Torsten 30 Apr '19

30 Apr '19

Hello, I want to change /update my SUSE products in Uyuni. I already configured repos for SLES12 some time ago. Now I want to add SLES15, but the GUI shows "Server error, please check log files.". And in rhn_web_ui.log I find: 2019-04-15 10:46:01,798 [ajp-apr-0:0:0:0:0:0:0:1-8009-exec-14] WARN com.redhat.rhn.manager.content.ContentSyncManager - Error reading UUID: /etc/zypp/credentials.d/SCCcredentials (No such file or directory) There is no SCCcredentials file and the folder is empty. What is going wrong and how can I add and change new SLES products? Regards Torsten -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

5 16

[uyuni-users] Service management via systemd for system/minon
by Cristian Gherman 17 Apr '19

17 Apr '19

Hello, I like to know if service management - via salt and systemd - for system exist or will be at some point implemented. Salt can manage services easely: - enable/disable service, - start/stop/restart service - show a lot of info about service And I think this feature on Uyuni will be helpfull. PS: I done this with a simple interface writen in PHP wich connect to salt-api. Thanks -- Cristian Gherman -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

2 1

[uyuni-users] Bootstrapped salt minions never appear as systems
by David Mace 16 Apr '19

16 Apr '19

Hi, so this was working initially, but something has broke. I am running Uyuni 4.0.1 stable on openSUSE 42.3 host. A new openSUSE Leap 15.0 minion is bootstrapped using bootstrap.sh which was generated using mgr-bootstrap. It joins Salt master and the key shows using command: salt-key -L But the minion never appears in Systems > Systems List Viewing the Salt message bus using salt-run state.event pretty=True I see this: salt/job/20190411153502494691/new { "_stamp": "2019-04-11T14:35:02.495370", "arg": [], "fun": "mgractionchains.resume", "jid": "20190411153502494691", "minions": [ "minion.domain.co.uk" ], "missing": [], "tgt": "minion.domain.co.uk", "tgt_type": "glob", "user": "salt" } salt/job/20190411153502494691/ret/minion.domain.co.uk { "_stamp": "2019-04-11T14:35:06.850239", "cmd": "_return", "fun": "mgractionchains.resume", "fun_args": [], "id": "minion.domain.co.uk", "jid": "20190411153502494691", "metadata": { "suma-action-chain": true }, "out": "nested", "retcode": 254, "return": "'mgractionchains.resume' is not available.", "success": false } >From the minion if I do a salt-call state.apply I get this error: minion.domain.co.uk:~ # salt-call state.apply [WARNING ] /var/cache/salt/minion/extmods/grains/__pycache__/cpuinfo.cpython- 36.py:20: DeprecationWarning: Use of 'salt.utils.which_bin' detected. This function has been moved to 'salt.utils.path.which_bin' as of Salt 2018.3.0. This warning will be removed in Salt Neon. [ERROR ] Error encountered during module reload. Modules were not reloaded. [WARNING ] /var/cache/salt/minion/extmods/modules/udevdb.py:24: DeprecationWarning: Use of 'salt.utils.which_bin' detected. This function has been moved to 'salt.utils.path.which_bin' as of Salt 2018.3.0. This warning will be removed in Salt Neon. [ERROR ] Template was specified incorrectly: False [ERROR ] Template was specified incorrectly: False local: Data failed to compile: ---------- Specified SLS packages.packages_7a5b9695fb48e3a146f6b8d35caf5e2a in saltenv base is not available on the salt master or through a configured fileserver ---------- Specified SLS custom.custom_7a5b9695fb48e3a146f6b8d35caf5e2a in saltenv base is not available on the salt master or through a configured fileserver Not sure where else to look for errors? -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

4 7

Re: [uyuni-users] Bootstrapped salt minions never appear as systems
by Strahil Nikolov 12 Apr '19

12 Apr '19

I'm quite new to the list, but the only thing that helps recover the SUMA 3.2 (that's what I have as experience) is to do a full reboot. If possible - try a reboot and check. If somebody more experienced can help you - it will be nice to learn how they do it. best Regards, Strahil Nikolov Hi, I also realised there have been no tasks scheduled or run in Schedule > Pending Actions or Schedule > Completed Actions since yesterday 10:25. I have restarted taskomatic since then. Is there something wrong with my database? Cheers -----Original Message----- Date: Fri, 12 Apr 2019 11:30:55 +0000 (UTC) Subject: Re: [uyuni-users] Bootstrapped salt minions never appear as systems To: uyuni-users(a)opensuse.org, David Mace <david(a)macemail.co.uk> From: Strahil Nikolov <hunter86_bg(a)yahoo.com> Hi David, I also have an openSuSE 15 minion and it joined properly. Here is what I did . 1. Checked what is the expected channel name so the bootstrap repo will be successfully created. -> /usr/share/susemgr/mgr_bootstrap_data.py 2. Created the channel with the same name and added several repos Mines are: oss/nonoss base oss/nonoss updates SLE15-uyuni-client-tools 3. Created the bootstrap repo mgr-create-bootstrap-repo 4. Created bootstrap script via web and edited it manually via cli to add the sle15 key 5. Bootstraped via web filling everything necessary. For bootstraping I have used the ip of the machine , but most probably it will work via hostname. Best Regards, Strahil Nikolov В петък, 12 април 2019 г., 6:37:09 ч. Гринуич-4, David Mace <david(a)macemail.co.uk> написа: Hi, so this was working initially, but something has broke. I am running Uyuni 4.0.1 stable on openSUSE 42.3 host. A new openSUSE Leap 15.0 minion is bootstrapped using bootstrap.sh which was generated using mgr-bootstrap. It joins Salt master and the key shows using command: salt-key -L But the minion never appears in Systems > Systems List Viewing the Salt message bus using salt-run state.event pretty=True I see this: salt/job/20190411153502494691/new { "_stamp": "2019-04-11T14:35:02.495370", "arg": [], "fun": "mgractionchains.resume", "jid": "20190411153502494691", "minions": [ "minion.domain.co.uk" ], "missing": [], "tgt": "minion.domain.co.uk", "tgt_type": "glob", "user": "salt" } salt/job/20190411153502494691/ret/minion.domain.co.uk { "_stamp": "2019-04-11T14:35:06.850239", "cmd": "_return", "fun": "mgractionchains.resume", "fun_args": [], "id": "minion.domain.co.uk", "jid": "20190411153502494691", "metadata": { "suma-action-chain": true }, "out": "nested", "retcode": 254, "return": "'mgractionchains.resume' is not available.", "success": false } >From the minion if I do a salt-call state.apply I get this error: minion.domain.co.uk:~ # salt-call state.apply [WARNING ] /var/cache/salt/minion/extmods/grains/__pycache__/cpuinfo.cpython- 36.py:20: DeprecationWarning: Use of 'salt.utils.which_bin' detected. This function has been moved to 'salt.utils.path.which_bin' as of Salt 2018.3.0. This warning will be removed in Salt Neon. [ERROR ] Error encountered during module reload. Modules were not reloaded. [WARNING ] /var/cache/salt/minion/extmods/modules/udevdb.py:24: DeprecationWarning: Use of 'salt.utils.which_bin' detected. This function has been moved to 'salt.utils.path.which_bin' as of Salt 2018.3.0. This warning will be removed in Salt Neon. [ERROR ] Template was specified incorrectly: False [ERROR ] Template was specified incorrectly: False local: Data failed to compile: ---------- Specified SLS packages.packages_7a5b9695fb48e3a146f6b8d35caf5e2a in saltenv base is not available on the salt master or through a configured fileserver ---------- Specified SLS custom.custom_7a5b9695fb48e3a146f6b8d35caf5e2a in saltenv base is not available on the salt master or through a configured fileserver Not sure where else to look for errors? -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

1 0

[uyuni-users] Error during applying the bootstrap state, message: Response code: 500
by Pavel Arnošt 12 Apr '19

12 Apr '19

Hi, I have fresh installation of Uyuni 4.0.1 on fully updated Leap 42.3 and I have problems bootstrapping minions on /rhn/manager/systems/bootstrap page. After click on "Bootstrap" button, it shows " Error during applying the bootstrap state, message: Response code: 500". I didn't do any configuration - I just created admin user. I traced error to salt-api that logs following while bootstrapping minion (fqdn of minion is replaced with "minion.domain"): [DEBUG ] Rendered data from file: /etc/salt/roster: # Sample salt-ssh config file #web1: # host: 192.168.42.1 # The IP addr or DNS hostname # user: fred # Remote executions will be executed as user fred # passwd: foobarbaz # The password to use for login, if omitted, keys are used # sudo: True # Whether to sudo to root, not enabled by default #web2: # host: 192.168.42.2 # Automatically added by "salt" at 2019-04-08T19:44:36.714140 None: host: None user: root passwd: # Automatically added by "salt" at 2019-04-08T19:54:16.464249 None: host: None user: root passwd: [ERROR ] Unable to render roster file: while constructing a mapping in "<unicode string>", line 11, column 1: None: ^ found conflicting ID 'None' in "<unicode string>", line 16, column 1: None: ^ [DEBUG ] Matched minions: {} [INFO ] [u'minion.domain'] [DEBUG ] Error while processing request for: /run Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/salt/netapi/rest_cherrypy/app.py", line 858, in hypermedia_handler ret = cherrypy.serving.request._hypermedia_inner_handler(*args, **kwargs) File "/usr/lib/python2.7/site-packages/cherrypy/_cpdispatch.py", line 61, in __call__ return self.callable(*self.args, **self.kwargs) File "/usr/lib/python2.7/site-packages/salt/netapi/rest_cherrypy/app.py", line 2135, in POST 'return': list(self.exec_lowstate()), File "/usr/lib/python2.7/site-packages/salt/netapi/rest_cherrypy/app.py", line 1185, in exec_lowstate ret = self.api.run(chunk) File "/usr/lib/python2.7/site-packages/salt/netapi/__init__.py", line 75, in run return l_fun(*f_call.get('args', ()), **f_call.get('kwargs', {})) File "/usr/lib/python2.7/site-packages/salt/netapi/__init__.py", line 140, in ssh return ssh_client.cmd_sync(kwargs) File "/usr/lib/python2.7/site-packages/salt/client/ssh/client.py", line 179, in cmd_sync **kwargs) File "/usr/lib/python2.7/site-packages/salt/client/ssh/client.py", line 141, in cmd **kwargs) File "/usr/lib/python2.7/site-packages/salt/client/ssh/client.py", line 73, in _prep_ssh return salt.client.ssh.SSH(opts) File "/usr/lib/python2.7/site-packages/salt/client/ssh/__init__.py", line 233, in __init__ self._update_targets() File "/usr/lib/python2.7/site-packages/salt/client/ssh/__init__.py", line 401, in _update_targets if salt.utils.network.is_reachable_host(hostname): File "/usr/lib/python2.7/site-packages/salt/utils/network.py", line 236, in is_reachable_host assert type(socket.getaddrinfo(entity_name, 0, 0, 0, 0)) == list TypeError: getaddrinfo() argument 1 must be string or None What am I doing wrong? Thanks, Regards, Pavel -- To unsubscribe, e-mail: uyuni-users+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-users+owner(a)opensuse.org

2 2