Describe what you would like us to do:

When I tried to sudo on aarch64 and s390x VM's, they are just stuck after Password+Token prompt for 5 min or so and then returning back Sorry, try again.

It is really helpful to look at whats going on those vm's when a build is stuck.

When do you need this to be done by? (YYYY/MM/DD)

ASAP

mohanboddu commented Jun 24, 2020

FYI, I tried it on buildhw-a64-01 and buildvm-s390x-08 vm's

kevin commented Jun 25, 2020

I think this may be a RHIT firewall issue. Those builder networks need to talk to proxy01/10/101/110 on port 8443/tcp to get to the totpcgi/yubikey pods in openshift.

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: groomed, medium-gain, medium-trouble

Jun 25, 2020

kevin commented Sep 2, 2020

This is fixed.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Sep 2, 2020

sharkcz commented Sep 10, 2020

Finally tried myself and it really has been fixed. Thanks a lot.

Metadata

Assignee

None

Tags

Blocking

None

Depending on

None

Priority

Normal

fedora-infrastructure

#9078 sudo not working on aarch64 and s390x builders Closed: Fixed Sep 2, 2020 by kevin. Opened Jun 24, 2020 by mohanboddu.

Describe what you would like us to do:

When do you need this to be done by? (YYYY/MM/DD)

Metadata

medium-gain medium-trouble

#9078 sudo not working on aarch64 and s390x builders

Closed: Fixed Sep 2, 2020 by kevin. Opened Jun 24, 2020 by mohanboddu.