Hi,

On Wed, 9 Dec 2020 at 16:24, Ruslanas Gžibovskis <ruslanas@lpic.lt> wrote:
Hi Oliver,

Can you please confirm then the following:

Remove NovaAZ from roles file.

That is not necessary. The tripleo service is included in the compute roles by default but it's also disabled by default.
 
Remove novaAZ from environment files, and it should be able to update without this step?

Yes, remove the nova-az-config.yaml environment file from the deploy command line. I think that should just revert back to default (service disabled). If not then you can explicitly disable it with:
resource_registry:
  OS::TripleO::Services::NovaAZConfig: OS::Heat::None

Cheers,
Ollie
 

Maybe i will need to ensure they are in same cell and so on, and assign zone manually. 

Is it correct?

On Wed, 9 Dec 2020, 18:07 Oliver Walsh, <owalsh@redhat.com> wrote:
Ok, that will not work. If you want to manually configure the AZs after deployment then just stop using [1].

Cheers,
Ollie

On Tue, 8 Dec 2020 at 06:59, Ruslanas Gžibovskis <ruslanas@lpic.lt> wrote:
The first deployment set all computes to zone named according to stack name, but later I have created Alpha01, Alpha02. And set according in node-info.yaml file. But still, it fails with message, that some compute is already present in zone Alpha01... like it cannot create such zone. And I say, yes captain, I know, I have created and added YOU into that zone... Maybe I need to do some "tweaks" to DB? just now thought about it. 

On Mon, 7 Dec 2020 at 20:02, Oliver Walsh <owalsh@redhat.com> wrote:
Hi,

You will need to manually remove the hosts from the old zone ("Alpha01") before adding them to the new zone. A host can only belong to one AZ.

Thanks,
Ollie

On Mon, 7 Dec 2020 at 11:32, Ruslanas Gžibovskis <ruslanas@lpic.lt> wrote:
anyone know, how to bypass aggregation group error? thank you.

On Sat, 5 Dec 2020 at 18:08, Ruslanas Gžibovskis <ruslanas@lpic.lt> wrote:
Hi all,

Any thoughts on this one?
 
Hi all.

After changing the host aggregate group and zone, I cannot run OpenStack deploy command successfully again, even after updating deployment environment files according to my setup.

I receive error bigger one in [0]:
2020-12-02 10:16:18.532419 | 52540000-0001-cf95-492f-0000000003ca |      FATAL | Nova: Manage aggregate and availability zone and add hosts to the zone | undercloud | error={"changed": false, "msg": "ConflictException: 409: Client Error for url: http://10.120.129.199:8774/v2.1/os-aggregates/1/action, Cannot add host to aggregate 1. Reason: One or more hosts already in availability zone(s) ['Alpha01']."}

I was following this link [1] instructions for "Configuring Availability Zones (AZ)" steps to modify with OpenStack commands. And zone was created successfully, but when I needed to add additional nodes, executed deployment again with increased numbers it was complaining about an incorrect aggregate zone, and now it is complaining about not empty zone with error [0] mentioned above. I have added aggregate zones into deployment files even role file... any ideas?

Also, I think, this should be mentioned, that added it after install, you lose the possibility to update using tripleo tool and you will need to modify environment files with.



[0] http://paste.openstack.org/show/800622/
[1] https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/features/distributed_compute_node.html#configuring-availability-zones-az





--
Ruslanas Gžibovskis
+370 6030 7030
_______________________________________________
users mailing list
users@lists.rdoproject.org
http://lists.rdoproject.org/mailman/listinfo/users

To unsubscribe: users-unsubscribe@lists.rdoproject.org


--
Ruslanas Gžibovskis
+370 6030 7030