3.13. Provisioning Issues

This section describes known issues with the Provisioning component of Satellite 6.1.
BZ 1203670: Provisioning of virtual machine on RHEV-M through Satellite 6 fails with "User is not authorized to perform this action."
Issue

If you create a user on RHEV-M and assign the required roles and permissions for provisioning, when you try to deploy a new Content Host the operation fails with an error similar to the following: 

Rolling back due to a problem: [Set up compute instance sat6-content-host.example.com         2       failed
.
.
Failed to save: Failed to create a compute lab-rhevm.example.com (RHEV) instance sat6-content-host.example.com: User is not authorized to perform this action.
In the /var/log/ovirt-engine/engine.log file on RHEV-M the following messages might appear: 
Event ID: -1, Message: User example-user logged in.
2015-03-09 18:24:09,961 WARN  [org.ovirt.engine.core.bll.RemoveVmCommand] (ajp-/127.0.0.1:8702-20) [197b036d] CanDoAction of action RemoveVm failed. Reasons:VAR__ACTION__REMOVE,VAR__TYPE__VM,USER_NOT_AUTHORIZED_TO_PERFORM_ACTION
Workaround

Log in to the "User Portal" with the same user and same permissions to create a new virtual machine.

BZ 1170261: RHEL 7 missing from list of available OSes when using VMware ESXi as Compute Node, even when RHEL 7 profiles exist
Issue

If you use VMware as a compute resource and have Red Hat Enterprise Linux 7 available as a profile, it does not appear as an available OS when creating a new host in Satellite 6.1.

This is caused by the version of the rbvmomi gem shipped with Satellite 6.1 (1.6). This issue disappears if version 1.8 or later of this gem is installed. You can determine the currently-installed version of this gem as follows: 
# ll /opt/rh/ruby193/root/usr/share/gems/gems/rbvmomi-1.6.0/
Workaround

To address this issue, you need to manually update the vmodl.db file and restart the appropriate services, as follows:

Procedure 3.3. To Update the vmodl.db File:

  1. Change to the appropriate directory and back up the existing file: 
    # cd /opt/rh/ruby193/root/usr/share/gems/gems/rbvmomi-1.6.0/

# ll
total 1172
drwxr-xr-x. 2 root root    4096 Apr  2 15:06 bin
drwxr-xr-x. 3 root root    4096 Apr  2 15:06 lib
-rw-r--r--. 1 root root    1078 Jan 30  2014 LICENSE
-rw-r--r--. 1 root root 1187562 Jan 30  2014 vmodl.db

# mv vmodl.db vmodl.db.1.60
  2. Download the latest version of the vmodl.db file: 
    # wget https://github.com/vmware/rbvmomi/blob/master/vmodl.db?raw=true -O vmodl.db
  3. Restart the foreman and httpd services: 
    # service foreman restart
# service httpd restart

    Note

    After you restart the httpd service you might see the following warning:
    [warn] module passenger_module is already loaded, skipping
    This can be safely ignored.
BZ 1197139: Newly created hosts in VMware can receive an empty network label/VLAN
Issue

If you clone a host in a Vmware ESX cluster from a template, the newly created host receives an empty network label/VLAN on the network interface. The attached network interface is not active and is assigned the "Standard port group" type, while previously deployed machines have been assigned the "Distributed port group" interface type. As a result the VM does not receive a DHCP IP address and cannot complete deployment.

This issue has so far only been observed in a VMware network infrastructure based on distributed switches, and can be reproduced as follows:
  1. In the VMware UI, define a VMware network infrastructure based on distributed switches.
  2. In VMware UI, create a template based on an image with attached distributed virtual switches and ports.
  3. In Satellite 6, define a VMware compute resource and some compute profiles.
  4. Create compute profiles using the previously defined VMware template.
  5. In the Satellite 6 web UI, navigate to Hosts → New Host, and enter all required parameters.
  6. Select Deploy on VMware.
  7. Select Compute Profile.
  8. On the Virtual Machine tab, in the Network field, select any of the defined VLANs/Network Labels (must be queried automatically).
  9. Click Submit.
Workaround

The best workaround currently available is that for the described network infrastructure, use network-based, instead of image-based, provisioning.

BZ 1219577: Cannot create unmanaged hosts from the web UI
Issue

The web UI currently provides no direct process for creating an unmanaged host.

Workaround

To create an unmanaged host in the web UI, you first need to select a managed host and then edit it to make it unmanaged. You can also use the API to create an unmanaged host without first creating a managed host.

BZ 1194288: Accessing a provisioned host's console using an encrypted connection
Issue

Unlike Satellite 6.0, Satellite 6.1 uses encrypted connections by default to connect to the console of provisioned hosts. Before you can use encrypted connections, you need to import the Satellite server's CA certificate into your browser.

Workaround

Import the Satellite server's CA certificate into your browser.

Procedure 3.4. To Import the CA certificate:

  1. Download the CA certificate from https://satellite6-server/pub/katello-server-ca.crt
  2. In Firefox, navigate to Edit → Preferences → Advanced.
  3. On the Certificates tab, click View Certificates.
  4. On the Servers tab, click Import, select the certificate that you downloaded, and then click Open.

Note

Modify this procedure to suit whichever browser you are using.
BZ 1223962: VMware Compute Resource issue
Issue

Provisioning fails with VMware Compute Resource if the vCenter's data center uses nested folders.

Workaround

Until this issue is resolved, Red Hat recommends that you create VMware virtual machines outside of Satellite 6 and associate them using subscription-manager and puppet-agent explicitly.

See also: