SUSE update repositories disappeared

[chris...@unilogcorp.com]

After installing a new sles 11 server on GCE today, I attempted to patch to the latest.

But I get a response that the repository is unavailable.

If I ping, there is no response.

I erase the config and rerun it and it puts the same server back in.

smt-gce.susecloud.net at 108.59.80.221.

I checked a few other existing servers and they also fail now and did not last week (or so).

Any ideas?

Chris.

[Jimmy Kaplowitz]

Hi Chris,

I'm bringing your email to SUSE's attention so they can follow up. Thanks for reaching out.

- Jimmy

> --
> © 2014 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
>  
> Email preferences: You received this email because you signed up for the Google Compute Engine Discussion Google Group (gce-dis...@googlegroups.com) to participate in discussions with other members of the Google Compute Engine community and the Google Compute Engine Team.
> ---
> You received this message because you are subscribed to the Google Groups "gce-discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to gce-discussio...@googlegroups.com.
> To post to this group, send email to gce-dis...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/gce-discussion/b0659551-0a0a-4852-b582-a3a2a775459e%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Robert Schweikert]

On Thursday, December 11, 2014 2:42:44 PM UTC-5, chris...@unilogcorp.com wrote:

After installing a new sles 11 server on GCE today, I attempted to patch to the latest.

But I get a response that the repository is unavailable.

If I ping, there is no response.

I erase the config and rerun it and it puts the same server back in.

What are you re-running?
 

smt-gce.susecloud.net at 108.59.80.221.

This is the IP for one of the SMT servers. There server appears in good working order.
 

I checked a few other existing servers and they also fail now and did not last week (or so).

Can you share the IP addresses of the failing servers?

I just started a new VM and things worked as expected.


Later,
Robert

[Christopher Bracy]

suse_register -E

/etc/init.d/guestregister start

This was a msitake because it cleared out the repositories.  I can rebuild that list by hand once the repository server is back.

smt-gce.susecloud.net at 108.59.80.221 is not reachable from any of my servers.

Other servers i patched last week with this as the repository worked and now can not accesss it either.

I can make a new VM, just not patch it or add packages.  I am building 12 more today.

Chris Bracy
Manager of Infrastructure and Hosting
Unilog Content Solutions LLC
Suite 510
985 Old Eagle School Rd
Wayne, PA 19087
direct: 484-254-6632
skype: cabracy

---

From: gce-dis...@googlegroups.com <gce-dis...@googlegroups.com> on behalf of Robert Schweikert <rjsc...@suse.com>
Sent: Thursday, December 11, 2014 4:01 PM
To: gce-dis...@googlegroups.com
Subject: [gce-discussion] Re: SUSE update repositories disappeared

 

--
© 2014 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
 
Email preferences: You received this email because you signed up for the Google Compute Engine Discussion Google Group (gce-dis...@googlegroups.com) to participate in discussions with other members of the Google Compute Engine community and the Google Compute Engine Team.
---

You received this message because you are subscribed to a topic in the Google Groups "gce-discussion" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gce-discussion/RD8XgXFSNBc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gce-discussio...@googlegroups.com.

To post to this group, send email to gce-dis...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/gce-discussion/51720084-b3cd-4789-b227-8de65a3acacc%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

DISCLAIMER: This communication (including any attachments) is intended solely for the recipient(s) named above and may contain information that is confidential, privileged or legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication. Thank you for your cooperation.

[Christopher Bracy]

I'll try to bring everything to this thread....

What is the image you used to start the instance?  It was a sles11-sp3 image that was available a few months.  It was configured, and then we created several new images and build servers from that.  We will pass 50 today.

What regions?  all us-central-1a

The log file /var/log/cloudregister

  2014-12-02 15:43:20,377 INFO:Using API: regionInfo
2014-12-02 15:43:20,378 INFO:Using region server: 146.148.73.14
2014-12-02 15:43:20,420 INFO:Starting new HTTPS connection (1): 146.148.73.14
2014-12-02 15:43:20,439 INFO:Starting new HTTP connection (1): 108.59.85.41
2014-12-02 15:43:20,443 INFO:Modified /etc/hosts, changed IP for: smt-gce.susecloud.net
2014-12-02 15:43:20,455 INFO:Instance is registered, nothing to do
2014-12-11 19:35:31,765 INFO:Using API: regionInfo
2014-12-11 19:35:31,765 INFO:Using region server: 146.148.73.14
2014-12-11 19:35:31,775 INFO:Starting new HTTPS connection (1): 146.148.73.14
2014-12-11 19:35:31,790 INFO:Starting new HTTP connection (1): 108.59.80.221
2014-12-11 19:35:31,793 INFO:Modified /etc/hosts, changed IP for: smt-gce.susecloud.net
2014-12-11 19:35:31,794 INFO:Registration: /usr/lib/suseRegister/bin/clientSetup4SMT.sh --host smt-gce.susecloud.net --fingerprint 9E:B5:BD:DA:97:52:DA:55:F0:F2:5D:5C:64:60:D3:E0:5C:D4:FB:79 --yes

Are you using BYOS images?  No  They were not available at the start of the project.  Is there a way to convert?  But thats another subject.

Chris Bracy
Manager of Infrastructure and Hosting
Unilog Content Solutions LLC
Suite 510
985 Old Eagle School Rd
Wayne, PA 19087
direct: 484-254-6632
skype: cabracy

---

From: gce-dis...@googlegroups.com <gce-dis...@googlegroups.com> on behalf of Robert Schweikert <rjsc...@suse.com>
Sent: Thursday, December 11, 2014 4:01 PM
To: gce-dis...@googlegroups.com
Subject: [gce-discussion] Re: SUSE update repositories disappeared

 

--
© 2014 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
 
Email preferences: You received this email because you signed up for the Google Compute Engine Discussion Google Group (gce-dis...@googlegroups.com) to participate in discussions with other members of the Google Compute Engine community and the Google Compute Engine Team.
---
You received this message because you are subscribed to a topic in the Google Groups "gce-discussion" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gce-discussion/RD8XgXFSNBc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gce-discussio...@googlegroups.com.
To post to this group, send email to gce-dis...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gce-discussion/51720084-b3cd-4789-b227-8de65a3acacc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Robert Schweikert]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/12/2014 07:31 AM, Christopher Bracy wrote:
> suse_register -E
>
> /etc/init.d/guestregister start
>
>
> This was a msitake because it cleared out the repositories.

Well, suse_register -E removes the registration information locally,
and that's OK. You then re-ran the registration and that should have
put the repositories back.

> I can rebuild that list by hand once the repository server is
> back.

That will not do the trick there is a bit more magic sauce involved.
>
>
> smt-gce.susecloud.net<http://smt-gce.susecloud.net> at

> 108.59.80.221 is not reachable from any of my servers.

Well, lets figure out why not. This will be the first piece of the
puzzle. What is the response to:

wget http://smt-gce.susecloud.net/smt.crt

Does the file get downloaded or do you get an error?

>
> Other servers i patched last week with this as the repository
> worked and now can not accesss it either.

I deployed a new access control mechanism, maybe that is the culprit.
Can you provide me with the public IP of one or two of these
instances? In what region are they running?

Thanks


- --
Robert Schweikert MAY THE SOURCE BE WITH YOU
Public Cloud Architect LINUX
rjsc...@suse.com
781-464-8147
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJUixsTAAoJEE4FgL32d2UkutsIAJOgKz8bjGE8qrvW697ib9ep
hdU5myWX0NgnxCScGq3jTEqnDR3W7LmXtPqOhAVAv+CcF2ALcPcscessy4qM8cKf
BCsFFs0WmxYuKH3ICkx9uakBuwJtBWtr4kTcVD5/lextW88n7cz/QpS7tawSLgYA
kOXkLrNftXHVeYZvXyUdBM3KPcVs0TAnnLIKC3DTJaSqbKtxUpn/J+YsuBYx6yvD
eGfxlUbD5RDU4RmufuXoBv4ETsSiaPHxbFmuDs7RtO+y/QnccoBfkgPuQME5qz7S
iDpM0xjCWfK46dfLZIwTJ9buaP5ty7nSE6C29G0SDUy+ZJzr5j9Vg8K7dhIhgOw=
=R43N
-----END PGP SIGNATURE-----

[Robert Schweikert]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/12/2014 07:46 AM, Christopher Bracy wrote:
> I'll try to bring everything to this thread....
>
>
> What is the image you used to start the instance? It was a
> sles11-sp3 image that was available a few months.

Sorry will need to know more detail, i.e. the exact image name, should
be something like sles11-sp3-vSOMEDATE

> It was configured, and then we created several new images and build
> servers from that.

When you say "created several new images" what operations did you perform?

> We will pass 50 today.
>
> What regions? all us-central-1a
>
> The log file /var/log/cloudregister
>
> 2014-12-02 15:43:20,377 INFO:Using API: regionInfo 2014-12-02
> 15:43:20,378 INFO:Using region server: 146.148.73.14 2014-12-02
> 15:43:20,420 INFO:Starting new HTTPS connection (1): 146.148.73.14
> 2014-12-02 15:43:20,439 INFO:Starting new HTTP connection (1):
> 108.59.85.41 2014-12-02 15:43:20,443 INFO:Modified /etc/hosts,
> changed IP for: smt-gce.susecloud.net 2014-12-02 15:43:20,455
> INFO:Instance is registered, nothing to do 2014-12-11 19:35:31,765
> INFO:Using API: regionInfo 2014-12-11 19:35:31,765 INFO:Using
> region server: 146.148.73.14 2014-12-11 19:35:31,775 INFO:Starting
> new HTTPS connection (1): 146.148.73.14 2014-12-11 19:35:31,790
> INFO:Starting new HTTP connection (1): 108.59.80.221 2014-12-11
> 19:35:31,793 INFO:Modified /etc/hosts, changed IP for:
> smt-gce.susecloud.net 2014-12-11 19:35:31,794 INFO:Registration:
> /usr/lib/suseRegister/bin/clientSetup4SMT.sh --host
> smt-gce.susecloud.net --fingerprint
> 9E:B5:BD:DA:97:52:DA:55:F0:F2:5D:5C:64:60:D3:E0:5C:D4:FB:79 --yes

OK, access to the region server works and your instance is being
pointed to the correct SMT server.

>
>
> Are you using BYOS images? No They were not available at the
> start of the project. Is there a way to convert?

No sorry. once you run an on demand image that's what you have, there
is no way to convert, you'd have to start over.

Later,
Robert

- --
Robert Schweikert MAY THE SOURCE BE WITH YOU
Public Cloud Architect LINUX
rjsc...@suse.com
781-464-8147
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJUixwYAAoJEE4FgL32d2Uk8qQH/Agmo8A+vR2kir115Mp4FEHV
cuBPAHMR7gsPl31RHLUz8Lve6Ppl+CNsi5W5ZkfmJeTQd+XD4JVPQVKL1JqmaiRF
LnxkZXgha9vq2sblQGONxHNTeguDkYV//O8BJeU7oXlIVpNOgkXd62iY/zj5gNj1
lHCKge/idSbETB6BgceCtTQVv/dHhGjjqS8yaJWMgpNsfaBETL97x+kIosFgODLu
lz3A5jzKLdxAawwaGOHDrl4A0Dwch8kJ17hPXk4IbGBWl22oODhaoif4yJ5b3Hoz
VJmFIF/oQmXXU0JVKeJoSRjIc8JMu6ujLhEbViL+dXkiw9LX9a0dMf96JKrtbZo=
=+ZHr
-----END PGP SIGNATURE-----

[Christopher Bracy]

Answered below.

I just built a new instance from sles-11-sp3-v20141105 (the 9/30 isnt there)

I try online update. There are initially no repositories, so the workflow runs. Then it gives the same error, that it cant access smt-gce.susecloud.net

