General

Profile

Alexander Brunhirl

  • Login: abrix
  • Registered on: 2014-09-18
  • Last connection: 2020-07-01

Issues

open closed Total
Assigned issues 0 0 0
Reported issues 12 16 28

Activity

2020-07-01

16:11 Rudder Bug #17893 (In progress): After migration standard technique packageManagement doesn't work anymore
Like Bug #17895, this was a follow up error from Bug #17873.
> Follow up error from #17873; hence I closed it.
> ...
Alexander Brunhirl
14:47 Rudder Bug #17893: After migration standard technique packageManagement doesn't work anymore
Unfortunatly it's not the case @rudder@ does contain the proper values @{"packages":{"installed_cache_expire":60,"upd... Alexander Brunhirl
12:20 Rudder Bug #17893: After migration standard technique packageManagement doesn't work anymore
Just collected the data... Alexander Brunhirl
11:47 Rudder Bug #17893: After migration standard technique packageManagement doesn't work anymore
Same with latest available version... Alexander Brunhirl
11:35 Rudder Bug #17893 (Rejected): After migration standard technique packageManagement doesn't work anymore
Hi,
after the rudder 6.0 to 6.1 migration the standard directive "Packages" seems to report errors and don't insta...
Alexander Brunhirl
16:06 Rudder Bug #17895 (Rejected): After migration from 6.0 to 6.1 the Techniques Editor is empty
Follow up error from #17873; hence I closed it.
Workaround:...
Alexander Brunhirl
13:59 Rudder Bug #17895 (Rejected): After migration from 6.0 to 6.1 the Techniques Editor is empty
Hi,
after the upgrade from 6.0 to 6.1 on SLES12 SP4 the technique editor is empty.
Best regards,
Alex
Alexander Brunhirl

2020-06-30

09:51 Rudder Bug #17873: SLES12 upgrade error 6.0 to 6.1
FYI. the RPM Epoch is still showing 30.04.2014 ;)... Alexander Brunhirl
09:46 Rudder Bug #17873 (Released): SLES12 upgrade error 6.0 to 6.1
Hi,
during upgrading from Rudder 6.0 to 6.1 on SLES12 SP4 I got the following error.
Best regards,
Alex
<pr...
Alexander Brunhirl

2020-06-10

15:58 Rudder Bug #17703: Jinja2 vars.sys.ipv4 issue
> jinja2 has actually two syntaxes for key access : . or [''] (with quotes), so as the variable name contains [] we n... Alexander Brunhirl

Also available in: Atom