Terraform Error: Failed to query available provider packages

Terraform error when executing terraform init command

 Terraform Error: Failed to query available provider packages

Could not retrieve the list of available versions for provider hashicorp/oci: no available releases match the given constraints >= 4.41.0, ~> 4.59.0

Background:

I got a working terraform project from a friend, when I tried to run in my environment, I am getting this error.

My development environment is oracle developer instance, which is already packed with terraform.

After copying the terraform project, I am trying to do a terraform init

[root@shivin-dev-sg terraform]# terraform init

Initializing modules...

Downloading registry.terraform.io/oracle-terraform-modules/vcn/oci 3.2.0 for vcn...

- vcn in .terraform/modules/vcn

- vcn.drg_from_vcn_module in .terraform/modules/vcn/modules/drg

Initializing the backend...

Initializing provider plugins...

- Finding hashicorp/kubernetes versions matching "~> 2.4.1"...

- Finding latest version of hashicorp/local...

- Finding hashicorp/oci versions matching ">= 4.41.0, ~> 4.59.0"...

- Installing hashicorp/kubernetes v2.4.1...

- Installed hashicorp/kubernetes v2.4.1 (signed by HashiCorp)

- Installing hashicorp/local v2.1.0...

- Installed hashicorp/local v2.1.0 (signed by HashiCorp)

╷

│ Error: Failed to query available provider packages

│ 

│ Could not retrieve the list of available versions for provider hashicorp/oci: no available releases match the given constraints >= 4.41.0, ~> 4.59.0

╵

[root@shivin-dev-sg terraform]#

What is the issue and how to fix it?

As you can see from the initalizing provider plugins part, the oci plugin version is 4.41.0 but in our provider.tf the version is 4.59.0. This means somewhere in my machine there is a plugin cache. I need to find delete it for fixing this issue.

Steps to solve the issue:

cd /usr/share/terraform/

rm -rf plugins

cd /root

rm -rf .terraform

cd /path-to-your-terraform

rm -rf .terraform.d

Now, do a terraform init, it will works!!

How to backup and restore Oracle Integration Cloud (OIC)

How to backup and restore Oracle Integration Cloud (OIC)

 Current Environment : 

• Oracle Integration Instance
• Standard Edition
• 5K messages per hour

How to backup OIC Integration.

1. Login to your OCI cloud account.
2. Select "Developer Service" --> "Application Integration" --> "Integration"

    3.    Select your existing OIC instance and click on "Service Console"

    4.    Select "Integrations"

    5.    You could able to see your Integrations endpoints and its configurations.

    6.  Here, in this example, I am taking the backup of "demo" endpoint.

    7.  Mouse over to the "demo" endpoint right side and choose "Actions" --> "Export". 

         It will download the backup in your machine as "DEMO_01.00.00000.iar" file.

How to backup OIC Integration.

1. Login to your OCI cloud account.
2. Select "Developer Service" --> "Application Integration" --> "Integration"
3. Create your new OIC instance.
4. Select "Integrations"

    

        5. Click on "Import" and upload your previous backup file "DEMO_01.00.00000.iar"

        6. This will restore OIC integration from our older instance to the new instance.

These steps will help to backup and restore Oracle Integration Cloud (OIC).

unable to create file filename too long git clone

 When I do a git clone I am getting the following error - unable to create file filename too long git clone

Solution : 

git clone -c core.longpaths=true <repo url>

How to connect Oracle Storage account in arcserver

 How to connect Oracle Storage account in arcserver?

When I tried to connect OCI Object storage with arcserver, I am getting an error saying failed to connect.

I tried the same credentials with Cloudberry and I encounter an error. But in cloudberry the error shows the reason. Fix for the error is http://www.linuxblackmagic.com/2021/10/authorization-mechanism-you-have.html

After fixing the error, I came to know that the issue is related to "Signature Version". For changing the signature version, there is no option in web. We need to go to "C:\Program Files\Arcserve\Unified Data Protection\Management\BIN\CCI\Config"

then open the file "AmazonPlugin", change the line from true to false

# original

#Set S3SignerType Override to true

SIGNER_OVERRIDE=true

#after change

#Set S3SignerType Override to true

SIGNER_OVERRIDE=false

Then restart the arcserver.

Try to connect, your OCI object storage account will connect now.

Authorization mechanism you have provided is not supported. please use aws4-hmac-sha256

 When you work with AWS SDK or AWS S3 compatible storage, during the time of connection settings you may encounter this error 

authorization mechanism you have provided is not supported. please use aws4-hmac-sha256

I got this error when I tried to add a storage in Cloudberry tool. The destination is Oracle Object storage.

How to solve this error?

This is because of the signature version used is old. You need to Click on the "Advanced Settings", then on drop down of Signature version, choose 4.

Disaster Recovery Planning and Business Continuity Planning | Webinar | ...

Skynetclouds is a managed multi cloud service provider having experienced cloud professionals from AWS, Azure, Google Cloud and Oracle Cloud. 

As per ISO 27001, Information Security Management Systems – Disaster Recovery and BCP are one of the main topics. In this digital era, we should be well equipped to face any disaster and as business owners, we should focus more on the mitigation plans. As you know we can’t control the occurrence of this disaster, but we can plan and implement a good recovery plan.

Different types of disasters are:

Operational failures

• Power failures
• IT hardware failures
• N/W failures
• Software failures

Natural Disasters

• Flood
• Storm
• Earthquakes

Human-caused Events

• Human error
• Malicious insider
• Unknowing errors

RTO = Recovery Time Objective (How quickly can my application be running again?)

RPO = Recovery Point Objective (How many transactions can I stand to lose?)

Why Skynetclouds?

• Managed Cloud Service Provider
• Cloud Architects who are certified in Azure, AWS, GCP & Oracle
• 24/7 * 365 Availability
• DevOps as Service
• Focused on Security, Cost Deduction and Automation

authentication plugin caching_sha2_password is not supported

 Getting the below error message when you connect to mysql8

authentication plugin caching_sha2_password is not supported

In MySQL 8.0, caching_sha2_password is the default authentication plugin rather than mysql_native_password.

Login to Mysql as root

Check whether the mysql user plugin is mysql_native_password or caching_sha2_password

select Host,User,plugin from mysql.user;

If its caching_sha2_password, change to mysql_native_password

ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY '{Password}';

RESTART MYSQL SERVICE.

Try now!