Huge Thanks to all of you and the team.
Yes After executed the given command, I can able to access the cock pit. will
wait for the fixes.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy
Hi Klaas,
Thanks for the update!
On Tue, May 25, 2021 at 8:12 PM Klaas Demter wrote:
> I can confirm after this cockpit login works again on ovirt-node 4.4.6.3
>
>
> Greetings
>
> Klaas
>
>
>
> On 5/25/21 5:10 PM, Lev Veyde wrote:
>
> Hi Dhanaraj,
>
> First of all - thanks for informing us
I can confirm after this cockpit login works again on ovirt-node 4.4.6.3
Greetings
Klaas
On 5/25/21 5:10 PM, Lev Veyde wrote:
Hi Dhanaraj,
First of all - thanks for informing us about this issue!
We found the source of the issue, and are working on fixing it for the
next release.
Hi Dhanaraj,
First of all - thanks for informing us about this issue!
We found the source of the issue, and are working on fixing it for the next
release.
Meanwhile there is a workaround that should fix the situation.
You need to run (with root account) the following command:
chmod u+s
Hi All
if any further logs required let me know I can share the info,
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
Hi,
I reproduced this issue when upgrading ovirt node from
ovirt-node-ng-4.4.5.1-0.20210323.0+1 to
ovirt-node-ng-4.4.6.3-0.20210518.0+1
After the upgrade, when logging in to cockpit, got a "Wrong user name or
password" error.
Thanks & regards
Pengshan Yu
On Wed, May 19, 2021 at 3:13 PM
On Wed, May 19, 2021 at 9:05 AM Yaning Wang wrote:
> add p...@redhat.com
>
> Sandro Bonazzola 于2021年5月19日周三 下午2:40写道:
>
>>
>>
>> Il giorno lun 17 mag 2021 alle ore 07:48 dhanaraj.ramesh--- via Users <
>> users@ovirt.org> ha scritto:
>>
>>> Hi Team,
>>>
>>> after upgrading ovirt node from 4.4.5
add p...@redhat.com
Sandro Bonazzola 于2021年5月19日周三 下午2:40写道:
>
>
> Il giorno lun 17 mag 2021 alle ore 07:48 dhanaraj.ramesh--- via Users <
> users@ovirt.org> ha scritto:
>
>> Hi Team,
>>
>> after upgrading ovirt node from 4.4.5 to 4.4.6, unale to login to the
>> cockpit using root, but could
Hi Sandro,
QE did not reproduce this issue when upgrading RHVH from 4.4.5 to 4.4.6. I
will try to reproduce with ovirt node.
Thanks & Regards
Pengshan Yu
On Wed, May 19, 2021 at 2:41 PM Sandro Bonazzola
wrote:
>
>
> Il giorno lun 17 mag 2021 alle ore 07:48 dhanaraj.ramesh--- via Users <
>
Il giorno lun 17 mag 2021 alle ore 07:48 dhanaraj.ramesh--- via Users <
users@ovirt.org> ha scritto:
> Hi Team,
>
> after upgrading ovirt node from 4.4.5 to 4.4.6, unale to login to the
> cockpit using root, but could able to login via ssh. please check whether
> this is considered as bug
>
Can
I fixed the permission error with btmp but it made no difference.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
Thanks everyone for the troubleshooting so far. I agree that the cockpit auth
file is the same as 4.4.5. The timestamps are before the upgrade too. I get
the same errors in the secure log. I found an error messages, looking at it
now.
secure log
May 18 21:50:57 unix_chkpwd[529704]:
Gianluca, I hope I my frustration didn't come across too strong - I apologize
if so. I certainly now understand your posting of 4.4.5 as a diff source
against 4.4.6 - thanks! - regards - Glenn
___
Users mailing list -- users@ovirt.org
To unsubscribe
I swapped out the /etc/authselect login and system files and It seems to be
that the
updated node 4.6 pam stack is calling /usr/sbin/chkpwd and that fails for
all cockpit users, root and otherwise.
for root
May 18 13:03:02 br014 unix_chkpwd[14186]: check pass; user unknown
May 18 13:03:02 br014
/etc/pam.d/cockpit under node 4.4.6 is the same as you posted.
Something else changed.
#%PAM-1.0
# this MUST be first in the "auth" stack as it sets PAM_USER
# user_unknown is definitive, so die instead of ignore to avoid subsequent
modules mess up the error code
-auth [success=done
On Tue, May 18, 2021 at 4:50 PM Glenn Farmer
wrote:
> The current thread is about 4.4.6 - nice that you can login to your 4.4.5.
>
The subject of the thread says it all... ;-)
My point was to ask if you see differences in /etc/pam.d/cockpit in your
4.4.6, in respect with the version I pasted
I see the same thing on a test cluster. I presumed it was due to using
sssd and kerberos for local user logins.
Here's an example of what gets written to /var/log/secure when root login
to cockpit fails.
May 18 11:29:07 br014 unix_chkpwd[26429]: check pass; user unknown
May 18 11:29:07 br014
The current thread is about 4.4.6 - nice that you can login to your 4.4.5.
I changed the admin password on the engine - still cannot access the Cockpit
GUI on any of my hosts.
Do I have to reboot them? Restart Cockpit - tried that - failed.
Cannot access Cockpit on all hosts in a cluster
On Tue, May 18, 2021 at 7:39 AM wrote:
> Hello.
> I'm having the same issue with cockpit on the nodes. I'm unable to login
> as root or local user. I went from 4.4.5 to 4.4.6. It worked fine before
> the upgrade. I know the password is correct because I can log into the node
> via console and
Hello.
I'm having the same issue with cockpit on the nodes. I'm unable to login as
root or local user. I went from 4.4.5 to 4.4.6. It worked fine before the
upgrade. I know the password is correct because I can log into the node via
console and ssh. On one of the nodes I created a local account
Connect to engine via ssh and run following command with template:
#ovirt-aaa-jdbc-tool user password-reset {username}
--password-valid-to='-MM-dd hh:mm:ssZ'
After reset check admin user status:
#ovirt-aaa-jdbc-tool user show admin
___
Users mailing
21 matches
Mail list logo