- Uyuni Users - openSUSE Mailing Lists

migrate from RMT to Uyuni while patching SLES15 SP2 systems to SP3?

by Heiner Wulfhorst

Hi list! I was asked to patch our SLES15 SP2 systems to SP3. Currently they are connected to SUSE RMT. Do you think that is a good opportunity to also migrate them into our uyuni? Pros: * I don't have to touch every system twice * am able to do any post-upgrade task faster and more easy as i have "the power of salt" Con: Double risk for incidents Or would you separate that change? -> why? I think the biggest risk lies within SP Upgrade, am i right? Is there any "compatibility check" / dry run i can do on target systems to see how they would be affected by the Upgrade before i run it? Or anything else to minimize risk? What are your thoughts about this? BR Heiner

3 days, 8 hours

1
0
0 0

Recent errors syncing EL7's EPEL repo

by Simon Avery

Hi Folks, Anyone else having sync issues with EL7's EPEL repo for the past week or so? I've split out and recreated the repo on Uyuni but it still bombs out when importing one of the errata files. My hunch is this is actually an EPEL issue rather than a Uyuni one, but the pertinent error makes me wonder if this is a new thing that's going to need extra handling in Uyuni? "CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck"" Things were okay a week or so-ish ago and I made no changes on my side, but started getting sync failures late last week, or over the weekend. Thanks Example repo url; https://www.mirrorservice.org/sites/dl.fedoraproject.org/pub/epel/7/x86_64/ 2021/09/08 13:35:47 +01:00 Add Patch FEDORA-EPEL-2019-3630e34c31 2021/09/08 13:35:47 +01:00 Add Patch FEDORA-EPEL-2018-81bb24fe00 2021/09/08 13:35:47 +01:00 Add Patch FEDORA-EPEL-2018-6f7d6eeeed 2021/09/08 13:35:47 +01:00 Syncing 4684 new patch(es) to channel. 2021/09/08 13:36:02 +01:00 Unexpected error: <class 'psycopg2.errors.CheckViolation'> 2021/09/08 13:36:02 +01:00 Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/spacewalk/satellite_tools/reposync.py", line 600, in sync self.import_updates(plugin) File "/usr/lib/python3.6/site-packages/spacewalk/satellite_tools/reposync.py", line 741, in import_updates processed_updates_count = self.upload_updates(notices) File "/usr/lib/python3.6/site-packages/spacewalk/satellite_tools/reposync.py", line 967, in upload_updates importer.run() File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/importLib.py", line 778, in run self.submit() File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/errataImport.py", line 217, in submit dml = self.backend.processErrata(self.batch) File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", line 1011, in processErrata transactional=1) File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", line 2151, in __processObjectCollection return self.__processObjectCollection__(objColl, parentTable, childDict, **kwargs) File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", line 2322, in __processObjectCollection__ return self.__doDML(dml) File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", line 2427, in __doDML self.__doInsert(dml.insert, dml.tables) File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", line 2434, in __doInsert self.__doInsertTable(tname, dict) File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backend.py", line 2449, in __doInsertTable insertObj.query(hash) File "/usr/lib/python3.6/site-packages/spacewalk/server/importlib/backendLib.py", line 453, in query statement.execute_values(self._buildQuery(None), value_list, fetch=False, page_size=10_000) File "/usr/lib/python3.6/site-packages/spacewalk/server/rhnSQL/sql_base.py", line 166, in execute_values return self._execute_wrapper(self._execute_values, sql, argslist, template, page_size, fetch) File "/usr/lib/python3.6/site-packages/spacewalk/server/rhnSQL/driver_postgresql.py", line 299, in _execute_wrapper retval = function(*p, **kw) File "/usr/lib/python3.6/site-packages/spacewalk/server/rhnSQL/driver_postgresql.py", line 353, in _execute_values results = psycopg2.extras.execute_values(self._real_cursor, sql, argslist, template=template, page_size=page_size, fetch=fetch) File "/usr/lib64/python3.6/site-packages/psycopg2/extras.py", line 1289, in execute_values cur.execute(b''.join(parts)) psycopg2.errors.CheckViolation: new row for relation "rhnerrata" violates check constraint "rhn_errata_adv_status_ck" DETAIL: Failing row contains (11847, FEDORA-EPEL-2021-aa19cf2506, Product Enhancement Advisory, FEDORA-EPEL-2021-aa19cf2506, 200, Fedora EPEL 7, Rebuild for Knot DNS 3.1, knot-resolver-5.4.1-2.el7, , , 2021-09-06 03:52:14-01, 2021-09-06 03:52:14-01, null, null, 1, null, updates(a)fedoraproject.org<mailto:updates@fedoraproject.org>, 2021-09-08 11:34:52.299009-01, 2021-09-08 11:34:52.299009-01, 2021-09-08 11:34:52.299009-01, 1, pending). Simon Avery Linux Systems Administrator