I was actually trying to add a package when I started this. Should that work from the same repository?

________________________________________
From: Robert Schweikert <rjsc...@suse.com>
Sent: Friday, December 12, 2014 11:47 AM
To: Christopher Bracy; gce-dis...@googlegroups.com
Subject: Re: [gce-discussion] Re: SUSE update repositories disappeared

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/12/2014 07:46 AM, Christopher Bracy wrote:
> I'll try to bring everything to this thread....
>
>
> What is the image you used to start the instance? It was a
> sles11-sp3 image that was available a few months.

Sorry will need to know more detail, i.e. the exact image name, should
be something like sles11-sp3-vSOMEDATE

I don't know for sure, but I would guess sles-11-sp3-v20140930 since they were built in October.

> It was configured, and then we created several new images and build
> servers from that.

When you say "created several new images" what operations did you perform?

Mount temparary disk to /mnt/tmp
gcimagebundle -d /dev/sda -o /mnt/tmp/
gsutil cp xx.image.tar.gz gs://path
gcloud compute images create imagename -source-uri gs://path/xx.image.tar.gz

[Robert Schweikert]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/12/2014 12:36 PM, Christopher Bracy wrote:
<snip>

>
> When you say "created several new images" what operations did you
> perform?
>
> Mount temparary disk to /mnt/tmp gcimagebundle -d /dev/sda -o
> /mnt/tmp/ gsutil cp xx.image.tar.gz gs://path gcloud compute images
> create imagename -source-uri gs://path/xx.image.tar.gz

OK, I think this answers the question and also the question about the
conversion to BYOS ;)

I suspect, will confirm with my contact at Google, that gcimagbundle
does not wrap the metadata into the tarball. Therefore as far as the
SMT server is concerned you are running a BYOS image and you are not
granted access to the repositories on the SMT server running in GCE.

You'd have to register the server with the customer center using
suse_register and your SUSE entitlements.

We'll see if my suspicion is correct.

- --
Robert Schweikert MAY THE SOURCE BE WITH YOU
Public Cloud Architect LINUX
rjsc...@suse.com
781-464-8147
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJUizXqAAoJEE4FgL32d2UkLP4H/Atb6N7kG37WDpGZHvHtaOdg
YyAMHogGiSYRgqMHq2QGH1sitWkcUq+nutjAtVITug2CckJgyYKpZseDWHO++eT+
NgebRE8StT9TaYNB6gzDtdzcu5EvJtGt/e7GfrEpOtiDdHSPVWkRv/DUQOuYFvNi
cVe+Mk80lODx5SuuRldyyIyqeo409nc0r3no0kjl8yTE44a1IjcHNWDUUYoXVG7F
lMCbOsv8yPk+NXD9e6JTMjhsYY4cWTTOVYFEctDOrdyWGEQi3oXXCbVVpjqrwkWF
COrmS2AfeLG2sBsIHa96YT2diaHKZh9BuAFLjRgH+MTjFF6e5VWr7Sva4dhLQ9o=
=Uf1F
-----END PGP SIGNATURE-----

[Robert Schweikert]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/12/2014 01:37 PM, Robert Schweikert wrote:
> On 12/12/2014 12:36 PM, Christopher Bracy wrote: <snip>
>
>> When you say "created several new images" what operations did
>> you perform?
>
>> Mount temparary disk to /mnt/tmp gcimagebundle -d /dev/sda -o
>> /mnt/tmp/ gsutil cp xx.image.tar.gz gs://path gcloud compute
>> images create imagename -source-uri gs://path/xx.image.tar.gz
>
> OK, I think this answers the question and also the question about
> the conversion to BYOS ;)
>
> I suspect, will confirm with my contact at Google, that
> gcimagbundle does not wrap the metadata into the tarball. Therefore
> as far as the SMT server is concerned you are running a BYOS image
> and you are not granted access to the repositories on the SMT
> server running in GCE.
>
> You'd have to register the server with the customer center using
> suse_register and your SUSE entitlements.
>
> We'll see if my suspicion is correct.

