The document describes how to resolve issues you may encounter while using NHN Cloud.
You can only use the OS version provided by NHN Cloud. And uploading personal images is not allowed.
To use personal OS images, create an instance with NHN Cloud image and apply Create Image.
It happens when the personal key (PEM key) applied to access instance has invalid authority. Adjust the authority of personal key file like below.
$ chmod 600 your-key.pem
To get root authority from CentOS instance, use the 'sudo' command like follows.
$ sudo su
You shall encounter with such error, when an image is created with instance using two or more block storages and instance is created and booted with such image.
For instances that use more than two block storages, set disks other than default disk in the /etc/fstab
file. Since the file is to be replicated as well, when image is created, error occurs in mounting due to lack of a block storage referenced by the/etc/fstab
file.
To resolve this issue, set block storage of the /etc/fstab
file, except default disk, as footnote, before creating an image.
It happens when DNS is blocked at the receiving part of the security group to which instance belongs. Adjust the security group to be allowed to receive DNS.
It happens when DNS is blocked at the receiving part of the security group to which instance belongs. Adjust the security group to be allowed to receive DNS.
NHN Cloud's Monitoring services (System Monitoring, Service Monitoring, Cloud Monitoring) may not work properly on instances that use proxies. Also, in the case of Windows operating systems, problems such as password reset may occur.
To avoid this issue, you must disable proxying for the 169.254.0.0/16
band on instances that use proxies. Typically, you would set this value in an environment variable called no_proxy
, but some proxies ignore this environment variable, so refer to the proxy guide to set this up.
Use the yum repository
file after modifying the file as follows.
Additional updates are not supported for OS for which official support has ended, so it is recommended that you use a higher version of the OS.
$ sudo vi /etc/yum.repos.d/CentOS-Base.repo
[base]
...
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os&infra=$infra&cc=$cc
#baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
baseurl=https://vault.centos.org/6.10/os/$basearch/
...
[updates]
...
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates&infra=$infra&cc=$cc
#baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/
baseurl=https://vault.centos.org/6.10/updates/$basearch/
...
[extras]
...
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras&infra=$infra&cc=$cc
#baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/
baseurl=https://vault.centos.org/6.10/extras/$basearch/
...
$ sudo vi /etc/yum.repos.d/CentOS-Base.repo
[base]
...
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os&infra=$infra&cc=$cc
#baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
baseurl=https://vault.centos.org/7.9.2009/os/$basearch/
...
[updates]
...
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates&infra=$infra&cc=$cc
#baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/
baseurl=https://vault.centos.org/7.9.2009/updates/$basearch/
...
[extras]
...
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras&infra=$infra&cc=$cc
#baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/
baseurl=https://vault.centos.org/7.9.2009/extras/$basearch/
...
[centosplus]
...
#mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus&infra=$infra&cc=$cc
#baseurl=http://mirror.centos.org/centos/$releasever/centosplus/$basearch/
baseurl=https://vault.centos.org/7.9.2009/centosplus/$basearch/
...
$ sudo yum clean all
$ sudo yum repolist