1 week, 5 days

2
2
0 0

Packages not updated after update 2021:06 -> 2021:08

by Bidault, Philippe

Hi all ¡ I have just updated Uyuni to 2021:08, and have noticed 6 packages not being update because of a vendor change: uyuni:~ # zypper update Loading repository data... Reading installed packages... The following 6 package updates will NOT be installed: mgr-osa-dispatcher python3-mgr-osa-common python3-mgr-osa-dispatcher python3-rhnlib python3-suseRegisterInfo suseRegisterInfo Nothing to do. uyuni:~ # zypper update mgr-osa-dispatcher python3-mgr-osa-common python3-mgr-osa-dispatcher python3-rhnlib python3-suseRegisterInfo suseRegisterInfo Loading repository data... Reading installed packages... There is an update candidate for 'python3-rhnlib' from vendor 'obs://build.opensuse.org/systemsmanagement:Uyuni', while the current vendor is 'SUSE LLC https://www.suse.com/'. Use 'zypper install python3-rhnlib-4.3.1-1.2.uyuni1.noarch' to install this candidate. There is an update candidate for 'suseRegisterInfo' from vendor 'obs://build.opensuse.org/systemsmanagement:Uyuni', while the current vendor is 'SUSE LLC https://www.suse.com/'. Use 'zypper install suseRegisterInfo-4.3.1-1.2.uyuni1.noarch' to install this candidate. There is an update candidate for 'mgr-osa-dispatcher' from vendor 'obs://build.opensuse.org/systemsmanagement:Uyuni', while the current vendor is 'SUSE LLC https://www.suse.com/'. Use 'zypper install mgr-osa-dispatcher-4.3.1-1.2.uyuni1.noarch' to install this candidate. There is an update candidate for 'python3-mgr-osa-common' from vendor 'obs://build.opensuse.org/systemsmanagement:Uyuni', while the current vendor is 'SUSE LLC https://www.suse.com/'. Use 'zypper install python3-mgr-osa-common-4.3.1-1.2.uyuni1.noarch' to install this candidate. There is an update candidate for 'python3-mgr-osa-dispatcher' from vendor 'obs://build.opensuse.org/systemsmanagement:Uyuni', while the current vendor is 'SUSE LLC https://www.suse.com/'. Use 'zypper install python3-mgr-osa-dispatcher-4.3.1-1.2.uyuni1.noarch' to install this candidate. There is an update candidate for 'python3-suseRegisterInfo' from vendor 'obs://build.opensuse.org/systemsmanagement:Uyuni', while the current vendor is 'SUSE LLC https://www.suse.com/'. Use 'zypper install python3-suseRegisterInfo-4.3.1-1.2.uyuni1.noarch' to install this candidate. Resolving package dependencies... Nothing to do. Do I have to change vendor for them and force the update or do I have to keep them like that ? Regards, Philippe. Philippe Bidault | Unix Engineer | Getronics ________________________________ M. 34617301667 | E. Philippe.Bidault(a)Getronics.com | W. www.getronics.com<https://www.getronics.com> [cid:3-lines_7512e235-163a-4853-8e4f-b0d4fc62ce73.png]<https://getronics.com/> 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/

2 weeks

2
4
0 0

Problems when using server-migrator.sh to get from 2021.02 to .08

by Heiner Wulfhorst

