- ARCHIVED: Uyuni Development

[uyuni-devel] Cobbler system add fails with exception
by Strahil Nikolov 07 Dec '19

07 Dec '19

Hello Community, I'm trying to setup a fully automated deployment with Uyuni and cobbler, but it seems that there is something wrong with my setup. When I run 'uyuni:/etc/cobbler # cobbler system add --help' Traceback (most recent call last): File "/usr/bin/cobbler", line 35, in <module> sys.exit(app.main()) File "/usr/lib/python3.6/site-packages/cobbler/cli.py", line 745, in main rc = cli.run(sys.argv) File "/usr/lib/python3.6/site-packages/cobbler/cli.py", line 358, in run self.object_command(object_type, object_action) File "/usr/lib/python3.6/site-packages/cobbler/cli.py", line 428, in object_command network_interface_fields, settings, object_action) File "/usr/lib/python3.6/site-packages/cobbler/cli.py", line 238, in add_options_from_fields _add_parser_option_from_field(parser, field, settings) File "/usr/lib/python3.6/site-packages/cobbler/cli.py", line 209, in _add_parser_option_from_field raise Exception("field %s default value (%s) is not listed in choices (%s)" % (name, default, str(choices))) Exception: field redhat_management_key default value (<<inherit>>) is not listed in choices (str) I got a traceback that 'redhat_management_key' default value is not listed in choices. My guess is that this should not happen,but my python skills are quite limited. As I have a separate NIC (separate VLAN) for the Uyuni's cobbler, I wanted to be able to pass in kickstart/autoyast 's script the network settings (via system variables) before powering off the machine. Then an automated process will change the VLAN (and PXE boot) of the client's NIC and will start it up. Once it's available, it will be bootstrapped and additional configuration can be done on the permanent address. Also, it seems that bootstrapping RHEL 7 via cobbler is failing, so that cannot be done during initial deployment. Most probably the 'spacewalk/redhat_register' snippet has an issue and cobbler is not expanding the it. Thanks for reading such a long post and any help is appreciated, maybe there is already a fix. If not - I can provide details in an issue. Best Regards, Strahil Nikolov -- To unsubscribe, e-mail: uyuni-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-devel+owner(a)opensuse.org

2 5

[uyuni-devel] New repository URLs for Uyuni Master/Develop Server and Proxy
by Julio Gonzalez 30 Oct '19

30 Oct '19

Hi everyone. The URLs for Uyuni Master (AKA Develop), Server and Proxy are now as follows: Server: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Master… Proxy: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Master… The reason for this change is that we plan to replicate this for Stable as well, so in the future changing the Uyuni version will not affect the repositories. I repeat, because this is important: this change does NOT affect Stable for now. When the time comes, we will warn about it at the mailing lists, and at the release notes (change does not affect Client Tools neither for Master/Develop or Stable, and will never affect them). # NEW INSTALLATIONS The website is now updated, so if you install a new Uyuni Master environment, you will be using the new URLs. # EXISTING INSTALLATIONS For existing installations, remember: those are NOT intended for production, and updating is NOT supported. Still, if you want to do things on your own then, at the server: 1. Update your `.repo` file for the server with the new URL. 2. Update at least `spacewalk-utils` package 3. Use `spacewalk-common-channels` to add the channels you need: uyuni-proxy- devel (and uyuni-server-devel if for some reason you already have the previous one). 4. If you don't need the previous channels, remove them: uyuni-proxy-devel- leap-151 (and uyuni-server-devel-leap-151 if for some reason you have it). Remember to remove the repositories as well. Best regards. -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

[uyuni-devel] Uyuni chat now available at Gitter!
by Julio Gonzalez 18 Oct '19

18 Oct '19

Hi all, We are now starting a PoC to consider moving our IRC channel at Freenode to Gitter. So as part of the PoC, our Gitter is now available at: https://gitter.im/uyuni-project/ Among other benefits, Gitter provides provide: - Rich text and files (and an easier way for people to provide commands, logs, etc). - Notifications - History (without bouncers). - Easy linking to GitHub issues. It also as an IRC gateway, for those that want to use an IRC client: https://irc.gitter.im/ We invite you all to join, and give it a try during the next two weeks. Meanwhile, we will be collecting feedback from you at Gitter, IRC and the uyuni-devel and uyuni-users mailing lists [1] With the experience and the feedback, we will decide in two weeks. Best regards, and have a nice weekend! [1] https://www.uyuni-project.org/pages/contact.html#ml -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

[uyuni-devel] Moving IRC channel to Gitter
by Julio Gonzalez 07 Oct '19

07 Oct '19

