Highlighted
Flight Engineer Flight Engineer
Flight Engineer
  • 1,116 Views

What to do after unrecoverable damage to registry VM in DO380?

Jump to solution

hello,


As chapter 4 is crusial for the rest of the course, I am stuck.
Is it possible to rerun the cluster-review or restore the services VM?

regards,

Jan Gerrit Kootstra

Labels (2)
2 Solutions

Accepted Solutions
Highlighted
Flight Engineer Flight Engineer
Flight Engineer
  • 1,100 Views

Re: DO380 registry is broken after ansible-playbook -i hosts-ucf \ post_install.yml

Jump to solution

You can reset all the VMs and have a proper working cluster by running 'lab build-cluster setup' on the workstation VM to have a working cluster again! Not a graceful solution, but will help you proceed from Chapter 5.

mj0vy

View solution in original post

Reply
Loading...
Highlighted
Flight Engineer Flight Engineer
Flight Engineer
  • 1,098 Views

Re: DO380 registry is broken after ansible-playbook -i hosts-ucf \ post_install.yml

Jump to solution

Hi Sreejith,

The error given by docker-registry-cli confused me.
I just gave the wrong domain-name for the registry server.

Thanks for the hint, might need it in the future.

Regards,

Jan Gerrit

View solution in original post

0 Kudos
Reply
Loading...
5 Replies
Highlighted
Flight Engineer Flight Engineer
Flight Engineer
  • 1,101 Views

Re: DO380 registry is broken after ansible-playbook -i hosts-ucf \ post_install.yml

Jump to solution

You can reset all the VMs and have a proper working cluster by running 'lab build-cluster setup' on the workstation VM to have a working cluster again! Not a graceful solution, but will help you proceed from Chapter 5.

mj0vy

View solution in original post

Reply
Loading...
Highlighted
Flight Engineer Flight Engineer
Flight Engineer
  • 1,099 Views

Re: DO380 registry is broken after ansible-playbook -i hosts-ucf \ post_install.yml

Jump to solution

Hi Sreejith,

The error given by docker-registry-cli confused me.
I just gave the wrong domain-name for the registry server.

Thanks for the hint, might need it in the future.

Regards,

Jan Gerrit

View solution in original post

0 Kudos
Reply
Loading...
Highlighted
Moderator
Moderator
  • 1,048 Views

Re: What to do after unrecoverable damage to registry VM in DO380?

Jump to solution

Hey, gentlemen. I took the liberty of changing the title (as it was misleading) to something more representative of the real issue discussed. Glad you solved the issue, @JG_Kootstra.

A black cat crossing the street signifies that the animal is going somewhere.
[don't forget to kudo a helpful post or mark it as a solution!]
Reply
Loading...
Highlighted
Flight Engineer Flight Engineer
Flight Engineer
  • 1,045 Views

Re: What to do after unrecoverable damage to registry VM in DO380?

Jump to solution

A better title would be: docker gives confusing error when you refer to a wrong registry. It gives a "trace dump" instead of registry cannot be reached.

0 Kudos
Reply
Loading...
Highlighted
Moderator
Moderator
  • 857 Views

Re: What to do after unrecoverable damage to registry VM in DO380?

Jump to solution

Actually, most of the thread does deal with reanimation of a defunct services VM, so the title is quite correct.

The section, however, wasn't, so I further moved the post to "Containers, DevOps & OpenShift".

A black cat crossing the street signifies that the animal is going somewhere.
[don't forget to kudo a helpful post or mark it as a solution!]
0 Kudos
Reply
Loading...
Join the discussion
You must log in to join this conversation.