Hi List, first i ran zypper ref and zypper up susemanager which said " *No update candidate*, *The highest available version is already installed* , Nothing to do ": # *zypper ref* Repository 'Non-OSS Repository' is up to date. Repository 'Main Repository' is up to date. Repository 'Main Update Repository' is up to date. Repository 'Update Repository (Non-Oss)' is up to date. Repository 'uyuni-server-2021-02' is up to date. *All repositories have been refreshed.* # *zypper up susemanager* Loading repository data... Reading installed packages... *No update candidate for 'susemanager-4.2.8-1.1.uyuni.x86_64'. The highest available version is already installed.* Resolving package dependencies... *Nothing to do.* But then i got this error when running /usr/lib/susemanager/bin/ server-migrator.sh (for full output see attachment): Computing distribution upgrade... 5 Problems: Problem: nothing provides 'postgresql13' needed by the to be installed spacewalk-postgresql-4.3.1-1.2.uyuni1.noarch Problem: nothing provides 'libcrypt.so.1(XCRYPT_2.0)(64bit)' needed by the to be installed jabberd-sqlite-2.7.0-5.5.uyuni1.x86_64 Problem: nothing provides 'product(Leap) >= 15.3' needed by the to be installed product:Uyuni-Server-2021.08-0.x86_64 Problem: nothing provides 'product(Leap) >= 15.3' needed by the to be installed product:Uyuni-Server-2021.08-0.x86_64 Problem: nothing provides 'postgresql13' needed by the to be installed spacewalk-postgresql-4.3.1-1.2.uyuni1.noarch Problem: nothing provides 'postgresql13' needed by the to be installed spacewalk-postgresql-4.3.1-1.2.uyuni1.noarch Solution 1: Following actions will be done: deinstallation of spacewalk-postgresql-4.2.3-1.2.uyuni.noarch deinstallation of spacewalk-common-4.2.3-1.2.uyuni.noarch Solution 2: keep obsolete spacewalk-postgresql-4.2.3-1.2.uyuni.noarch Solution 3: break spacewalk-postgresql-4.3.1-1.2.uyuni1.noarch by ignoring some of its dependencies Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c/d/?] (c): c =================================================================== If you did not yet migrate the database to postgresql12, do so now by running /usr/lib/susemanager/bin/pg-migrate-10-to-12.sh Reboot system afterwards. =================================================================== After that error i ran zypper ref and zypper up susemanager again, which (whyever) then found this update for susemanager: # zypper ref Repository 'Non-OSS Repository' is up to date. Repository 'Main Repository' is up to date. Repository 'Main Update Repository' is up to date. Repository 'Update Repository (Non-Oss)' is up to date. Repository 'Uyuni Server Stable' is up to date. All repositories have been refreshed. # zypper up susemanager Loading repository data... Reading installed packages... Resolving package dependencies... The following package is going to be upgraded: susemanager 1 package to upgrade. Overall download size: 83.8 KiB. Already cached: 0 B. After the operation, additional 14.0 KiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving package susemanager-4.3.2-1.1.uyuni1.x86_64 (1/1), 83.8 KiB (197.6 KiB unpacked) Retrieving: susemanager-4.3.2-1.1.uyuni1.x86_64.rpm .............................................................................................[done] Checking for file conflicts: ....................................................................................................................[done] (1/1) Installing: susemanager-4.3.2-1.1.uyuni1.x86_64 ...........................................................................................[done] Executing %posttrans scripts ....................................................................................................................[done] After that i ran /usr/lib/susemanager/bin/server-migrator.sh again which then returned no more errors/problems and began to upgrade my system: <...> Executing %posttrans scripts ....................................................................................................................[done] Update notifications were received from the following packages: susemanager-schema-4.3.1-1.2.uyuni1.noarch (/var/adm/update-messages/susemanager-schema-4.3.1-1.2.uyuni1) View the notifications now? [y/n] (n): n There are running programs which still use files and libraries deleted or updated by recent upgrades. They should be restarted to benefit from the latest updates. Run 'zypper ps -s' to list these programs. Since the last system boot core libraries or services have been updated. Reboot is suggested to ensure that your system benefits from these updates. =================================================================== If you did not yet migrate the database to postgresql13, do so now by running /usr/lib/susemanager/bin/pg-migrate-x-to-y.sh Reboot system afterwards. =================================================================== What went wrong? Is there an error in the upgrade guide ( https://www.uyuni-project.org/doc/2021.08/uyuni_upgrade_guide.pdf)? Looks like at first try it is using leap/15.2 repos and at second try 15.3... BR, Heiner

2 weeks, 4 days

2
4
0 0

Uyuni Community Hours

by Julio Gonzalez

Join us one more month to learn and discuss about Uyuni! The latest developments around Uyuni are presented and the community can ask question, provide feedback, request or suggest features or enhancements, etc to the Product Owner and members of the development team. Agenda will be published in the Uyuni wiki: https://github.com/uyuni-project/uyuni/wiki/Uyuni-Community-Hours Uyuni Community Hours are held every last Friday of the month, at 4 PEM CET/CEST. Meetings are recorded and published in the Uyuni YouTube channel: https://www.youtube.com/channel/UCB0SkZFAw9vPCFeUIYqZQ5A NOTE: This schedule overrides the previous one and does not request attendance confirmation. ________________________________________________________________________________ Microsoft Teams meeting Join on your computer or mobile app Click here to join the meeting<https://teams.microsoft.com/l/meetup-join/19%3ameeting_ZjZlMWI0OTctNGMxZi00…> Learn More<https://aka.ms/JoinTeamsMeeting> | Meeting options<https://teams.microsoft.com/meetingOptions/?organizerId=ef7551ee-a699-477f-…> ________________________________________________________________________________

3 weeks, 3 days

1
0
0 0

Re: [EXTERNAL] Re: Error after upgrading to latest version

by Allen Beddingfield

