Currently, the Ansible role won't automatically create a dedicated /var/cache/rhn partition. This might led into storage problems as at least 20 GB are required.

As older releases are currently mirrored until further notice, it would be an option to add version pinning for installation. Details here: https://build.opensuse.org/project/subprojects/systemsmanagement:Uyuni:Snapshots

As Uyuni 2022.06 and SUMA 4.3 were released, it would be great to have to possibility to install them. Both need 15 SP4 as Base OS.

SUSE Manager can also be installed on IBM Z, it would be great to have support for it. Currently, required SCC modules are hardcoded to x86_64.

It might be sufficient to replace x86_64 in defaults/main.yml with {{ ansible_architecture }} to also allow ppc64le and s390x..

Hello Christian,

when installing Suse Manager on SP4, it is not possible to activate the module python2

- name: sle-module-python2
   identifier: "sle-module-python2/{{ ansible_distribution_version }}/{{ ansible_architecture }}"

I have changed it to python3 and it was working.
So, maybe you need to check which SP is installed to put the right python module.

Best regards,
steffen

Since opensuse 15.4 the perl TimeDate module is not installed anymore and also is not available on the default repositories.
To install the missing package we have to add the dedicated perl repo first, then we can install it:

# zypper addrepo https://download.opensuse.org/repositories/devel:languages:perl/15.4/devel:languages:perl.repo
# zypper refresh
# zypper in perl-TimeDate

After that the import will run again

It would be nice to have an option to pre-enable monitoring by installing the following packages:

# zypper in golang-github-prometheus-node_exporter golang-github-wrouesnel-postgres_exporter prometheus-jmx_exporter golang-github-lusitaniae-apache_exporter prometheus-jmx_exporter-tomcat

Maybe there is also a way for enabling monitoring in the WebUI...

Hello,

Unfortunately, website http://oserrata.atix.de/debian/xml_export/latest is no longer available.
This makes the erratas for debian not work.

Are you aware of an alternative source?

Currently the pre-requisite check fails:

TASK [stdevel.uyuni : Ensure having 15 SP1 release] ****************************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Please upgrade to SP1"}

NOTE: SUSE Manager 4.0.x (based on SLES 15 SP1) is still supported until June 2021.

It would be great to have the possibility to create firewall rules needed for Uyuni:

create a variable to change the default fs size of 10GB for production systems.
this has been noticed during an installation.
Is this a good idea?

Currently, only the syntax is checked - it would be great to spin-up an opensuse/leap container and run the full molecule test phase. This could be done with GitHub actions.

After implementing content staging (see also issue #3) it would be handy to have the possibility to enable CentOS and Debian errata import. There are two Perl utilities for this.

This requires the following steps:

• Install requirements (perl, perl-Text-Unidecode)
• Download and place errata import scripts
• Create cronjob for downloading/updating errata information

It would be handy to create bootstrap repositories after creating channels (see also issue #3).

It would be handy to automate mirroring SUSE products. This includes adding mirror credentials first.

It might be possible to test z series support without having expensive hardware by leveraging hercules: http://linuxvm.org/Info/HOWTOs/hercules.html

It would be easier to have the role named "uyuni" instead of "ansible-uyuni".

As Uyuni is the upstream project for SUSE Manager, it would be nice to also have it supported. The package/pattern names are exactly the same.

Needed changes:

• task to enter registration code
• ensure having appropriate repository enabled

In accordance with the official documentation it would be good to implement the following "hack" to replace the base product with SUSE Manager:

# rpm -e --nodeps sles-release
# vi /etc/zypp/zypp.conf
...
solver.onlyRequires = false

ESC ZZ
# SUSEConnect -p SUSE-Manager-Server/4.0/x86_64 -r <code> -e <mail>
# SUSEConnect -p sle-module-basesystem/15.1/x86_64
# SUSEConnect -p sle-module-python2/15.1/x86_64
# SUSEConnect -p sle-module-server-applications/15.1/x86_64
# SUSEConnect -p sle-module-web-scripting/15.1/x86_64
# SUSEConnect -p sle-module-suse-manager-server/<productnumber>/x86_64
# ln -s /etc/products.d/SUSE-Manager-Server.prod /etc/products.d/baseproduct
# zypper in yast2-storage-ng

It would be good to tag the particular tasks for easier debugging and skipping.

The Python package jmespath is required - otherwise the playbook will fail:

ASK [stdevel.uyuni : Register system] *****************************************************************************************
fatal: [localhost]: FAILED! => {"msg": "The conditional check 'scc_registration.stdout | from_json | json_query(query_filter) | join | lower != \"registered\"' failed. The error was: You need to install \"jmespath\" prior to running json_query filter\n\nThe error appears to be in '/home/sles/.ansible/roles/stdevel.uyuni/tasks/prepare_sles.yml': line 9, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Register system\n  ^ here\n"}

Currently, the LVM code looks really duplicated (dedicated tasks per LV, filesystem and mount). It would great having a loop for this stuff.

A couple of releases ago, a patch repo was introduced: https://www.uyuni-project.org/pages/patches.html

It might be an option for adding it during installation.

It would be great to have Molecule unit tests

Hi

I have tried installing the SUSE Manager 4.0 using the Ansible.
Encountered error during the installation and found the modules needs to be updated with the following order.
requesting you to kindly update the code base with the changes.

sles_modules:

  - name: sle-module-basesystem
    identifier: sle-module-basesystem/15.1/x86_64
  - name: sle-module-web-scripting
    identifier: sle-module-web-scripting/15.1/x86_64
  - name: sle-module-python2
    identifier: sle-module-python2/15.1/x86_64
  - name: sle-module-suse-manager-server
    identifier: sle-module-suse-manager-server/4.0/x86_64
  - name: sle-module-server-applications
    identifier: sle-module-server-applications/15.1/x86_64
  - name: sle-module-desktop-applications
    identifier: sle-module-desktop-applications/15.1/x86_64
  - name: sle-module-development-tools
    identifier: sle-module-development-tools/15.1/x86_64

Hi Christian

It would be nice to have a parameter uyuni_scc_url in order to specify URL to use for registration; could be useful e.g. in cloud environments to specify --url=scc.suse.com

Thanks, Dietmar

It would be great to have custom SSL certificates installed before installation: https://documentation.suse.com/external-tree/en-us/suma/4.0/suse-manager/administration/ssl-certs-imported.html#_imported_certificates_for_new_installations

Some systems don't require a second disk for application data (e.g. temporary Vagrant boxes), so it would be handy having the possibility to skip LVM tasks.

It would be handy to have the possibility to implement a proxy installation

As Spacewalk is dead like a dodo we could rename the variables.

It would be great to also have the possibility to create software channels via spacewalk-common-channels (from the spacewalk-utils package).

Tasks:

• install requirements
• create channels