Hi all, We are considering moving our IRC channel at Freenode to Gitter. We would like to give it a try (meaning we'd keep both IRC and Gitter in parallel for some time), and mid-term replace it if we find the test satisfactory. Among other benefits, Gitter would provide: - Rich text and files (and an easier way for people to provide commands, logs, etc). - Notifications - History (without bouncers). - Easy linking to GitHub issues. But, before starting testing anything, we would like to know what our community thinks about it. Best regards. -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

[uyuni-devel] Building the Java code
by Cedric Bosdonnat 02 Sep '19

02 Sep '19

Hi all, Now it is possible to build the Java code without any dependency on SUSE R&D internal resources. Check this page for updated informations on how to setup your environment: https://github.com/uyuni-project/uyuni/wiki/Java-Development-Environment What actually changed? Before we were manually maintaining an Apache Ivy repository with the JAR files built from the openSUSE / SLE RPMs needed to build. Since Friday this is no longer needed, but you need to install a tiny script called obs-to-maven that will create such a repository locally out of OBS packages. You can install obs-to-maven for your distro from this repository: https://build.opensuse.org/package/show/systemsmanagement:Uyuni:Utils/obs-t… Then all you need to get the dependencies is to run: cd $UYUNI_SRC/java; ant -f manager-build.xml ivy All those instructions and how to setup your development environment is fairly well documented on the wiki page. Have fun! -- Cedric Bosdonnat N��r��y隊[��x�z��칻�&ޢ��'��-��w�zf��쮞'^��~� ޮ�^�ˬz��

1 0

[uyuni-devel] Re: [uyuni-users] Fwd: openSUSE 15.1 tools repo sync errors?
by Strahil Nikolov 23 Aug '19

23 Aug '19

On August 23, 2019 5:06:33 PM GMT+03:00, Boris Manojlovic <boris(a)steki.net> wrote: >kernel-default but it is multiple packages that will trigger this >(same update as in SLE SP1 in which i first noticed this issue with >this specific changelog entry ) > >sw:~ # cat /etc/*rele* >NAME="openSUSE Leap" >VERSION="15.1 " >ID="opensuse-leap" >ID_LIKE="suse opensuse" >VERSION_ID="15.1" >PRETTY_NAME="openSUSE Leap 15.1" >ANSI_COLOR="0;32" >CPE_NAME="cpe:/o:opensuse:leap:15.1" >BUG_REPORT_URL="https://bugs.opensuse.org" >HOME_URL="https://www.opensuse.org/" >Spacewalk release 4.0 (Smile) >sw:~ # rpm -q --changelog kernel-default |grep -A 5 -B1 >'reclaimed_journal_buckets' >* Mon Jul 15 2019 colyli(a)suse.de >- bcache: add reclaimed_journal_buckets to struct cache_set > (bsc#1140652). >- bcache: performance improvement for btree_flush_write() > (bsc#1140652). >- bcache: fix race in btree_flush_write() (bsc#1140652). >- bcache: remove retry_flush_write from struct cache_set >-- >* Mon Jul 15 2019 colyli(a)suse.de >- bcache: add reclaimed_journal_buckets to struct cache_set > (bsc#1140652). >- bcache: performance improvement for btree_flush_write() > (bsc#1140652). >- bcache: fix race in btree_flush_write() (bsc#1140652). >- bcache: remove retry_flush_write from struct cache_set >sw:~ # > >On Fri, Aug 23, 2019 at 12:46 AM Strahil Nikolov ><hunter86_bg(a)yahoo.com> wrote: >> >> >> On August 21, 2019 12:21:29 PM GMT+03:00, Boris Manojlovic ><boris(a)steki.net> wrote: >> >> >Hi list, >> > >> >reason why all of you had issues with updates from opensuse 15.1 is >> >kernel update that originated from suse sources (or someone made >> >exactly SAME kind of mistake) >> > >> >in source code (database code) you will find your mentioned unique >> >index creation code >> > >> >``` >> >CREATE UNIQUE INDEX rhn_pkg_clr_pid_cld_uq >> > ON rhnPackageChangeLogRec (package_id, changelog_data_id) >> > NOLOGGING >> > TABLESPACE [[32m_tbs]]; >> >``` >> > >> >so what happens in other part of code is next >> >get changelog data from rpm, insert it into db line by line (all >text >> >as one row per changelog entry ) >> >some other stuff in between >> >try adding rpm package changelog info into table as bellow >(arbitrary >> >values 10 and 3 just to show point) >> >``` >> >info into packagechangelogrec ( pkg_id=10 , chg_id=3 ,...); >> >info into packagechangelogrec ( pkg_id=10 , chg_id=3 ,...); <- >second >> >one fails with unique index problerm >> >` >> >insert will of course fail with given error (from log file pasted) >as >> >package has exactly same changelog entries. >> > >> >hope this helps someone in future to debug this kind of error >> > >> >P.S. >> >sorry for not responding to thread as is, simply was not subscribed >> >before :) >> > >> >P.P.S. >> > >> >Not sure list got it as i still did not confirm my subscription >before >> >sending... >> > >> > >> >Is it fixed, as I thought my Uyuni DB 'ended' and redeployed again >:) ? >> > >> >I will need to create all repos again. >> > >> >Best Regards, >> >Strahil Nikolov >> >> >> It's definitely not fixed: >> >> 01:39:50 01:39:50 Importing packages to DB: >Importing packages: >|--------------------------------------------------| 0.21% 01:41:24 >0.21 % Importing packages: >|--------------------------------------------------| 0.38% 01:42:40 >duplicate key value violates unique constraint "rhn_pkg_clr_pid_cld_uq" >DETAIL: Key (package_id, changelog_data_id)=(36047, 35803) already >exists. 01:42:40 Unexpected error: 01:42:40 Traceback (most recent call >last): File >"/usr/lib/python3.6/site-packages/spacewalk/satellite_tools/reposync.py", >line 568, in sync ret = self.import_packages(plugin, data['id'], >url, is_non_local_repo) File >"/usr/lib/python3.6/site-packages/spacewalk/satellite_tools/reposync.py", >line 1086, in import_packages importer.run() File >"/usr/lib/python3.6/site-packages/spacewalk/server/importlib/importLib.py", >line 764, in run self.submit() File >"/usr/lib/python3.6/site-packages/spacewalk/server/importlib/packageImport.py", >line 343, in submit transactional=self.transactional) File >"/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", >line 853, in processPackages transactional=transactional) File >"/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", >line 2158, in __processObjectCollection__ return self.__doDML(dml) >File >"/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", >line 2263, in __doDML self.__doInsert(dml.insert, dml.tables) >File >"/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", >line 2270, in __doInsert self.__doInsertTable(tname, dict) File >"/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", >line 2285, in __doInsertTable insertObj.query(hash) File >"/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backendLib.py", >line 459, in query executeStatement(statement, values, chunksize) >File >"/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backendLib.py", >line 484, in executeStatement count += >statement.executemany(**tempdict) File >"/usr/lib/python3.6/site-packages/spacewalk/server/rhnSQL/sql_base.py", >line 159, in executemany return >self._execute_wrapper(self._executemany, *p, **kw) File >"/usr/lib/python3.6/site-packages/spacewalk/server/rhnSQL/driver_postgresql.py", >line 298, in _execute_wrapper retval = function(*p, **kw) File >"/usr/lib/python3.6/site-packages/spacewalk/server/rhnSQL/driver_postgresql.py", >line 348, in _executemany self._real_cursor.executemany(self.sql, >all_kwargs) psycopg2.IntegrityError: duplicate key value violates >unique constraint "rhn_pkg_clr_pid_cld_uq" DETAIL: Key (package_id, >changelog_data_id)=(36047, 35803) already exists. >> >> Does anyone know the names of the offending packages ? >> >> 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 Adding uyuni-devel list. I hope someone in the dev can assist us. Best Regards, Strahil Nikolov -- To unsubscribe, e-mail: uyuni-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-devel+owner(a)opensuse.org

1 0

[uyuni-devel] Documentation Bug in Uyuni 4.0.2 Reference guide (PDF)
by Strahil Nikolov 05 Aug '19

05 Aug '19

Hello All, Can someone rebuild the reference guide for Uyuni 4.0.2 ,as there is a difference between the PDF and the HTML ? I have described the issue in : https://github.com/uyuni-project/uyuni-docs/issues/6 Best Regards, Strahil Nikolov -- To unsubscribe, e-mail: uyuni-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-devel+owner(a)opensuse.org

1 0

[uyuni-devel] New website and branding
by Julio Gonzalez 02 Aug '19

02 Aug '19

Together with the announcement of Uyuni 4.0.2 we are happy to present our new website and branding: https://www.uyuni-project.org/ You can also check the updated documentation as HTML, and with a search engine working at: https://www.uyuni-project.org/uyuni-docs/uyuni/index-uyuni.html What's more, you can even contribute to the documentation from there! We hope you will enjoy it, and we will be happy to receive your feedback and contributions. Happy hacking! -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

[uyuni-devel] Uyuni 4.0.2 is released!
by Julio Gonzalez 02 Aug '19

02 Aug '19

Hello everyone, We are happy to announce the immediate availability of Uyuni 4.0.2, our third Uyuni release! At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 4.0.2, including the release notes, documentation, requirements and setup instructions. ===================================== IMPORTANT: If you are migrating from 4.0.1 check the release notes [1], as a special procedure is needed for the server! ===================================== This is the list of highlights for this release: - Base system upgrade to openSUSE Leap 15.1 - Salt 2019.2.0 - Prometheus Monitoring - Content lifecycle management - Virtualization management for Salt minions - Updated Documentation Structure - Improved logging for Salt Remote Command Page - Support for more Distributions as Clients - EoL for openSUSE Leap 42.3 clients - Salt Rate Limiting (Batching) - Product Information Loaded from SCC - Image build host with SLES 12 SP4 - Updated backend for communicating with SCC - XMLRPC API changes - Support for Ubuntu Clients - Change behavior on token refresh - New option to force regeneration of channel metadata - New products supported - Package download endpoint override - Technical preview: Single Sign-On (SSO) Please check the release notes for full details. Remember that Uyuni follows a rolling release planning, so there will be no maintenance of 4.0.2, but a new version with bugfixes and most probably new features. We hope you will enjoy Uyuni 4.0.2 and invite everyone of you to send us your feedback [1] and of course your patches, if you can contribute. Happy hacking! [1] https://www.uyuni-project.org/doc/4.0.2/release-notes-uyuni-server.html [2] https://www.uyuni-project.org/pages/contact.html -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 0

[uyuni-devel] Re: [uyuni-users] need assistance with debugging bootstrap issues
by Strahil Nikolov 16 Jul '19

16 Jul '19

Hi Chris, thanks for your hint. I have tested adding a fresh openSUSE 15.1 and everything is fine until I have noticed that every minute the Uyuni is doing package refresh (8 refresh per minute) and never stops. Running it manually passes in 3.22s . Now I have to find the reason behind this constant running of package refresh. Adding uyuni-devel list. Best Regards, Strahil Nikolov В вторник, 9 юли 2019 г., 17:47:16 ч. Гринуич+3, Cristian Gherman <cristian.gherman(a)reea.net> написа: I had to change the id of minions in something: fe-1.blabla.com => fe-1-prod.blabla,com If I use previous names , they are not added to Uyuni any more. Cristian Gherman -------- Forwarded Message -------- Subject: Re: [uyuni-users] need assistance with debugging bootstrap issues Date: Tue, 9 Jul 2019 13:55:59 +0000 (UTC) From: Strahil Nikolov <hunter86_bg(a)yahoo.com> To: Cristian Gherman <cristian.gherman(a)reea.net> Hi Christian, thanks for the fast reply. Already done all of these. The new key is accepted , but the machines are not added. I even used "snapper" to rollback one of the VMs to openSUSE 15.0 in order to check bootstraping. The results are the same. Rebooting Uyuni doesn't solve the issue :) Any ideas appreciated. Best Regards, Strahil Nikolov В вторник, 9 юли 2019 г., 9:52:05 ч. Гринуич-4, Cristian Gherman <cristian.gherman(a)reea.net> написа: Hello, Can you try this: - remove minion key from master - stop the salt-minion on VM's - remove minion key from /etc/salt/pki/ - change the minion id in /etc/minion_id - change the machine id in /etc/machine-id with command systemd-machine-id-setup - start the salt-minion on VM's - accept new keys, check if minons is added on Uyuni This steps helped me with some stoborn minions some time ago. Cristian Gherman On 7/9/19 4:39 PM, Strahil Nikolov wrote: > Hello All, > can you assist me by guiding me in the correct direction? > Yesterday I found out that all my clients (4 openSUSE 15.1) are not reporting for the past 3 days.I tried to refresh , but it didn't do anything . > > Then I removed the VMs and tried to add them, but after accepting the salt key - the VM is not added as a system. > I have checked the logs and I see a lot of errors , one of them is : > 2019-07-09 16:26:24,719 [salt-event-thread-1] ERROR com.suse.manager.reactor.PGEventListener - Unexpected exception while executing a MessageAction 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:483) > at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472) > 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) > ... 30 more > 2019-07-09 16:26:24,719 [salt-event-thread-4] ERROR com.redhat.rhn.frontend.events.TransactionHelper - java.lang.ClassCastException 2019-07-09 16:26:24,719 [salt-event-thread-4] ERROR com.redhat.rhn.frontend.events.TransactionHelper - Additional Exception during Exception handling java.lang.ClassCastException > 2019-07-09 16:26:24,720 [salt-event-thread-3] ERROR com.redhat.rhn.frontend.events.TransactionHelper - java.lang.ClassCastException 2019-07-09 16:26:24,719 [salt-event-thread-1] ERROR com.redhat.rhn.frontend.events.TransactionHelper - com.suse.manager.reactor.PGEventListenerException > 2019-07-09 16:26:24,720 [salt-event-thread-5] ERROR com.redhat.rhn.frontend.events.TransactionHelper - com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected NUMBER but was BEGIN_OBJECT at path $.retcode > > Any ideas how to debug this one? Which logs should I check ? > Maybe someone has already had a similar situation... > > 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 -- To unsubscribe, e-mail: uyuni-devel+unsubscribe(a)opensuse.org To contact the owner, e-mail: uyuni-devel+owner(a)opensuse.org

1 3