I was finally able to get the time to complete this process. Your instructions were great, and worked perfectly. I was able to get upgraded to the latest version, with the May release as an interim - as you suggested. Thanks! Allen B. -- Allen Beddingfield Systems Engineer Office of Information Technology The University of Alabama Office 205-348-2251 allen(a)ua.edu <https://www.ua.edu/> ________________________________ From: Julio Gonzalez Sent: Friday, July 23, 2021 12:22 PM To: uyuni-users(a)opensuse.org; users(a)lists.uyuni-project.org Cc: Allen Beddingfield Subject: [EXTERNAL] Re: Error after upgrading to latest version On viernes, 23 de julio de 2021 16:44:17 (CEST) Allen Beddingfield wrote: > This is the output of "zypper dup". > > Loading repository data... > Reading installed packages... > Warning: You are about to do a distribution upgrade with all enabled > repositories. Make sure these repositories are compatible before you > continue. See 'man zypper' for more information about this command. > Computing distribution upgrade... > Nothing to do. > > I have a VM snapshot that I can revert. What I can't figure out how to do > is to upgrade only to 2020.07, instead of the current version, as required. > What would be the process to get to that intermediate version? I could > revert the snapshot, upgrade to 2020.07, then to the current version, if I > knew the steps to upgrade to that intermediate version. Thanks! > Allen B. There is a way, but unsupported. So I will do my best, but can tell you: "yeah, this will work for sure!" :-) We have Snapshots for the different versions, they are only used for reproducing migration bugs. The last one for the server on top of Leap 15.2 is at: https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Snapsh… So that means you can use a special procedure to migat to 2021.05 first: MIGRATING TO 2021.05 =================== # zypper ar https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Snapsh… uyuni-2021.05 # zypper in susemanager At this point you will have the migration script that was used to migrate from Uyuni on top Leap 15.1 to Uyuni on top of Leap 15.2 DO NOT RUN IT YET!!!!!! Edit the migration script, with vim or other editor: # vim /usr/lib/susemanager/bin/server-migrator.sh Change the line: zypper ar -n "Uyuni Server Stable" https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable… uyuni-server-stable To: zypper ar -n "Uyuni Server 2021.05" https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Snapsh… uyuni-2021.05 Run the script: # /usr/lib/susemanager/bin/server-migrator.sh This should take your system to openSUSE Leap 15.2 and Uyuni 2021.05, in terms of packaging. Run /usr/lib/susemanager/bin/pg-migrate-10-to-12.sh as instructed. DO NOT REBOOT YET. Check the current release notes for 2021.06 (yes), and run any manual steps documented between 2020.09 and 2021.05 (both included). Most of them could probably be skipped since they are about changing the vendor to openSUSE (and that should be done by server-migrator) but run them anyway, just in case. After all manual steps are executed, you can reboot. Check that the server is able to start, that the WebUI is loading, and then run some smoke tests, just in case (for example run a salt remote command against a couple of minions). If everything is working at this point, then you can migrate to 2021.06 MIGRATING TO 2021.06 =================== Add the Stable repository again: # zypper ar -n "Uyuni Server Stable" https://download.opensuse.org/repositories/systemsmanagement:/Uyuni:/Stable… uyuni-server-stable And run the regular procedure for the migration from 2021.05 to 2021.06 So as you can see, this is doing an upgrade in two steps: 2020.07 to 2021.05 first (Leap 15.3 to Leap 15.2) 2021.05 to 2021.06 then (Leap 15.2 to Leap 15.3) I never tried this, but should work :-) > > -- > Allen Beddingfield > Systems Engineer > Office of Information Technology > The University of Alabama > Office 205-348-2251 > allen(a)ua.edu > <https://www.ua.edu/> > > ________________________________ > From: Julio Gonzalez > Sent: Friday, July 23, 2021 9:40 AM > To: uyuni-users(a)opensuse.org; users(a)lists.uyuni-project.org > Cc: Allen Beddingfield > Subject: [EXTERNAL] Re: Error after upgrading to latest version > > On viernes, 23 de julio de 2021 16:31:16 (CEST) Allen Beddingfield wrote: > > I have three Uyuni servers that I've updated to the latest version. The > > first two went well. The third fails on the startup of Tomcat. This one > > was from an older revision. The other two were running an Uyuni version > > at > > Leap 15.2, but the one with the problem was old enough to be on 15.1. > > Not supported. That's why the release notes say: > > "You need at least Uyuni 2020.07 already installed to perform the upgrade." > > As that's the first version on top of openSUSE Leap 15.1 > > Let's see if we can help, but no promises :-) > > > I did > > "zypper up susemanager" > > Ran server-migrator.sh > > Then ran pg-migrate-10-to-13.sh > > All completed with no errors. > > > > On restart, there is an issue with Tomcat. This appears in the most > > recent > > catalina log: > > > > 23-Jul-2021 09:23:03.806 INFO [main] > > > > org.apache.catalina.startup.VersionLoggerListener.log Server version name: > > Apache Tomcat/9.0.36 23-Jul-2021 09:23:03.822 INFO [main] > > > > org.apache.catalina.startup.VersionLoggerListener.log Server built: > > Mar 17 2021 12:00:00 UTC 23-Jul-2021 09:23:03.822 INFO [main] > > > > org.apache.catalina.startup.VersionLoggerListener.log Server version > > number: 9.0.36.0 23-Jul-2021 09:23:03.823 INFO [main] > > > > org.apache.catalina.startup.VersionLoggerListener.log OS Name: > > Linux 23-Jul-2021 09:23:03.823 INFO [main] > > > > org.apache.catalina.startup.VersionLoggerListener.log OS Version: > > 5.3.18-59.16-default 23-Jul-2021 09:23:03.823 INFO [main] > > > > org.apache.catalina.startup.VersionLoggerListener.log Architecture: > > amd64 23-Jul-2021 09:23:03.823 INFO [main] > > > > org.apache.catalina.startup.VersionLoggerListener.log Java Home: > > /usr/lib64/jvm/java-11-openjdk-11 23-Jul-2021 09:23:03.823 INFO [main] > > > > org.apache.catalina.startup.VersionLoggerListener.log JVM Version: > > 11.0.11+9-suse-3.56.1-x8664 23-Jul-2021 09:23:03.823 INFO [main] > > > > org.apache.catalina.startup.VersionLoggerListener.log JVM Vendor: > > Oracle Corporation 23-Jul-2021 09:23:03.823 INFO [main] > > > > org.apache.catalina.startup.VersionLoggerListener.log CATALINA_BASE: > > /usr/share/tomcat 23-Jul-2021 09:23:03.823 INFO [main] > > > > org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: > > /usr/share/tomcat 23-Jul-2021 09:23:03.826 INFO [main] > > > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: -ea 23-Jul-2021 09:23:03.826 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: -Xms256m 23-Jul-2021 09:23:03.826 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: -Xmx1G 23-Jul-2021 09:23:03.827 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: -Djava.awt.headless=true 23-Jul-2021 09:23:03.827 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: > > -Dorg.xml.sax.driver=com.redhat.rhn.frontend.xmlrpc.util.RhnSAXParser > > 23-Jul-2021 09:23:03.827 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: -Dorg.apache.tomcat.util.http.Parameters.MAX_COUNT=1024 > > 23-Jul-2021 09:23:03.827 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: -XX:MaxNewSize=256 23-Jul-2021 09:23:03.827 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: -XX:-UseConcMarkSweepGC 23-Jul-2021 09:23:03.827 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: -Dnet.sf.ehcache.skipUpdateCheck=true 23-Jul-2021 09:23:03.827 > > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command > > line argument: --add-modules=java.annotation,com.sun.xml.bind 23-Jul-2021 > > 09:23:03.827 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: > > --add-exports=java.annotation/javax.annotation.security=ALL-UNNAMED > > 23-Jul-2021 09:23:03.827 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: > > --add-opens=java.annotation/javax.annotation.security=ALL-UNNAMED > > 23-Jul-2021 09:23:03.827 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: -Dcatalina.base=/usr/share/tomcat 23-Jul-2021 09:23:03.828 INFO > > [main] org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: -Dcatalina.home=/usr/share/tomcat 23-Jul-2021 09:23:03.828 INFO > > [main] org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: -Djava.endorsed.dirs= 23-Jul-2021 09:23:03.828 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: -Djava.io.tmpdir=/var/cache/tomcat/temp 23-Jul-2021 09:23:03.828 > > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command > > line argument: > > -Djava.util.logging.config.file=/usr/share/tomcat/conf/logging.properties > > 23-Jul-2021 09:23:03.831 INFO [main] > > org.apache.catalina.startup.VersionLoggerListener.log Command line > > argument: > > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > > 23-Jul-2021 09:23:03.832 INFO [main] > > org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded Apache > > Tomcat Native library [1.2.23] using APR version [1.6.3]. 23-Jul-2021 > > 09:23:03.832 INFO [main] > > org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR > > capabilities: IPv6 [true], sendfile [true], accept filters [false], random > > [true]. 23-Jul-2021 09:23:03.832 INFO [main] > > org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL > > configuration: useAprConnector [false], useOpenSSL [true] 23-Jul-2021 > > 09:23:03.834 INFO [main] > > org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL > > successfully initialized [OpenSSL 1.1.1d 10 Sep 2019] 23-Jul-2021 > > 09:23:05.159 INFO [main] org.apache.coyote.AbstractProtocol.init > > Initializing ProtocolHandler ["ajp-nio-127.0.0.1-8009"] 23-Jul-2021 > > 09:23:05.280 INFO [main] org.apache.coyote.AbstractProtocol.init > > Initializing ProtocolHandler ["ajp-nio-0:0:0:0:0:0:0:1-8009"] 23-Jul-2021 > > 09:23:05.305 INFO [main] org.apache.coyote.AbstractProtocol.init > > Initializing ProtocolHandler ["http-nio-127.0.0.1-8080"] 23-Jul-2021 > > 09:23:05.313 INFO [main] org.apache.catalina.startup.Catalina.load Server > > initialization in [1,874] milliseconds 23-Jul-2021 09:23:05.631 INFO > > [main] > > org.apache.catalina.core.StandardService.startInternal Starting service > > [Catalina] 23-Jul-2021 09:23:05.631 INFO [main] > > org.apache.catalina.core.StandardEngine.startInternal Starting Servlet > > engine: [Apache Tomcat/9.0.36] 23-Jul-2021 09:23:05.680 INFO [main] > > org.apache.catalina.startup.HostConfig.deployDirectory Deploying web > > application directory [/srv/tomcat/webapps/rhn] 23-Jul-2021 09:23:07.488 > > SEVERE [main] org.apache.catalina.startup.HostConfig.deployDirectory Error > > deploying web application directory [/srv/tomcat/webapps/rhn] > > java.lang.IllegalStateException: Error starting child > > > > at > > > > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java > > : > > 720) at > > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:690) at > > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:705) at > > org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:113 > > 2 > > ) at > > org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java > > : > > 1865) at > > java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.ja > > v > > a:515) at > > java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at > > org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecuto > > r > > Service.java:75) at > > java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExec > > u > > torService.java:118) at > > org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:1 > > 0 > > 44) at > > org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:429) at > > org.apache.catalina.startup.HostConfig.start(HostConfig.java:1575) at > > org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:309) > > at > > org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.ja > > v > > a:123) at > > org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java > > : > > 423) at > > org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366) at > > org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:93 > > 6 > > ) at > > org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841) > > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at > > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java: > > 1 > > 384) at > > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java: > > 1 > > 374) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > > at > > org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecuto > > r > > Service.java:75) at > > java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExec > > u > > torService.java:140) at > > org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:90 > > 9 > > ) at > > org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java: > > 2 > > 62) at > > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) > > at > > org.apache.catalina.core.StandardService.startInternal(StandardService.jav > > a > > > > :421) at > > > > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) at > > org.apache.catalina.core.StandardServer.startInternal(StandardServer.java: > > 9 > > 30) at > > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) > > at org.apache.catalina.startup.Catalina.start(Catalina.java:633) at > > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > > Method) at > > java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMetho > > d > > AccessorImpl.java:62) at > > java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Delegat > > i > > ngMethodAccessorImpl.java:43) at > > java.base/java.lang.reflect.Method.invoke(Method.java:566) at > > org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:343) at > > org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:474) Caused by: > > org.apache.catalina.LifecycleException: Failed to start component > > [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/rhn]] > > at > > org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBa > > s > > e.java:440) at > > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198) at > > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java > > : > > 717) ... 37 more > > > > Caused by: java.lang.NullPointerException > > > > at > > > > org.apache.tomcat.util.scan.StandardJarScanner.process(StandardJarScanner. > > j > > ava:382) at > > org.apache.tomcat.util.scan.StandardJarScanner.scan(StandardJarScanner.jav > > a > > > > :195) at > > > > org.apache.catalina.startup.ContextConfig.processJarsForWebFragments(Conte > > x > > tConfig.java:1971) at > > org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:112 > > 9 > > ) at > > org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.jav > > a > > > > :775) > > : > > at > > > > org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.jav > > a > > > > :301) at > > > > org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.ja > > v > > a:123) at > > org.apache.catalina.core.StandardContext.startInternal(StandardContext.jav > > a > > > > :5044) at > > > > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) ... > > 38 > > more > > 23-Jul-2021 09:23:07.492 INFO [main] > > org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web > > application directory [/srv/tomcat/webapps/rhn] has finished in [1,813] ms > > 23-Jul-2021 09:23:07.524 INFO [main] > > org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler > > ["ajp-nio-127.0.0.1-8009"] 23-Jul-2021 09:23:07.752 INFO [main] > > org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler > > ["ajp-nio-0:0:0:0:0:0:0:1-8009"] 23-Jul-2021 09:23:07.880 INFO [main] > > org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler > > ["http-nio-127.0.0.1-8080"] 23-Jul-2021 09:23:07.913 INFO [main] > > org.apache.catalina.startup.Catalina.start Server startup in [2,600] > > milliseconds > > Can you provide the output of: > > `zypper dup`? > > I wonder if some of the Java dependencies didn't change to come from Leap. > > -- > Julio González Gil > Release Engineer, SUSE Manager and Uyuni > jgonzalez(a)suse.com -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

