Skip to content

Known Issues

There are some currently known issues in the Compute platform. This page describes the most common pitfalls. Known issues for Backup is under the Backup FAQ page.

Networking issue with the Debian 10 images

Unfortunately the network services installed on the publicly provided Debian 10 images are not working with OpenStack. One option is to install a Debain 9 image and then do an upgrade. Another option is to provide the following Cloud-Init script under "Configuration" when launching the instance. This will make the network services work as intended.

#cloud-config

output: {all: '| tee -a /var/log/cloud-init-output.log'}

password: [REDACTED]

chpasswd: { expire: False }

ssh_pwauth: True

manage_etc_hosts: false

package_upgrade: false

packages:

- curl

write_files:

- path: /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg

content: |

network: {config: disabled}

- path: /etc/network/interfaces.d/custom_eth0

content: |

auto lo

iface lo inet loopback

auto eth0

iface eth0 inet dhcp

mtu 1500

iface eth0 inet6 dhcp

accept_ra 2

runcmd:

- sed -i '1i\'"$(curl -s http://169.254.169.254/latest/meta-data/local-ipv4) $(hostname)" /etc/hosts

- rm -f /etc/network/interfaces.d/50-cloud-init

- systemctl restart networking

New certificate and hostname on Safespring Backup Service

Safespring backup service is changing hostname: tsm1.cloud.ipnett.se becomes tsm1.backup.sto2.safedc.net.

All customers running Safespring Backup needs to update hostnames and certificates for Safespring Backup services to start using the new hostnames. See this blogpost for details.

Resize operations disabled

Due to different issues with resize operations, we have disabled the resize operations users. If you need to resize instances, please contact support.

We expect to support user initiated resize operations after a future system upgrade.

DNS Resolver

The built in resolver in the platform has some issues in the current version. It has been reported to be slow and not to respond to queries in a timely manner. The best work around is to provide another resolver when creating the network to which you connect your instances. Use 89.32.32.32 which is SUNETs resolver. It is done in the third tab in the "Create Network" dialogue:

Create Network Tab 3

In the picture above we picked Googles resolver but any external resolver would work. Please note that this setting can only set when creating the network in the GUI. In order to update this setting on an existing network, the API must be used.

Instance operations

"Create Snapshot" only works for smaller instances at the moment. In addition, creating snapshots can in some cases create locking issues in the storage backend which will lead to a hard reboot of the instance. This has to do with some compatibility issues with OpenStack and the Ceph backend. With the coming upgrade of OpenStack, this is prioritized to get working for all kinds of instances.

In the drop-down menu in the instance listing there are some operations which are unsupported at the moment. It does not mean that they fail, but they could lead to data-loss and therefore not recommended for use. Problems with using "Suspend" and "Resize" while a volume was attached to the instance have been reported. To ensure that the attached volume persists after the operation it should be detached from the instance before the "Suspend" or "Resize" command is issued.

Create Network Tab 3

"Resize" works if you shutdown the instance first. It is prioritized function to get working properly even for running instances. "Shelve" shutdowns the instance and takes a snapshot of it. It works for smaller instances but takes very long time for larger instances and should be used with caution.

SNAT-networks in the network listing and Topology view

For every network you create which is connected to a router with an external gateway another network also will show up in the network listing and network topology view:

Network Listing

These network should be neglected, but never deleted as the NAT-functionality for floating IPs will stop working if they are deleted. This extra information (which only confuses the user) is planned to go away in newer releases of the platform.

Network operations in the GUI

Right now the operations to change admin state and to change name of a network does not work in the GUI. We recommend our users to use API Access to perform these operations.

Backup client incompatibility with local Windows NTFS deduplication enabled

Some users have reported performance issues when running the backup client on volumes with NTFS deduplication enabled since the deduplication in the backup client conflicts with the deduplication in the filesystem. The recommended solution is to turn off deduplication either on the filesystem or local deduplication in the backup client.

Too recent version of shade results in images not showing

We have had an instance where a newer (1.24.0) version of shade caused some images to become unavailable for provisioning when using ansible.

The solution was to downgrade shade to a known good (1.12.1) version.

Unstable ipv6 connectivity

If you experience flapping ipv6 connectivity it could be resolved either by setting a static default route and not depend on RA. Remove the accept_ra 1 if it exists in you network configuration file or any sysctl settings for accept_ra.

Set static default route.

This is an example, check your instance network address and change accordingly.

# ip -6 route add default via 2001:6b0:5a:4017::1

You may need to delete the RA route first if it exists.

# ip -6 route delete default

Alternative configure all ipv6 settings static.

Set static ipv6.

Find your ipv6 address from Horizon or by CLI and insert it as ipv6_address and set ipv6_gateway to the same subnet but ::1 at the end.

iface ens6 inet6 static
  address "ipv6_address"
  netmask 64
  gateway "ipv6_gateway"
  autoconf 0
  dns-nameservers 2001:4860:4860::8844 2001:4860:4860::8888
IPV6INIT=yes
IPV6ADDR="ipv6_address"/64
IPV6_DEFAULTGW="ipv6_gateway"
IPV6_AUTOCONF=no
DNS1=2001:4860:4860::8844
DNS2=2001:4860:4860::8888