[OSGeo] #3314: general and gdal matrix rooms disconnected from slack

Committees SAC tickets
, ,
1

#3314: general and gdal matrix rooms disconnected from slack
----------------------+--------------------------------------
Reporter: robe | Owner: sac-tickets@…
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2024-I
Component: SysAdmin | Keywords:
----------------------+--------------------------------------
We upgraded osgeo:general and osgeo:matrix rooms to version 10 on matrix.

Immediately after slack General and slack gdal were disconnected from
matrix.

It seemed initially all was good, but after the first message to general
after the upgrade second message and subsequent messages became
disconnected from slack. In some sort of split brain it seems.

I'm not sure if it's the version 10 (maybe slack can't handle that, as the
other rooms mirrored on slack that still work - postgis, geos) are version
9.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3314&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

2

#3314: general and gdal matrix rooms disconnected from slack
----------------------+---------------------------------------
Reporter: robe | Owner: sac-tickets@…
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2024-I
Component: SysAdmin | Resolution:
Keywords: |
----------------------+---------------------------------------
Comment (by robe):

Looks like foss4g is also disconnected or perhaps it was never connected
to the matrix foss4g
--
Ticket URL: <#3314 (general and gdal matrix rooms disconnected from slack) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

3

#3314: general and gdal matrix rooms disconnected from slack
----------------------+---------------------------------------
Reporter: robe | Owner: sac-tickets@…
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2024-I
Component: SysAdmin | Resolution:
Keywords: |
----------------------+---------------------------------------
Description changed by robe:

Old description:

We upgraded osgeo:general and osgeo:matrix rooms to version 10 on matrix.

Immediately after slack General and slack gdal were disconnected from
matrix.

It seemed initially all was good, but after the first message to general
after the upgrade second message and subsequent messages became
disconnected from slack. In some sort of split brain it seems.

I'm not sure if it's the version 10 (maybe slack can't handle that, as
the other rooms mirrored on slack that still work - postgis, geos) are
version 9.

New description:

We upgraded osgeo:general and osgeo:matrix rooms to version 11 on matrix.

Immediately after slack General and slack gdal were disconnected from
matrix.

It seemed initially all was good, but after the first message to general
after the upgrade second message and subsequent messages became
disconnected from slack. In some sort of split brain it seems.

I'm not sure if it's the version 10 (maybe slack can't handle that, as the
other rooms mirrored on slack that still work - postgis, geos) are version
9.

--
--
Ticket URL: <#3314 (general and gdal matrix rooms disconnected from slack) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

4

#3314: general and gdal matrix rooms disconnected from slack
----------------------+---------------------------------------
Reporter: robe | Owner: sac-tickets@…
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2024-I
Component: SysAdmin | Resolution:
Keywords: |
----------------------+---------------------------------------
Comment (by robe):

I was looking for solutions and I found strk's who said he ran into it
when upgrading to version 9

https://github.com/matrix-org/matrix-appservice-
slack/issues/627#issuecomment-1006039454

----
I finally found the actual fix (after upgrade, that is):

     Go to the start history of the new room, follow the link to the OLD
room
     Unlink the bridge from the OLD room
     Add the bridge to the NEW room

----

strk but I don't understand how to do your solution, I hope you do.
--
Ticket URL: <#3314 (general and gdal matrix rooms disconnected from slack) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

5

#3314: general and gdal matrix rooms disconnected from slack
----------------------+------------------------------------------------
Reporter: robe | Owner: sac-tickets@…
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2024-III (strk)
Component: SysAdmin | Resolution:
Keywords: |
----------------------+------------------------------------------------
Changes (by robe):

* milestone: Sysadmin Contract 2024-I => Sysadmin Contract 2024-III (strk)

--
Ticket URL: <#3314 (general and gdal matrix rooms disconnected from slack) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

6

#3314: general and gdal matrix rooms disconnected from slack
--------------------------+------------------------------------------------
Reporter: robe | Owner: sac-tickets@…
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2024-III (strk)
Component: | Resolution:
  SysAdmin/Matrix |
Keywords: |
--------------------------+------------------------------------------------
Changes (by robe):

* component: SysAdmin => SysAdmin/Matrix

--
Ticket URL: <#3314 (general and gdal matrix rooms disconnected from slack) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

7

#3314: general and gdal matrix rooms disconnected from slack
-----------------------------+---------------------------------------
Reporter: robe | Owner: sac-tickets@…
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2024-I
Component: SysAdmin/Matrix | Resolution:
Keywords: |
-----------------------------+---------------------------------------
Changes (by robe):

* milestone: Sysadmin Contract 2024-III (strk) => Sysadmin Contract 2024-I

--
Ticket URL: <#3314 (general and gdal matrix rooms disconnected from slack) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

8

#3314: general and gdal matrix rooms disconnected from slack
-----------------------------+---------------------------------------
Reporter: robe | Owner: sac-tickets@…
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2024-I
Component: SysAdmin/Matrix | Resolution:
Keywords: |
-----------------------------+---------------------------------------
Comment (by robe):

nevermind I think I fumbled my way thru it so general is now working
again. Now for gdal.

foss4g was never integrated. I tried to integrat to slack, but I have no
admin rights to the osgeo:foss4g matrix channel so can't make the other
connection.
--
Ticket URL: <#3314 (general and gdal matrix rooms disconnected from slack) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

9

#3314: general and gdal matrix rooms disconnected from slack
-----------------------------+---------------------------------------
Reporter: robe | Owner: sac-tickets@…
     Type: task | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2024-I
Component: SysAdmin/Matrix | Resolution: fixed
Keywords: |
-----------------------------+---------------------------------------
Changes (by robe):

* resolution: => fixed
* status: new => closed

Comment:

Okay got gdal working.

To do - basically following strk's guidance

1. Had to install Integration widget in my element, so I see the linkages.
2. Annoyingly when I went to the old room, I saw no Slack Bridge
installed, so I added it, then got the option to unlink. So unlinked

3. Then went to new room added the Slack Bridge, then linked to the
relevant slack gdal / General (repeated for each room)
--
Ticket URL: <#3314 (general and gdal matrix rooms disconnected from slack) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.