3 weeks, 4 days

1
0
0 0

how to upload custom rpms to uyuni

by Heiner Wulfhorst

Hi list, my customer needs following RPMs on his systems: - oracle-instantclient12.2-basic-12.2.0.1.0-1.x86_64.rpm - oracle-instantclient12.2-sqlplus-12.2.0.1.0-1.x86_64.rpm Is there any (maybe hidden) form in Web UI to upload RPMs into Uyuni? Or can i upload them with scp into any special path in uyuni server's filesystem to then assign them to a channel? In uyuni reference manual i found following information: "To create a new channel, click the Create Channel link. Select the appropriate options for the newchannel, including base architecture and GPG options, then click [Create Channel]. Note that a channel created in this manner is blank, containing no packages. You must either *upload software packages* or add packages from other repositories. You may also choose to include patches in your custom channel." This makes me believe there must be a way to upload any rpm into uyuni, but i (so far) couldn't find it. I created a new (empty) software channel but only find a form to select already existing packages into that channel. Thx, BR, Heiner

3 weeks, 5 days

4
3
0 0

Use Salt-Api externally from Uyuni

by Jesse Harris

Good day fellow uyuni users. I would like to leverage the salt-api that is used by uyuni. Currently the uyuni API does not have a method to list, accept or deny a salt-key. But the salt api does. I would like to do something like is mentioned here: https://stackoverflow.com/questions/19067341/using-salt-api-to-call-salt-ke… I have inspected the salt-api that is setup on uyuni and it is currently set up to only listen on the loopback interface which is easy to change. The next problem I have seems to be that the file based admin authentication does not match the admin account that I used to set up uyuni. I'm wondering if it is stored somewhere in the database for internal communication with the salt-api? Is there a safe way to get/set the password without disrupting internal comms with the api? Or is there a way to set up a second salt-api on the same box? I'm not a saltstack guru so I would love it if someone could point me in the right direction. Thanks -Jesse