My suspicion was incorrect. gcimagebundle does preserve the metadata.
Thus, you should get access to the SMT servers in GCE.

Lets double check the access control of the SMT servers, can you give
the public IP address of one or two machines where you observer the
problem?

Thanks

- --
Robert Schweikert MAY THE SOURCE BE WITH YOU
Public Cloud Architect LINUX
rjsc...@suse.com
781-464-8147
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJUiz9hAAoJEE4FgL32d2UkOWkH/1aeBOrEy2zAl8LPBnf7dtRz
k4dwH3+84StS9MVfAoLsUdn+KGajVv0fdSdGh5u2gUAz1kosf1t5wdIllvoBSIdX
pH+Vz7rCxYgE8jb5lsFcHp6LwbXPozPOl9ZxDJGRixfY1KSTwvIlOSiXsqlO0hae
JPI/ok6bXAfgKiSFuVcq4sOpQLP+9/PdiUgC/+Bi15yH6MVMJPUULeKdkILBBJ+k
92OkdQm5clm5vfINcU+um6UvBD2cZx7V/sZotPBuyJBJyIY40ZT9HuXb6eF+Yk34
XjHtmArDTEmH5s7vqipxQNB9Xd5snJlxOMVjbCvVpbgdmG4ZiimOw3sbatIJBkY=
=atK1
-----END PGP SIGNATURE-----

[Robert Schweikert]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/12/2014 02:17 PM, Robert Schweikert wrote:
> On 12/12/2014 01:37 PM, Robert Schweikert wrote:
>> On 12/12/2014 12:36 PM, Christopher Bracy wrote: <snip>
>
>>> When you say "created several new images" what operations did
>>> you perform?
>
>>> Mount temparary disk to /mnt/tmp gcimagebundle -d /dev/sda -o
>>> /mnt/tmp/ gsutil cp xx.image.tar.gz gs://path gcloud compute
>>> images create imagename -source-uri gs://path/xx.image.tar.gz
>
>> OK, I think this answers the question and also the question
>> about the conversion to BYOS ;)
>
>> I suspect, will confirm with my contact at Google, that
>> gcimagbundle does not wrap the metadata into the tarball.
>> Therefore as far as the SMT server is concerned you are running a
>> BYOS image and you are not granted access to the repositories on
>> the SMT server running in GCE.
>
>> You'd have to register the server with the customer center using
>> suse_register and your SUSE entitlements.
>
>> We'll see if my suspicion is correct.
>
> My suspicion was incorrect. gcimagebundle does preserve the
> metadata. Thus, you should get access to the SMT servers in GCE.
>
> Lets double check the access control of the SMT servers, can you
> give the public IP address of one or two machines where you
> observer the problem?

