** Description changed:

  [ Impact ]
  
  Outputs of long configurations always have their lines wrapped, even when 
piped
  into another command, which is not intended, and can break automation or 
scripts.
  
  We fix this by backporting a fix from upstream (already present in R/S)
  to Noble.
  
- 
  [ Test Plan ]
  
  $ apt update; apt install pcs pacemaker corosync resource-agents-extra
- $ lxc exec pcs-repro -- pcs resource create longline ocf:heartbeat:Dummy \
-       
state=/var/lib/some/very/long/path/that/makes/the/attributes/line/way/longer/than/eighty/characters
+ $ pcs resource create longline ocf:heartbeat:Dummy \
+       
state=/var/lib/some/very/long/path/that/makes/the/attributes/line/way/longer/than/eighty/characters
  $ pcs config | grep "state=/var/lib"
  
  this will output
  
  Warning: Some nodes are missing names in corosync.conf, those nodes were 
omitted. Edit corosync.conf and make sure all nodes have their name set.
-       
state=/var/lib/some/very/long/path/that/makes/the/attributes/line/way/long
+       
state=/var/lib/some/very/long/path/that/makes/the/attributes/line/way/long
  
  with the long path cut off (as it is wrapped)
  
  the fixed version would have:
  
  Warning: Some nodes are missing names in corosync.conf, those nodes were 
omitted. Edit corosync.conf and make sure all nodes have their name set.
-       
state=/var/lib/some/very/long/path/that/makes/the/attributes/line/way/longer/than/eighty/characters
+       
state=/var/lib/some/very/long/path/that/makes/the/attributes/line/way/longer/than/eighty/characters
  
  as one (very long) line
  
  [ Where Problems Might Occur ]
  
- The fix is targeted to the specific check for whether or not lines should be 
wrapped, so it is unlikely to cause other problems in pcs itself. However, 
+ The fix is targeted to the specific check for whether or not lines should be 
wrapped, so it is unlikely to cause other problems in pcs itself. However,
  other packages may depend on this unintended behavior. If such regressions
  are found, they will require their own fixes and SRUs
  
  [ Original Bug ]
  
  -> $ pcs constraint colocation --full
  Colocation Constraints:
    Promoted resource 'REDIS-6385-clone' with Promoted resource 'PGSQL-
        PAF-5438-clone' (id: colocation-REDIS-6385-clone-PGSQL-PAF-5438-clone-
        INFINITY)
      score=INFINITY
    Started resource 'HA-10-1-1-88' with Promoted resource 
'PGSQL-PAF-5438-clone'
        (id: colocation-HA-10-1-1-88-PGSQL-PAF-5438-clone-INFINITY)
      score=INFINITY
  ...
  
  I do not believe this is due to env vars/params - is it hard-coded @ 
compile/build time?
  Should be:
  
  -> $ pcs constraint colocation --full
  Colocation Constraints:
    Promoted resource 'REDIS-6385-clone' with Promoted resource 
'PGSQL-PAF-5438-clone' (id: 
colocation-REDIS-6385-clone-PGSQL-PAF-5438-clone-INFINITY)
      score=INFINITY
  ...
  
  I you can, please fix it.
  many thanks, L

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2168936

Title:
  pcs output with broken lines - why?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/2168936/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to