1 month

2
1
0 0

Uyuni 2021.08 is released!

by Julio Gonzalez

We are happy to announce the immediate availability of Uyuni 2021.08 At https://www.uyuni-project.org/pages/stable-version.html you will find all the resources you need to start working with Uyuni 2021.08, including the release notes, documentation, requirements and setup instructions. VERY IMPORTANT: Read the release notes! If you are updating from an Uyuni version older than 2021.06, a major upgrade procedure is required. This is the list of highlights for this release: * Rocky Linux 8 as client * Ansible Playbooks test mode * Kiwi parameters for OS Image profiles * Fixes for AArch64 hosts, including virtualization * Virtual Machines and UEFI * Pacemaker support for KVM and Xen virtual machines * New CLM Filter Template * OpenSCAP Audit * Logs for Salt SSH clients * Tech-preview: Inter-Server Synchronization version 2 * Monitoring: prometheus and grafana updates Please check the release notes for full details. Remember that Uyuni will follow a rolling release planning, so the next version will contain bugfixes for this one and any new features. There will be no maintenance of 2021.08 As always, we hope you will enjoy Uyuni 2021.08 and we 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/pages/contact.html -- Julio González Gil Release Engineer, SUSE Manager and Uyuni jgonzalez(a)suse.com

1 month

3
2
0 0

Problems using Autoinstall Distro

by Heiner Wulfhorst

Hi List, i am trying to autoinstall SLES15 systems but my autoinstall distribution seems to have problems. After booting (PXE) i get a gray tui box on blue background saying " Please make sure your installation medium is available". The URL in "install" Kernel Parameter of the distro was generated automatically, i did not change it. When i try to accessit with browser i get an error message: Internal Server Error The server experienced a problem which prevented your request from being filled out. It may not be possible to execute this action at this time. Please help us correct this problem by contacting us with details of how you received this message. URLs of other Distros can be accessed w/o errors. I deleted and re-created the Distro, rebuilt the (staged/contentlifecycle) Repo, both without luck. Any hint is welcome! Thanks! Heiner PGP: C5160402C3F27014(a)keys.gnupg.net <http://keys.gnupg.net/pks/lookup?search=0xC5160402C3F27014&fingerprint=on&o…>

1 month, 1 week

2
3
0 0