OK, found the bug, it was an issue with the access control. A certain
set of IP addresses was being dropped :( . The bug is fixed now and
the code has been deployed to all servers. I double checked the ACL
and your issue should be resolved.

Sorry for the inconvenience, thanks for the patience and working with
me to get this resolved.

- --
Robert Schweikert MAY THE SOURCE BE WITH YOU
Public Cloud Architect LINUX
rjsc...@suse.com
781-464-8147
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJUi2gpAAoJEE4FgL32d2Uk6zgH/1vGAf7zdcjOVFQ2F2zTO/Lw
F4O0C/SRRDcMOlhGh5X/ZKGcoS/Fpq7hyPeLHKk0nP5bH0fNQl3Cvgv56C/CPZ8T
1ijDzlWfUgtP/uPWIgKEESLUIlfXi+tJUwrBKAGz9HghdmwDvMw+r+mygWNhS2pv
0XK4JvB9LiIVpP9Gk3lDtg/mpexsNSDMCKi2Iq9idbz/RcLGDyVo42ruaSrFk0hP
l7mSRIrGl/9b63/2FePCuz/sr0ehPhQb1WONuxwDysghkukCBTpODbkK0cUjzCsV
vV1r+vk6Wr4CyHAfy+CUrHAZXspokQoXMCkDpoFGHsJU7Cb3t/Q17fe10J+X1Ow=
=8wXk
-----END PGP SIGNATURE-----

[Christopher Bracy]

I tried on several (but not nearly all) of the servers and both online update and package installation works.

Thanks for the quick response.

Chris Bracy
Manager of Infrastructure and Hosting
Unilog Content Solutions LLC
Suite 510
985 Old Eagle School Rd
Wayne, PA 19087
direct: 484-254-6632
skype: cabracy

________________________________________
From: gce-dis...@googlegroups.com <gce-dis...@googlegroups.com> on behalf of Robert Schweikert <rjsc...@suse.com>
Sent: Friday, December 12, 2014 5:11 PM
To: gce-dis...@googlegroups.com

Subject: Re: [gce-discussion] Re: SUSE update repositories disappeared

--
© 2014 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043

Email preferences: You received this email because you signed up for the Google Compute Engine Discussion Google Group (gce-dis...@googlegroups.com) to participate in discussions with other members of the Google Compute Engine community and the Google Compute Engine Team.
---
You received this message because you are subscribed to a topic in the Google Groups "gce-discussion" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/gce-discussion/RD8XgXFSNBc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to gce-discussio...@googlegroups.com.
To post to this group, send email to gce-dis...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/gce-discussion/548B6829.3040000%40suse.com.

For more options, visit https://groups.google.com/d/optout.

[Usama Abdulrehman]

When executing this command for system registration  SUSEConnect -p PackageHub/15/x86_64

i'm getting below error, it seems the web address its pointing to for registration is not valid, any hints?  

Registering system to registration proxy https://smt-gce.susecloud.netUpdating system details on https://smt-gce.susecloud.net ...Activating PackageHub 15 x86_64 ...Error: Registration server returned 'Unmet product dependencies, activate one of these products first: Basesystem Module 15 x86_64, Basesystem Module 15 x86_64, Basesystem Module 15 x86_64' (422)

[Robert Schweikert]

Hi,

On 2/1/20 6:02 PM, 'Usama Abdulrehman' via gce-discussion wrote:
> When executing this command for system registration SUSEConnect -p
> PackageHub/15/x86_64
>
> i'm getting below error, it seems the web address its pointing to for
> registration is not valid, any hints?
>
> Registering system to registration proxy https://smt-gce.susecloud.netUpdating
> system details on https://smt-gce.susecloud.net ...Activating PackageHub 15
> x86_64 ...Error: Registration server returned 'Unmet product dependencies,
> activate one of these products first: Basesystem Module 15 x86_64,
> Basesystem Module 15 x86_64, Basesystem Module 15 x86_64' (422)

Looks like the system does not have the necessary repositories setup.

What does zypper lr return?

--
Robert Schweikert MAY THE SOURCE BE WITH YOU

Distinguished Engineer LINUX
Technical Team Lead Public Cloud
rjsc...@suse.com
IRC: robjo

[Gautham (Google Cloud Support)]

Hi,

 

The issue appears to be at the OS level not really within the scope of this board, Google groups is meant for architectural and outages based discussions. . I would recommend posting this question on Serverfault.com [1] or Stackoverflow[2] for more visibilty.

[1] https://stackoverflow.com/questions/tagged/suse

[2] https://serverfault.com/questions/tagged/opensuse

[Robert Schweikert]

On 2/6/20 7:06 PM, 'Gautham (Google Cloud Support)' via gce-discussion
wrote:

> Hi,
>
>
>
> The issue appears to be at the OS level not really within the scope of this
> board, Google groups is meant for architectural and outages based
> discussions. . I would recommend posting this question on Serverfault.com
> [1] or Stackoverflow[2] for more visibilty.
>
>
> [1] https://stackoverflow.com/questions/tagged/suse
> [2] https://serverfault.com/questions/tagged/opensuse

Where it will probably go unanswered as I don't think anyone is
monitoring those forums AFAIK.